Supabase "User already registered"? Handle Repeat Signups the Right Way

Updated 19 Oct 2026

Check your app now: free 30-second health check

Paste your live URL. We'll show what visitors and Google actually see. No signup.

Passive check only. We never submit forms or log in.

Someone fills in your signup form with an email that already has an account. Depending on your Supabase settings, one of two things happens:

  • The form shows User already registered (HTTP 422, error.code = user_already_exists).
  • Or, more confusingly, nothing goes wrong at all: the form says "Check your inbox", no error comes back, and no email ever arrives.

Both are expected Supabase behaviour, not a bug in your project. But both cause real problems on sites built with Lovable, Bolt, v0, Replit and Cursor: returning customers get stuck on a "check your inbox" screen forever, or your form shows a raw error and a dead end instead of a "sign in instead" button.

This guide explains which response you get and why, how to tell them apart in code, and how to build a signup form that helps returning users without telling strangers who has an account.

Why Supabase answers in two different ways

Supabase tries not to reveal which email addresses have accounts on your site. If signup said "this email is taken" every time, anyone could type in a list of addresses and learn who your customers are. So the answer depends on your settings.

According to Supabase's signUp reference, when signUp() is called for an existing, confirmed user:

Your settingsWhat signUp() returns
Confirm email and Confirm phone both onNo error. A fake ("obfuscated") user object, session = null, and no email is sent
Either Confirm email or Confirm phone offError User already registered (user_already_exists, HTTP 422)

Note the phone setting. Supabase's docs say the Confirm phone setting counts even when you don't use phone sign-in at all. This is why two projects with the same email settings can behave differently.

There's a third case people miss: an email that signed up before but never confirmed. Then Supabase returns no error, sends the confirmation email again (subject to the normal email rate limits), and does not change the stored password. A Supabase maintainer confirmed this is deliberate: updating the password of an unconfirmed account would let someone else take it over.

Step 1: find out which case you're in

Open your live signup page in a private window with DevTools open (Network tab). Sign up with an email you know already has an account, then look at the signup request to /auth/v1/signup.

What you seeWhich case
HTTP 422, body contains user_already_exists / "User already registered"Confirmed user, and Confirm email or Confirm phone is off
HTTP 200, session null, user.identities is an empty array []Confirmed user, both confirmations on (obfuscated response)
HTTP 200, session null, user.identities has one entry, and a new confirmation email arrivesExisting unconfirmed user, or a genuinely new signup
HTTP 200 with a sessionA brand-new user and Confirm email is off

Then check your settings in the Supabase dashboard under Authentication, in the Email provider settings (Confirm email) and the Phone provider settings (Confirm phone).

Also check that your live site is calling the project you think it is: the host in the request URL is your project's address. A preview build pointing at one project and the published site at another is a common source of "but that email isn't in my users list". See Supabase Auth Broke After Deploy? The Usual Suspects, in Order.

Step 2: stop treating data.user as "signed up"

The most common bug in generated signup code is this:

const { data, error } = await supabase.auth.signUp({ email, password });
if (data.user) {
  // "Account created!" → redirect to dashboard
}

With confirmations on, data.user exists in every case above: the fake user, the unconfirmed user and the real new user. So the form happily shows "Account created" to someone who already has an account and will never receive an email.

Use data.session and error instead:

const { data, error } = await supabase.auth.signUp({
  email,
  password,
  options: { emailRedirectTo: `${window.location.origin}/welcome` },
});

if (error) {
  // Covers user_already_exists (422) when a confirmation setting is off
  showMessage(error.code === 'user_already_exists'
    ? 'You may already have an account. Try signing in, or reset your password.'
    : 'Something went wrong. Please try again.');
} else if (data.session) {
  // Confirm email is off and this is a new user: they're signed in
  goTo('/dashboard');
} else {
  // Confirm email is on: new, unconfirmed OR existing user
  showMessage('Check your inbox to confirm your email. Already have an account? Sign in or reset your password.');
}

That last message is the key. It is true for all three cases, it gives the returning user a way forward, and it reveals nothing about who has an account.

Step 3: decide whether to detect existing users at all

Many tutorials suggest this check:

if (data.user && data.user.identities && data.user.identities.length === 0) {
  // email already registered
}

It works today with confirmations on, and Supabase's own older docs and GitHub threads mention it. But think before you use it:

  • It undoes the protection. If the form says "this email is already registered", anyone can test addresses one by one. For a newsletter tool that may not matter. For a health, finance or dating site, it does.
  • It relies on a detail of the response. The fake user's empty identities array is not a documented contract you control.

