How to fix auth/email-already-in-use in Firebase

FirebaseBEGINNERLOWUpdated Dec 22, 2025· 291 views

This error occurs when a user tries to create an account with an email that already exists in your Firebase project. Learn how to detect this error, prompt users to log in instead, and check for existing accounts before sign-up.

Quick fix

Fixes auth/email-already-in-use

import { createUserWithEmailAndPassword } from 'firebase/auth';

createuserWithEmailAndPassword(auth, email, password)
  .then((userCredential) => {
    console.log('User created:', userCredential.user);
  })
  .catch((error) => {
    if (error.code === 'auth/email-already-in-use') {
      console.log('Email already in use!');
    }
  });
  1. Check the error code in your catch block
  2. Display a user-friendly error message
  3. Pre-check for existing accounts before sign-up
  4. Provide a login option for existing users
firebase — error
import { createUserWithEmailAndPassword } from 'firebase/auth';
createuserWithEmailAndPassword(auth, email, password)
  .then((userCredential) => {
    console.log('User created:', userCredential.user);
  })
  .catch((error) => {
    if (error.code === 'auth/email-already-in-use') {
      console.log('Email already in use!');
    }
  });
auth/email-already-in-use

What this error means

The "auth/email-already-in-use" error is Firebase's way of preventing duplicate accounts with the same email address. When a user attempts to create a new account using `createUserWithEmailAndPassword()` with an email that is already registered in your Firebase authentication database, Firebase blocks the operation and throws this error. This is a protective measure to maintain data integrity and prevent confusion from multiple accounts sharing the same email.

Typical symptoms

  • Sign-up form displays error message after submitting email and password
  • User receives "That email address is already in use!" or similar message
  • New account creation fails silently without clear feedback
  • Users attempt to create multiple accounts with the same email address
  • CI/CD tests fail when trying to create test users with duplicate emails

Common causes

  1. User previously registered an account and forgot about it
  2. User is trying to create a new account instead of logging in
  3. Multiple sign-up attempts with the same email in rapid succession
  4. Test data or seed scripts creating duplicate user records
  5. Email address was used with a different authentication method (Google Sign-In, Facebook, etc.) and user is trying email/password

How to fix "auth/email-already-in-use"

1Check the error code in your catch block

When calling createUserWithEmailAndPassword(), wrap it in a try-catch block or add a .catch() handler to detect the error:

javascript
import { createUserWithEmailAndPassword } from 'firebase/auth';

createuserWithEmailAndPassword(auth, email, password)
  .then((userCredential) => {
    console.log('User created:', userCredential.user);
  })
  .catch((error) => {
    if (error.code === 'auth/email-already-in-use') {
      console.log('Email already in use!');
    }
  });
2Display a user-friendly error message

Show the user that the email is already registered and offer them options:

javascript
if (error.code === 'auth/email-already-in-use') {
  setErrorMessage('This email is already registered. Please sign in instead.');
  // Optionally show a button to redirect to login page
}
3Pre-check for existing accounts before sign-up

Use fetchSignInMethodsForEmail() to check if an email exists BEFORE attempting to create the account:

javascript
import { fetchSignInMethodsForEmail } from 'firebase/auth';

async function handleSignUp(email, password) {
  try {
    const methods = await fetchSignInMethodsForEmail(auth, email);
    
    if (methods.length > 0) {
      setErrorMessage('This email is already registered.');
      return;
    }
    
    // Safe to proceed with account creation
    await createUserWithEmailAndPassword(auth, email, password);
  } catch (error) {
    console.error('Sign-up error:', error.message);
  }
}
4Provide a login option for existing users

When the error occurs, give users an easy way to sign in instead:

javascript
if (error.code === 'auth/email-already-in-use') {
  return (
    <div>
      <p>This email is already registered.</p>
      <button onClick={() => navigateTo('/login')}>Sign In</button>
      <p>or try signing up with a different email</p>
    </div>
  );
}
5Handle linked authentication providers

If a user registered with Google Sign-In but tries to sign up with email/password using the same email, you'll get this error. Handle this by offering to link accounts:

javascript
if (error.code === 'auth/email-already-in-use') {
  // User can sign in with the existing method (e.g., Google)
  setErrorMessage(
    'This email is already associated with another sign-in method. Please sign in with that method.'
  );
}

Advanced notes

Consider enabling email enumeration protection in your Firebase Console security settings. This prevents bad actors from discovering which emails are registered by catching all errors with a generic message instead of revealing whether an email exists. However, this will make your app's error handling less specific. For test environments, use different email addresses for each test run (e.g., test-${Date.now()}@example.com) or delete test users between runs. Some SDKs may return email-already-in-use when attempting to link credentials with linkWithCredential() - ensure your app logic doesn't assume linking with the same email will always succeed.

Frequently asked questions

What does "auth/email-already-in-use" mean?
The "auth/email-already-in-use" error is Firebase's way of preventing duplicate accounts with the same email address. When a user attempts to create a new account using createUserWithEmailAndPassword() with an email that is already registered in your Firebase authentication database, Firebase blocks the operation and throws this error. This is a protective measure to maintain data integrity and prevent confusion from multiple accounts sharing the same email.
How do I fix "auth/email-already-in-use"?
This error occurs when a user tries to create an account with an email that already exists in your Firebase project. Learn how to detect this error, prompt users to log in instead, and check for existing accounts before sign-up.
What causes "auth/email-already-in-use"?
User previously registered an account and forgot about it User is trying to create a new account instead of logging in Multiple sign-up attempts with the same email in rapid succession
Is the "auth/email-already-in-use" error serious?
It is a low-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading