
If you previously signed in to Imagild with an email code, use Set / forgot password? in the sign-in dialog and verify the same email to set a password for that existing account. Then sign in with your email and new password. Setting a password is an account-access change; it does not create another account or grant another welcome balance.
Key Takeaways
- Start from the existing account's email, not a new registration.
- Request a code in the password-setting flow; a registration code serves a different purpose.
- After signing in, check your account, points and a known job before submitting new work.
Identify the email that owns your work
Use the email associated with your previous Imagild account. A familiar browser profile, nickname or photograph does not establish which account is signed in. If you still have a working session, record the account information available through the normal interface before changing anything. Keep that information private.
Your goal is to regain access to existing work. Choosing Sign up with a different address is a different operation, even if you use the same nickname. Do not recreate an account to test whether its points appear. If you cannot identify the original email, use Imagild support rather than guessing through repeated registrations.
Set the password from the sign-in dialog
Open the normal sign-in dialog on Imagild. The English password-recovery control is labeled Set / forgot password?; other interface languages use their corresponding labels.
- Choose Set / forgot password? rather than Sign up.
- Enter the existing account's email address.
- Request the verification code from this password-setting screen.
- Open the latest relevant email and enter that code in the same flow.
- Enter and confirm your new password, then save it.
- When the interface confirms the password was saved, return to sign-in and use the email and new password.
Choose a unique password and store it privately. Do not place the password or email code in a prompt, screenshot, support post or shared project brief. Support can investigate an access problem without asking you to publish either secret.
If a code is missing or rejected, diagnose that step separately. Repeatedly alternating between Sign up and password recovery makes it harder to know which code belongs to which operation. A successful password-save message is the checkpoint for this procedure; an email saying a code was requested is not that checkpoint.
Check the original account before generating
Once signed in, confirm the account shown in the interface and inspect a known item in Jobs or My assets. Compare a recognizable job or approximate creation time with your own records. Check the points display as a separate observation.
| What you observe | Next action |
|---|---|
| The expected account and known job are visible | Continue from that job or approved asset |
| Login works, but the account details differ | Stop and identify the original sign-in account |
| The account matches, but one job is missing | Keep its identifier or approximate submission time for support |
| A job is still processing | Inspect that task instead of creating a replacement automatically |
The existing-task recovery guide explains the difference between a draft, an accepted job and a completed result. Password setup does not prove that every browser-local field or editing arrangement has been restored.
A hypothetical return to an unfinished project
Suppose you previously used an email code to create a poster and later return to a password-based sign-in screen. Keep the original email, set its password, sign in, then locate the poster job. If its result is already available, review that result. Sending the same brief again would be a new generation rather than proof that account recovery worked.
This is an illustrative sequence, not a completed account-recovery test or a promise that a specific missing file can be restored. The pending-job checklist covers uncertain task states after access is restored.
What should stay unchanged?
Setting a password on the existing account does not create a second welcome grant. The points guide explains that the welcome allowance is granted once. Do not use the absence of a new grant as evidence that password setup failed.
Account access and the media-retention period are also separate. Regaining a login does not extend every old file's storage lifetime or guarantee recovery after deletion. Verify important results while they are available and retain your own approved copies.
Sources and scope
The password-setting labels and existing-account behavior were checked against Imagild's current sign-in implementation on October 30, 2026. Imagild support is the contact route for an unresolved access problem. This guide explains the documented workflow; no customer's password was changed and no live recovery, paid generation or account-merging test was performed for this article.
Prepared by Imagild Editorial, the company editorial team responsible for these guides. AI assisted research and drafting. Report a correction.
Cover: AI-generated conceptual illustration; not an application screenshot, observed result, private account record or privacy guarantee.