Where should I keep two-factor authentication backup codes?
Quick answer
For Google Account backup codes, print them and keep the paper somewhere safe, such as with important documents. Identify the account on the copy so you can recognize it later, and do not share the codes. Each code works once; creating a replacement set makes the previous set inactive. These instructions are specific to Google, so check another service’s guidance before applying the same rules. [S1]
The question, the details, the next step.
Where should I actually keep my two-factor authentication backup codes? I want them available if I lose access to my usual sign-in method, but I don’t want to leave them somewhere careless.
For Google Account backup codes, Google says you can print them and keep the paper somewhere safe, such as with important documents. Keep the account identification with the copy so you can tell what it belongs to later, and don’t share the codes. [S1]
The practical goal is to keep the paper findable by you while protecting it from casual viewing. A printed copy stored with important papers is one option supported by Google’s guidance. The supplied instructions cover Google Account codes, not every service’s backup codes.
What should I write on the page so I can recognize it, and can I keep codes for multiple services together?
Use a clear label on each copy that identifies the account. For example:
“Account: [identifier you recognize] Codes saved: [date]”
The bracketed text is a placeholder. Keep the codes themselves on the protected copy, not on an exposed label. If you store papers for multiple services together, use separate, clearly identified sheets or sections so you can distinguish the sets. Google’s guidance supports identifying its codes with the Google Account they belong to. [S1]
Don’t assume another service has the same rules: this source is specific to Google. Check each service’s own instructions before relying on its codes.
What if I use one code, or create a fresh set later? How do I avoid relying on an old printout?
For Google, each backup code works once. Google also says that creating a replacement set makes the previous set inactive. [S1] If you create a new set, update the stored copy and stop relying on the old one. You could note “Set saved: [date]” on the new copy to help distinguish it from an earlier printout; that date is just an organizing aid, not a stated Google requirement.
The source does not establish rules for other providers, so check their instructions rather than assuming their codes behave the same way.
Can you give me a final checklist before I put the codes away?
Use this checklist for Google Account backup codes:
- Print the codes and choose a safe place, such as with important documents. [S1]
- Identify the account on the copy so you can recognize it.
- Keep the codes private; don’t share them. [S1]
- Remember that each Google code works once. [S1]
- If you create a replacement set, update the stored copy because the previous set becomes inactive. [S1]
- For another service, check its own instructions before applying Google’s rules.
Example record: “Account: [identifier] | Codes saved: [date] | Stored with: [important documents].” Keep the actual codes on the protected copy, rather than in an exposed label.
A practical checklist
Print Google Account backup codes and keep the paper somewhere safe, such as with important documents. [S1]
Label the copy with an account identifier you will recognize.
Do not share the codes. [S1]
Treat each Google backup code as one-time use. [S1]
Update the stored copy after creating a replacement set; the previous Google set becomes inactive. [S1]
Check other services’ instructions instead of assuming Google’s rules apply.
A few more useful answers
Can I use this advice for backup codes from any service?
The cited instructions are for Google Account backup codes only. They do not establish the rules for other providers, so check the relevant service’s own guidance.
Can I use a Google backup code more than once?
No. Google says each backup code works once. [S1]
What happens to my old Google codes if I create a new set?
Google says creating a replacement set makes the previous set inactive, so update the stored copy and stop relying on the old one. [S1]
Sources
References used for this guide.
- [S1] Sign in with backup codes support.google.com · Checked