You turn on two-factor authentication, the site shows you a list of backup codes, and asks you to save them somewhere safe. Most people take a screenshot, or click Download and never look at the file again. Then the phone breaks, and the codes are either on the broken phone or lost in a folder nobody can remember. Here's where backup codes should actually go, which accounts need more than one copy, and where they should never sit.
What Backup Codes Are For
Backup codes (some services call them recovery codes) let you sign in when your usual second step isn't available: your phone is lost, your number changed, or your authenticator app was wiped. Each code works once. Google gives you a set of 10 eight-digit codes, and GitHub gives you 16.
That makes them two things at once:
- Your way back in. Without them, losing your phone can mean a slow account recovery process, or no way back at all.
- A way past your 2FA. Anyone who has your password and one unused code can sign in as you. The second step you turned on stops protecting you.
So the goal isn't to hide the codes as deeply as possible. It's to keep them somewhere that survives losing your phone, and that needs more than your phone's passcode to open.
Step 1: List the Accounts That Have Codes
Before choosing where to keep anything, make a short list. Most people have backup codes for more accounts than they remember. Check the security settings of:
- Your main email. It resets the passwords for almost everything else, so it comes first.
- Your password manager, if you use one.
- Your Apple, Google or Microsoft account, the one your phone signs in with.
- Banking and payment apps that offer codes.
- Work and developer accounts (GitHub, your domain registrar, your website host).
- Crypto exchanges. Our guide to backing up crypto wallet files covers those separately.
- Social accounts you'd hate to lose.
If an account has 2FA on but you never saved its codes, most services let you view or generate them again in the same settings page. Generating a new set cancels the old one, which is useful if you've lost track of where the old ones went.
Step 2: Pick Where Each Set Goes
There's no single right answer. A password manager is fine for most accounts, paper is fine too, and the important thing is that the codes don't share a single point of failure with the thing they're meant to rescue you from.
| Where | Good for | Watch out for |
|---|---|---|
| Paper, at home | Your main email, your password manager, your phone's account. Survives any device loss and can't be hacked remotely | Fire, a move, or a family member throwing it out. Label it clearly and keep it with your other important papers |
| Password manager | Most everyday accounts. GitHub's own docs recommend it for recovery codes | Never the password manager's own codes, and not the email that resets it: you'd need to be signed in to read them |
| Encrypted file or vault | People who'd rather keep a digital copy that isn't in their password manager, or want a second copy of the paper list | You need to remember the vault's own lock and set up its recovery |
| Encrypted USB drive | A second, offline copy kept somewhere other than your home | Drives fail. Check it opens once a year |
| Trusted person | A sealed copy of the most important codes, for emergencies | Only someone you'd trust with the account itself |
Google's own help page suggests keeping a printed copy "where you keep your passport or other important documents". For the two or three accounts that unlock everything else, that's good advice: keep two copies in two different places, so one lost bag or one dead phone doesn't take both.
Step 3: Clear Out the Copies You Didn't Mean to Keep
Backup codes are a lot like passport scans: the danger is often the copies you forgot about. Look for:
| Where | Why it's a problem | What to do |
|---|---|---|
| Screenshots | They sit in your photo library, open with your phone's passcode and usually sync to a cloud photo backup | Delete them, then empty Recently Deleted or Trash |
| Downloads folder | Google names its file Backup-codes- plus your username, and it stays in Downloads until you move it | Search for "Backup-codes", move or print it, then delete the original |
| Email to yourself | The codes sit in your inbox, your sent folder and on the mail provider's servers. And if this is the email account you're locked out of, they're no help | Delete both copies and empty the mail trash |
| Plain notes apps | An unlocked note opens for anyone who has your phone unlocked, and syncs to every device | Move the codes, then delete the note |
| Desktop text files | Easy to back up by accident into a cloud folder, unencrypted | Move them into an encrypted file, or print and delete |
If you find a set of codes you're not sure is current, generate a fresh set in that account's settings. The old codes stop working, and you only have to keep track of the new ones.
Step 4: Keep the Codes Current
Backup codes go stale in quieter ways than passwords do:
- Cross off each code you use. Google's help page suggests marking used codes, since each one works only once.
- Replace every copy when you generate a new set. The old set stops working, so a paper copy of old codes is worse than useless: it looks like a way back in, and isn't.
- Recheck once a year. Make sure the paper copy is where you think it is, the encrypted file still opens, and every account on your list still has codes.
If you lose your phone before you've sorted this out, our guide to what happens to your data when your phone is stolen covers the first steps.
Where Backup Codes Fit With Everything Else
Backup codes belong with your other "keys to the kingdom": recovery phrases, license keys, and scans of the documents that prove who you are. Our important documents checklist covers where those originals belong, and password managers vs. secure vaults explains which kind of tool suits which kind of file.
Keep a Copy in Vaultine
If you want a digital copy that isn't in your password manager and isn't sitting in a screenshot, Vaultine is an encrypted vault for iPhone, Android, Mac and Windows. Import the downloaded codes file, or a photo of your paper list, and it's encrypted on your device, opening only with the vault's own PIN or pattern. Then delete the original from Downloads or your photos. Set up your recovery phrase when you create the vault, and keep that on paper, away from the vault itself.



