Store Recovery Codes So They Still Exist During an Emergency

A recovery code stored only on the phone it is meant to replace is not much of a recovery plan. Put codes somewhere reachable when the primary device, password manager, or cloud account is unavailable.

Recovery codes belong outside the account and outside the device they are meant to rescue. Use two different failure domains: for example, a printed copy in a secure location and an encrypted digital copy outside the protected account.

Choose storage locations before generating codes so plaintext does not linger in Downloads. Have a printer, encrypted container, or secure document location ready.

Store codes outside the failure

Generate a fresh set after confirming your normal sign-in works. Generate codes only after normal two-factor sign-in works. Note that creating a new set can invalidate every previous code.

Use two different kinds of storage

1. Print or write one copy for a secure physical location

   Print one copy for a secure document location. The paper should identify the service but does not need the account password beside it.

2. Store an encrypted digital copy in a separate protected system

   Keep an encrypted digital copy outside the account it recovers. A file in that account’s own cloud storage may be unreachable during lockout.

3. Label the service and generation date without adding the password

   Mark single-use codes after use without photographing the whole sheet. Replace the set if you cannot tell which codes remain valid.

4. Replace the set after any code is exposed or the service regenerates it

   Regenerate immediately after accidental sharing, an unencrypted upload, or loss. Treat recovery codes with the same care as passwords.

A sealed paper copy can survive a dead phone and cloud lockout, while an encrypted digital copy is easier to update. Keeping both in the same backpack defeats the benefit of using two forms.

Know when a set becomes invalid

• A screenshot in the same phone is a fragile backup.
• Codes may be single-use.
• Do not email plaintext codes to yourself.

Generate a new set whenever codes appear in a shared folder, unencrypted screenshot, sent message, or lost piece of paper.

A screenshot is usually not enough

Check current menu names, limits, and recovery language against “Sign in with backup codes” and “Set up a recovery key for your Apple Account” before acting; platform behavior can change after publication, and each source should be used only for the claim it actually supports.

Google says its backup codes are single-use and that generating a new set makes the old set inactive.

Apple warns that an Apple Account recovery key must be kept outside services that become inaccessible when the account is locked.