Recover Discord After Losing Your Authenticator and Backup Codes
Locked out after losing your authenticator and backup codes? Here is the recovery sequence to try first.
Is this your situation?
You lost your phone with the authenticator app and you cannot find your backup codes. You want to get back into your Discord account without losing it for good.
Do this first
Check any other device still signed into Discord first. Do not reset your password before checking for saved backup codes, because a code is what gets you past the authenticator step. Look for a file named discord_backup_codes.txt or a screenshot of the codes before contacting support.
Which situation is yours?
- You have backup codes saved somewhere: use one to log in.
- You are already logged in on another device: disable MFA there, then re-add it.
- You set up SMS as well: request a code sent to your phone instead.
- You have no backup codes and no other session: support cannot remove your MFA.
- You used Google Authenticator: follow Google's own recovery guide.
- You never saved backup codes at all: support cannot generate new ones.
How Discord handles this
- Discord is unable to remove MFA or issue new backup codes if you do not have access to your backup codes.
- Backup codes may be saved as a file called discord_backup_codes.txt or as a screenshot in your photo gallery.
- If you signed up for MFA through Google Authenticator, follow Google's own guide for that app.
- Discord's support team is unable to generate new backup codes on your behalf.
- If you did not save your backup codes, Discord Support will not be able to remove MFA from your account.
Which recovery path is yours?
- Do you have a backup code saved anywhere? After logging in with a backup code, you can remove MFA from your account so you can add it back later.
- Are you still logged into Discord on another device? If already logged into your Discord account on a device, you can disable MFA and then re-add it.
- Did you also set up SMS MFA on this account? You can receive an SMS code instead of MFA or use a backup code to log in.
- Do you have no backup codes, no other session, and no SMS set up? Discord is unable to remove MFA or issue new backup codes if you do not have access to your backup codes.
What not to do
- Resetting your password before checking for backup codes If locked out of an account, a user can use a backup code to recover and reconfigure the account past MFA.Why it happens: The password field appears first, so it looks like the first move.
- Assuming support can generate new backup codes Discord's support team is unable to generate new backup codes on a user's behalf.Why it happens: Other platforms sometimes offer this, so the assumption carries over.
- Contacting support without having saved backup codes at all If a user did not save their backup codes, the Discord Support team will not be able to remove MFA from their account.Why it happens: Backup codes are shown once at setup and simple to skip saving.
What to have ready
- Other signed-in devices Check if you are logged into Discord elsewhere. If not logged in elsewhere, check for saved backup codes.
- Saved backup codes file Look for discord_backup_codes.txt. Backup codes could be saved as a txt file.
- Photo gallery screenshot Search your gallery for the codes. Backup codes could be saved as a screenshot in the gallery.
- SMS MFA setup Check if a phone number is enrolled. If SMS MFA is set up, use it to log in.
- Google Authenticator use Confirm which app you used. Google Authenticator users should follow Google's own guide.
- Password manager Check if a passkey is saved there. Passkeys can be stored in a password manager.
Stop this happening again
After you regain access, generate new backup codes and store them somewhere you will find again. Set up two-factor authentication with backup codes properly the first time to avoid repeating this.
Quick reference
| Situation | What happens |
|---|---|
| You have a saved backup code | After logging in with a backup code, you can remove MFA from your account so you can add it back later. |
| You are logged in elsewhere | If already logged in on that device, you can disable MFA and re-add it. |
| You have SMS MFA set up | You can receive an SMS code instead of MFA to log in. |
| You used Google Authenticator | Follow Google's own guide for recovering the app. |
| You have no codes and no other session | Discord is unable to remove MFA or issue new backup codes. |
| You never saved backup codes | Support will not be able to remove MFA from the account. |
Keeping track of who has access
Losing both an authenticator and its backup codes is a preventable kind of lockout. Delvia keeps a record of who holds access and which recovery methods are in place, so the gap shows up before it becomes a lockout. That record is what turns a scramble to recover an account into a short, known step.
Was this helpful?