ChatGPT Email Change Stuck in Verification Loop

You started changing the account email, got logged out, and now neither the old nor new email lets you back in. The verification link is the only way through. Recover without losing chats.

You changed your ChatGPT account email in Settings, the page told you to check the new inbox to confirm, and somewhere in the middle of that flow you got logged out. Now logging in with the old email fails (“invalid credentials”), logging in with the new email fails (“account not found”), and the verification email from the new address is the only thread holding the account together. This stuck state is common because email changes in ChatGPT are a two-phase commit: the new address must verify before the old one is fully invalidated, and any session interruption between those phases lands you in limbo. The fix is to find the verification email, or trigger a re-send through a careful login dance.

Common causes

Ordered by hit rate, highest first.

1. Verification email is sitting in spam or a sub-folder

The verification mail comes from noreply@tm.openai.com and many providers (Gmail Promotions, Outlook Focused, corporate Mimecast filters) hide it from the main inbox.

How to judge: Search the new inbox for “OpenAI” or “verify” with All Mail / All Folders scope. Includes spam, promotions, archive.

2. Session was logged out mid-flip

ChatGPT logs you out the moment the change is initiated. If you accept that prompt without first confirming you can receive mail at the new address, you can be stuck until you do.

How to judge: Try to log in with the OLD email — if it says “no account exists” but you just used it yesterday, the flip already happened.

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. The system refuses the change but the UI may already have logged you out.

How to judge: Try logging in with the new email. If it lets you in but you do not see your chats, that is the pre-existing account. The change was rejected silently.

4. Sign-in method conflict (Google vs email)

You originally signed in with Google for you@gmail.com, and you tried to change to you@company.com which was supposed to use password auth. The system gets confused between sign-in methods.

How to judge: At the login page, try Continue with Google with the new email; if that lets you in but the chats are gone, sign-in method got swapped.

The verification link is a one-time token tied to the session that requested it. Clicking it from a different browser or after closing the session can invalidate it.

How to judge: The verification link page shows “this link is invalid” rather than letting you confirm.

Some enterprise mail systems rewrite links for safe-browsing. The rewritten link no longer matches OpenAI’s expected token and verification fails.

How to judge: Hover the link in the verification email; if it points to safelinks.protection.outlook.com or similar, it has been rewritten.

Before you start

  • Confirm you have working access to BOTH the old email inbox and the new email inbox. If one is gone, recovery is much harder.
  • Decide which email you actually want as your long-term primary.
  • Disable any aggressive mail filters or rewrite proxies for the next hour.
  • Have your password manager open; you may need both old and new credentials.

Information to collect

  • Old email address.
  • New email address.
  • Sign-in method used (Google, Apple, email/password, SSO).
  • Approximate time you initiated the change.
  • Screenshot of the current error message.
  • Any verification email headers (especially the From and the verification URL host).
  • Whether either email is on a corporate Microsoft 365 / Mimecast / Proofpoint domain.

Step-by-step fix

Step 1: Hunt for the verification email everywhere

In the new inbox, search “OpenAI” across ALL folders. In Gmail use from:openai.com in:anywhere. In Outlook search the whole mailbox. Check Junk, Spam, Promotions, Archive, and any custom rules folder.

Use the same browser and same network you initiated the change from. Verification tokens are session-aware. If you switched devices, go back to the original device first.

Go to chat.openai.com → Log in → enter NEW email → click “Resend verification email.” A new token will be issued and the old one invalidated. Click the fresh link within 30 minutes.

Step 4: If new email already had an account, decide consolidation

The change was rejected. You have two accounts. Options:

  • Keep the original; abandon the change. Log in with OLD email; the change was never committed despite the UI suggesting otherwise.
  • Keep the new account; export chats from the old account via Settings → Data controls → Export.

Step 5: For corporate mail rewriting, try a personal forwarding address

Forward the verification email from your corporate inbox to a personal Gmail. Open Gmail in a clean browser. The forwarded link may retain the original URL if the rewrite only happened at the gateway preview.

Step 6: Use password reset as a backdoor

If you set a password (not Google/Apple SSO), go to chat.openai.com → Forgot password? → enter NEW email. A reset email arrives that effectively confirms the address. After resetting, log in with the new email.

Step 7: Contact support with both addresses verified

Open help.openai.com:

Subject: Email change stuck in verification loop

Old email: you@a.com
New email: you@b.com
Change initiated at: 2026-05-24 10:15 PT
Sign-in method: Google / email-password / SSO
Error: cannot log into either; verification email not received

I have access to both inboxes. Please either:
(a) roll back the change to the old email, or
(b) force-complete verification on the new email.

Response is usually 24-72 hours; do not initiate another change in the meantime.

Verify

  • You can log into chat.openai.com with the chosen email and see your historical chats.
  • Settings → Account shows the desired email as the primary.
  • A test password reset email arrives at the new address.
  • No “verify your email” banner is visible at the top of the app.

Long-term prevention

  • Never change email from a flaky network or while traveling; the verification dance benefits from a stable session.
  • Before clicking Change, send yourself a test email at the new address from a known sender to confirm the inbox delivers.
  • Choose one sign-in method (Google OR email/password) and stick to it; mixing causes mid-flip confusion.
  • Avoid changing to a corporate email if you might leave the company; you will lose access when IT disables the mailbox.
  • Keep the old inbox alive for at least 30 days after the change in case verification needs to retry.

Common pitfalls

  • Initiating a second email change while the first is pending — both can fail and leave the account orphaned.
  • Clicking verification links from a Slack or Teams unfurl preview; previews can pre-consume the token.
  • Assuming the old email is still valid for login after seeing the “we sent you a verification” message; it is not after the new email confirms.
  • Letting the verification email sit overnight; tokens often expire within 24 hours.
  • Using “Continue with Google” to sign in after you changed the auth from Google to password; the Google flow creates a fresh account instead of recovering.

FAQ

  • How long is the verification link valid? Typically 24 hours; some emails expire in 30 minutes.
  • Will my chat history transfer to the new email? Yes — changing email does not move your account; it just renames it. History stays.
  • Can I cancel an email change mid-flow? Only by completing or letting the verification expire. Once expired, the account reverts to the old email.
  • What if both inboxes are dead? Support can sometimes recover with proof-of-payment (last 4 digits of card, invoice ID). Otherwise the account is unrecoverable.
  • Is this different from a password reset loop? Yes. Password reset is about credentials; this is about which email owns the account.

Tags: #ChatGPT #account #Troubleshooting #Debug