To back up your 2FA codes securely, keep three things: each service's one-time recovery codes, an encrypted export of your authenticator accounts, and a safe place for both that is separate from the phone or computer you use every day. If you lose your device and have none of these, you may have to go through slow account recovery with each service, and some accounts cannot be recovered at all.
This guide explains what actually needs backing up, how to store it, and the mistakes that quietly defeat a backup.
Why 2FA needs its own backup
Your password lives in your head or a password manager. Your second factor lives on a device. Phones get lost, dropped in water, stolen and wiped. If the authenticator codes were only on that phone, you have lost the second factor for every account at once.
The sign-in then needs a way around the missing code, and that way around is exactly what attackers also try to use. OWASP's Multifactor Authentication Cheat Sheet notes that recovery must not become a bypass, and that issuing single-use recovery codes when MFA is first enabled is a recommended practice. In other words, services deliberately make recovery inconvenient. You want to prepare before you need it.
The three things worth backing up
1. Recovery codes (per service)
When you enable 2FA, many services show a list of one-time recovery codes. Each works once in place of an authenticator code. GitHub's help pages, for example, list recovery codes as the first option when you lose your 2FA credentials.
Save them at setup time, because some services show them only once. Print them or store them in an encrypted note. Do not leave them in a screenshot sitting in your camera roll.
2. An encrypted export of your authenticator
An export contains the secret key for every account, so it can recreate all your codes on a new device. That makes it powerful and sensitive in equal measure: whoever holds an unencrypted export can generate your codes.
Always export to an encrypted file. In 2Fa Live, backups are exported as encrypted files, and on restore the file is checked for a valid structure before anything is imported. As with the vault itself, there is no server copy, so there is no password-reset email if you forget the passphrase. Choose a passphrase you can recover from your password manager.
3. A record of the setup keys (optional, for critical accounts)
For accounts you cannot afford to lose, such as your main email or an exchange, some people store the original setup key, the text shown beside the QR code, in a password manager entry. This is a deliberate trade-off: the secret and the password then sit in the same place, which weakens the "two" in two-factor. If you do it, keep it to a few critical accounts and protect the manager with its own strong 2FA.
Where to keep the backups
| Backup | Good place | Avoid |
|---|---|---|
| Recovery codes | Printed copy in a safe, or an encrypted note | Plain email, screenshots, unlocked notes app |
| Encrypted export file | Encrypted cloud folder or an offline drive | A shared folder, an email attachment, the same device |
| Passphrase for the export | Password manager, or written down and stored apart | Next to the file itself |
The principle is separation. The file and the key to open it should not live in the same place. And at least one copy should survive the loss of your phone, which means it cannot live only on the phone.
A simple routine
- Enable 2FA on the account and save the recovery codes immediately.
- Add the account to your authenticator by scanning the QR code or typing the setup key.
- Export an encrypted backup right after, so the new account is included.
- Store the file and the passphrase separately.
- Test once. Restore the backup in a different browser or device and confirm the codes match the service. A backup you have never restored is a hope, not a backup.
- Repeat when you add accounts. Make it part of setting up any new 2FA.
Mistakes that defeat a backup
- Keeping the only copy on the same device. If the phone goes, so does the backup.
- Storing an unencrypted export in cloud storage or email. It contains live secrets.
- Forgetting the passphrase. An encrypted backup without its passphrase is unreadable by design.
- Never refreshing it. Accounts added since the last backup are missing.
- Using SMS as your only fallback. Phone numbers can be lost or taken over, and it moves the weak point rather than removing it.
- Skipping the test. Format and passphrase mistakes show up only on restore.
What about moving to a new phone?
A backup is also your migration path. When you change devices you restore from your encrypted export, or use an export feature in your old app. Some authenticators, including Google Authenticator, can also sync to your account. Their help pages describe an export-by-QR option and a sync option. For the step-by-step version, read how to move 2FA codes to a new phone.
If it is already too late, here is how to recover 2FA accounts after losing your phone.
How 2Fa Live handles your data
2Fa Live is a browser authenticator. Your secrets are encrypted in your browser with your passphrase and are never sent to a server, which is why the backup file is yours to manage and nobody else holds a copy. You can read the details on the is it safe page and in our privacy-first design.
Key takeaways
- Back up three layers: recovery codes, an encrypted export, and a safe place that is not your phone.
- Never store an unencrypted export. It holds the keys to your codes.
- Store the file and its passphrase separately, and test a restore at least once.
- Update the backup every time you add an account.
Tags: 2fa backup, recovery codes, encrypted backup, authenticator backup