You changed your ChatGPT account email in Settings → Account, the page asked for a verification code, and somewhere in that flow you got signed out. Now the old email logs you in to nothing (or says “incorrect email or password”), the new email says “no account found,” and the only thread holding the account together is a confirmation email you may not have finished. This stuck state is common because the email change only commits once the new address is confirmed — until then the account is in a half-flipped state, and any sign-out in between drops you into limbo.
Fastest fix (as of June 2026): the modern ChatGPT flow no longer relies on a clickable link. It sends a 6-digit security code to the new inbox; you paste that code back into the ChatGPT page to commit the change. So step one is: open the new inbox, find the code from noreply@tm.openai.com, and finish the prompt in the same tab that asked for it. If that tab is gone, log in with the new email and OpenAI re-issues a code. If you signed in with Google/Apple and there is no password, the change never applied — log back in with the OLD method and you will find everything intact.
One thing to settle the panic first: changing your email does not move, copy, or delete your account. It renames the account in place, so chat history, subscriptions, and custom instructions stay attached regardless of which side of the flip you are on.
First, log in at the right address
OpenAI moved the primary app to chatgpt.com (the old chat.openai.com now 301-redirects there). If you bookmarked the legacy URL, you are fine, but do all of the steps below at chatgpt.com so you are not debugging a redirect on top of an auth problem.
Common causes
Ordered by hit rate, highest first.
1. The 6-digit code is sitting unentered (or in spam)
The confirmation mail comes from noreply@tm.openai.com and contains a 6-digit code, not just a link. Gmail Promotions, Outlook Focused, and corporate Mimecast/Proofpoint filters routinely hide it. If you never typed the code, the change never committed.
How to judge: Search the new inbox for from:openai.com with All Mail / All Folders scope (includes Spam, Promotions, Archive). If a code mail exists and you never entered it, this is you.
2. You signed up with Google / Apple / Microsoft and have no password
If your account was created via social login (the SSO button), it has no email/password of its own, so the “change email” path either greys out or fails after the code step. Per OpenAI, accounts that signed up with SSO generally cannot move to email/password at all unless they are on an Enterprise plan.
How to judge: Go back to the login page and click Continue with Google (or Apple/Microsoft) with the ORIGINAL email. If that signs you straight into your real chats, the change never applied and you are safe — stop here.
3. The new email already had its own OpenAI account
You changed you@a.com to you@b.com, but you@b.com already had a separate ChatGPT account. OpenAI rejects the change (“email already in use”), but the UI may have signed you out first.
How to judge: Log in with the new email. If it lets you in but the chats are unfamiliar, that is the pre-existing account, and your change was rejected. Your original account still lives under the old email.
4. You hit the rate limit on change attempts
Sending the change (or re-requesting the code) too many times in a row temporarily locks the email-change feature. The page may show a generic “something went wrong” rather than naming the limit.
How to judge: Each retry fails instantly with the same error regardless of input. Wait, then retry.
5. The new email is a temp/disposable address or a company-verified domain
OpenAI blocks disposable mailboxes (10minutemail, temp-mail, etc.) and blocks changing to or from a domain your company has verified in its tenant. The change is refused at submit time.
How to judge: The error appears the instant you submit the new address, before any code is sent. Disposable domains and managed work domains both trigger it.
6. The code expired before you entered it
The 6-digit code is short-lived. If you let the email sit and came back later, the code is dead and you need a fresh one.
How to judge: Entering the code returns “code is invalid or expired.” Request a new code and use it within a few minutes.
Which bucket are you in?
| Symptom | Most likely cause | Go to |
|---|---|---|
| You never typed a code; mail is in spam | Cause 1 | Step 1 |
Old Continue with Google still opens your chats | Cause 2 | Step 2 |
| New email opens an account, but chats are strangers’ | Cause 3 | Step 4 (fix section) |
| Same error on every retry, instantly | Cause 4 | Wait ~30 min, then Step 1 |
| Error fires the moment you submit the new address | Cause 5 | Use a different real inbox |
| Code typed but “invalid or expired” | Cause 6 | Step 3 |
Before you start
- Do this on the web at
chatgpt.com, not the iOS or Android app. The email-change flow only exists in the web app, so retry there if you started on mobile. - Confirm you can receive mail at BOTH the old and new inboxes right now. If one is gone, recovery is much harder.
- Decide which email you actually want as your long-term primary.
- Have your password manager open; you may need both old and new credentials, and you may need to set a password (Cause 2).
- Disable any aggressive mail filters or rewrite proxies for the next hour.
Information to collect
- Old email address and new email address.
- Sign-in method actually used originally (Google, Apple, Microsoft, email/password, SSO).
- Approximate time you initiated the change (and timezone).
- Screenshot of the current error message, exact wording.
- The From header and subject of the most recent OpenAI mail in the new inbox.
- Whether either email is on a managed Microsoft 365 / Google Workspace / Mimecast / Proofpoint domain.
Step-by-step fix
Step 1: Find and enter the 6-digit code
In the new inbox, search from:openai.com across ALL folders — Junk, Spam, Promotions, Archive, and any rules folder. Open the most recent mail from noreply@tm.openai.com, copy the 6-digit code, and paste it into the ChatGPT verification field. Critically, finish this in the same browser tab that asked for the code; the field is part of the change session. If that tab is closed, do Step 2.
Step 2: If the change tab is gone, re-trigger from the new email
Go to chatgpt.com → Log in → enter the NEW email → continue. If the account is mid-flip, OpenAI re-issues a fresh 6-digit code to the new inbox and shows the entry field again. Enter the new code (the previous one is now void). This is the normal recovery path and resolves most cases.
Step 3: If the code is “invalid or expired,” request a fresh one
Click Resend code (or restart the login with the new email). A new code is issued and the old one is killed. Codes are short-lived, so grab it from the inbox and enter it within a couple of minutes. Do not request many in a row — that triggers the rate limit (Cause 4).
Step 4: If the new email already had an account, decide consolidation
The change was rejected and you now have two accounts. Options:
- Keep the original (recommended if your history and subscription live there): log in with the OLD email/method. The change was never committed despite the UI suggesting otherwise.
- Keep the new account: export your data from the old account at Settings → Data controls → Export data, then continue on the new account.
Step 5: Use a password reset as a backdoor (password accounts only)
If your account has an email/password (not pure Google/Apple/Microsoft SSO), go to chatgpt.com → Log in → Forgot password? → enter the NEW email. The reset email confirms you control that address; after resetting, sign in with the new email. If you are on SSO with no password, skip this — the reset will simply do nothing (Cause 2).
Step 6: For SSO accounts, fall back to the original provider
If you signed up with Google/Apple/Microsoft, you cannot resolve this with passwords or codes. Sign back in with Continue with Google/Apple/Microsoft using the ORIGINAL provider account. Your real chats are there. If you genuinely need a different email on the account, change it at the provider (Google/Apple/Microsoft account settings), which propagates to the OpenAI login.
Step 7: Contact support with both addresses ready
If you still cannot get in and the account holds a paid plan or chats you need, open a ticket at help.openai.com (use the chat widget; mention you are signed out). Send:
Subject: Email change stuck in verification — signed out of both addresses
Old email: you@a.com
New email: you@b.com
Change initiated at: 2026-06-15 10:15 PT
Sign-in method: Google / Apple / Microsoft / email-password
Error: cannot sign in to either; 6-digit code not received / not accepted
I control both inboxes. Please either:
(a) roll the account back to the old email, or
(b) re-send the verification code / force-complete the change to the new email.Response is usually 24-72 hours. Do not initiate another email change in the meantime — a second pending change can compound the problem.
How to confirm it’s fixed
- You can sign in at
chatgpt.comwith the chosen email and see your historical chats. - Settings → Account shows the email you intended as the primary.
- A test “Forgot password?” email (or a fresh login OTP) arrives at the new address.
- No “verify your email” banner sits at the top of the app.
Long-term prevention
- Before clicking Change, send yourself a test message at the new address from a known sender to confirm the inbox actually delivers.
- Have the new inbox open in another tab when you start, so you can paste the 6-digit code immediately before it expires.
- If you sign in with Google/Apple/Microsoft, manage the email at that provider rather than fighting the ChatGPT change flow.
- Avoid changing to a work email you might lose; when IT disables the mailbox you lose the codes and the recovery path with it.
- Keep the old inbox alive for at least 30 days after a change in case verification needs to retry.
Common pitfalls
- Closing the original change tab before entering the code — the field is session-bound, so you must re-trigger from login (Step 2).
- Requesting code after code in quick succession and tripping the rate limit (Cause 4); wait, then try once.
- Assuming a temp/disposable address will work — OpenAI rejects them at submit time.
- Starting a second email change while the first is pending; both can fail and orphan the account.
- Using a password reset on an SSO account; with no password set, the reset link does nothing.
FAQ
- Is it a link or a code now? As of June 2026 the change is confirmed with a 6-digit code sent to the new inbox, which you paste back into the ChatGPT page. Older clickable-link guides are out of date.
- Will my chat history transfer to the new email? Yes. Changing email renames the account in place; history, subscription, and custom instructions stay attached.
- I signed up with Google — why can’t I change my email? SSO accounts have no OpenAI password, so the change path is blocked. Per OpenAI, sign-up-via-SSO accounts generally cannot move to email/password unless on Enterprise; change the address at Google/Apple/Microsoft instead.
- Can I cancel an email change mid-flow? Yes — just do not enter the code. An unconfirmed change never commits, and you stay on the old email.
- Why does it say the new email is “already in use”? That address already has its own OpenAI account. Either log in to it, or pick a different new address (see Step 4).
- What if both inboxes are dead? Support can sometimes recover with proof-of-payment (last 4 digits of the card, invoice ID). Without inbox access or payment proof, the account is generally unrecoverable.