A safer pattern for most sites: show the neutral message from Step 2, and put "Sign in" and "Forgot password?" links right under it. Returning users find their way; strangers learn nothing.

If you decide you do want an explicit "already registered" message, turn it into a deliberate product choice, add rate limiting or a captcha to the signup form, and never check by reading a public profiles table from the browser. A table anyone can read is a much bigger leak than the signup response.

Step 4: fix "Check your inbox" for people who never get an email

Returning users who already confirmed get no email from a repeat signup. If your form only says "Check your inbox", they'll wait, then try again, then give up. Fixes:

  1. Say more on the confirmation screen: "Didn't get an email? You may already have an account. Sign in or reset your password."
  2. Add a resend button for genuinely unconfirmed users:
await supabase.auth.resend({
  type: 'signup',
  email,
  options: { emailRedirectTo: `${window.location.origin}/welcome` },
});

For an already-confirmed address this sends nothing, which is fine: the screen already points them to sign in.

  1. Make sure new users actually get their emails. If brand-new signups also see no email, that's a delivery problem (default sender limits, spam folders, no custom email sender), not this one. See Sign-up emails not arriving? Fix auth mail.

Step 5: the user who signed up with Google

A common support email: "I signed up with Google, then tried to create a password account with the same email, and it says I'm already registered (or nothing happens)."

The account exists, confirmed, with a Google identity and no password. signUp() won't add a password to an existing account, by design. Your options:

  • Point them to the Continue with Google button. Put it on the signup page as well as the login page, with a line like "Signed up with Google before? Use the Google button."
  • If you want them to also have a password, let them use Forgot password?. A completed password reset sets a password on the existing account.

Don't try to "fix" this by deleting and re-creating the user, which can break rows in your own tables that point at the old user id.

Step 6: it says "already registered" but the user isn't in your list

If Supabase insists the email exists but you can't find it under Authentication → Users:

  • Different project. Compare the project address in the live site's network request with the dashboard you're looking at (Step 1).
  • Case and spaces. Supabase matches emails without regard to case. Trim spaces before calling signUp and use the same cleaning at login.
  • Search the right field. Search by the full address; a user created with a phone number or by an admin invite can still own that email.
  • Invited users. An admin invite creates the account before the person ever visits your signup page. They should use the invite link or reset their password, not sign up again.

Step 7: don't switch off Confirm email just to get the error

Turning off Confirm email does make Supabase return a clear User already registered. It also means anyone can sign up as any address without proving they own it and get signed in straight away. If your policies or emails trust the user's email address, that's a real risk. Treat Confirm email as a security setting and handle the neutral response in your form instead.

If you do run with it off (some internal tools do), handle 422 user_already_exists explicitly with a "Sign in instead" link rather than letting the raw error reach the page. Forms that swallow errors are a classic silent failure; see Form says thanks but nothing arrives? Test it live.

Quick checklist

  1. Sign up on the live site with an existing email; read the status, error.code and identities in DevTools.
  2. Check Confirm email and Confirm phone in the dashboard; both matter.
  3. Make sure the live site talks to the right Supabase project.
  4. Branch on error and data.session, never on data.user alone.
  5. Use one neutral "check your inbox, or sign in / reset password" message.
  6. Add a resend button and sign-in / reset links on the confirmation screen.
  7. Offer the Google (or other) button on the signup page for people who used it before.
  8. Don't expose who has an account through a public table or a loud "email taken" message unless you've decided to.

Signup is where new customers arrive, and these problems only show up for real people, after launch. The free 30-second health check shows which pages on your live site fail to load, which links are broken and what errors appear in the console. For ongoing coverage, FlowCanary offers Daily monitoring of your signup, login and checkout (in development; founding spots $19/month, price locked for life, full refund on request any time before it launches).

Further reading

FAQ

Why doesn't Supabase return an error when someone signs up with an existing email?

With Confirm email and Confirm phone both on, Supabase returns a fake user and sends nothing, so your signup form can't be used to find out who has an account.

How do I get the "User already registered" error back?

It appears when Confirm email or Confirm phone is off. But switching confirmations off weakens your signup, so handling the neutral response is usually the better fix.

Does signing up again change the user's password?

No. For an existing unconfirmed user, Supabase resends the confirmation email and keeps the original password. For a confirmed user it changes nothing.

How can I check if an email is already registered?

From your own side, look in Authentication → Users or query from a server function with the service role key. Avoid exposing that check to the public signup form.

Related guides

Run the free 30-second check

Back to the FlowCanary homepage

FlowCanary on SaaSHub