App Finishers

Fix guide · updated 2026-11-15

Supabase "User already registered" error

AuthApiError: User already registered · user_already_exists · 422

Someone tries to sign up and Supabase answers "User already registered". Or, stranger: the sign-up seems to work, but the confirmation email never comes. Both happen when the email already has an account in your project. Which one you get depends on one setting, and neither tells the person what to do next. Here's how Supabase decides, and what your form should show.

What the error means

We read the sign-up code in Supabase Auth (internal/api/signup.go). When someone signs up with an email that already has a confirmed account:

If the account exists but was never confirmed, there's no error either: with "Confirm email" on, Supabase sends the confirmation email again and leaves the account as it was (see case 4).

1. The person already has an account

The usual case: they signed up a while ago and forgot, or they landed on the sign-up page when they meant to sign in. Nothing is broken. Your form just has to say so and offer the way in: sign in, or reset the password.

With "Confirm email" on, you can still tell, because the made-up user has no identities:

const { data, error } = await supabase.auth.signUp({ email, password });

if (error?.code === 'user_already_exists') {
  // "Confirm email" is off: the email already has an account
} else if (!error && data.user && data.user.identities?.length === 0) {
  // "Confirm email" is on: the email already has an account, and no email was sent
} else if (!error) {
  // a real sign-up: "Check your inbox" (or signed in, if confirmation is off)
}

Showing "This email already has an account" does tell a stranger that the address is in use. Most apps accept that. If yours shouldn't, show "Check your inbox" in every case and let existing users find the reset link on the sign-in page.

2. "Check your inbox", and nothing arrives

This is the silent version of case 1. Your app showed "Check your inbox" because signUp returned no error, but Supabase sent nothing, since the account already exists and is confirmed. The person waits for an email that will never come. Check identities as in the code above, and send them to sign in instead.

If the account is not confirmed and the email still doesn't come, that's a delivery problem, not this one: see "Email not confirmed" and "email rate limit exceeded".

3. They signed up with Google or a magic link before

An account created with Google, GitHub or a magic link counts as confirmed. So an email-and-password sign-up with the same address lands in case 1, even though the person never chose a password. They can sign in the way they did the first time, or set a password through your reset flow: the code is in our guide on "Invalid login credentials" (case 2). If your app offers both, say it on the sign-up form: "Signed up with Google? Use the Google button."

4. Signing up again doesn't change the password

If the first sign-up was never confirmed and the person signs up again with a different password, Supabase sends the confirmation again but keeps the first password. Its code says it won't update the account "because we can't be sure of their claimed identity". After they confirm, the new password fails with "Invalid login credentials". The way out is a password reset.

And if they sign up again within 60 seconds, they get "For security purposes, you can only request this after N seconds." instead: see "email rate limit exceeded".

5. "A user with this email address has already been registered"

Same situation, other door. This message (HTTP 422, code email_exists) comes from admin.auth.admin.createUser when you create a user from your server with an email that's taken, and from supabase.auth.updateUser({ email }) when someone changes their email to an address another account uses. In a seed script, treat it as "already there" and move on. In an email-change form, tell the person that address is already in use.

Find your case in two minutes

In the Supabase dashboard of the project your app really uses, open the SQL editor and run:

select email,
       email_confirmed_at,
       created_at,
       coalesce(encrypted_password, '') <> '' as has_password,
       raw_app_meta_data->>'provider' as signed_up_with
from auth.users
where lower(email) = lower('person@example.com');

If an AI tool built your app

Give your AI tool this prompt:

In the sign-up form, after supabase.auth.signUp: if error?.code is 'user_already_exists', or if there is no error and data.user.identities is an empty array, show "This email already has an account." with a "Sign in" link and a "Forgot password?" link that calls supabase.auth.resetPasswordForEmail(email, { redirectTo: window.location.origin + '/reset' }). In that case don't show "Check your email", since no email was sent. If the app also has Google sign-in, add the line "Signed up with Google? Use the Google button." Don't change anything else.

If the app has no /reset page yet, our guide on "Invalid login credentials" has the prompt that adds it.

Not quite your error?

Still stuck?

If the SQL shows an account for someone who says they never signed up, look at created_at and signed_up_with: an import, a seed script or an invite may have created it before they arrived. Invited people should use the link in their invite email, or the reset flow, rather than the sign-up form.

Other Supabase problems? See Supabase fixes.