Backup & recovery
A wallet-backup storage checklist
By Jolly Ledger editorial · Published · Reviewed · 4 min read
Short answer
Store wallet backups offline where they are protected from unauthorized access and realistic physical damage, but remain reachable for recovery. Review location dependencies, passphrase access and share thresholds—not just the material holding the words.
A good storage plan balances two competing needs: other people should not casually obtain the backup, and you should not lose the ability to retrieve it. A heavy container or durable plate addresses only part of that problem. Access arrangements, labeling and the relationship between copies matter just as much.
Start with an inventory that contains no words
List the wallets or backup sets you maintain, their formats, and the locations or access routes associated with them. Use neutral identifiers rather than public labels advertising valuable crypto. Keep this inventory private: even without a phrase, a map of backup locations can help someone target you.
Do not gather every backup into one place merely to complete the list. Inspect locations separately when practical. Never add photographs, scans or voice recordings of the words to ordinary notes, email, cloud drives or password-reset correspondence. Convenience copies can undermine an otherwise careful offline plan.
Review damage and unauthorized access separately
Review before changing anything
- Check that every word or marking remains legible and in the right order.
- Consider realistic local risks: water, fire, corrosion, accidental disposal and building access.
- Review who can enter the location, including visitors, contractors and people with spare keys.
- Check whether a lock, container or access code depends entirely on a device you could lose.
- Avoid obvious packaging or labels that reveal the contents.
Paper and metal have different durability characteristics, but neither prevents someone from reading the backup. Assess the actual product and environment rather than assuming all metal survives all damage. A sealed envelope may help reveal some interference; an intact seal does not establish that nobody copied its contents.
Understand what each extra copy changes
A complete duplicate of a single-signature backup adds another recovery route and another place where the secret could be obtained. It is not automatically safer or worse; the locations and access controls determine the trade-off. Ten copies in the same drawer add little resilience against a damaged drawer.
For a multi-share backup, inventory distinct shares and thresholds. Copies of the same share do not satisfy additional threshold positions. Keep enough distinct shares outside any one failure zone for the recovery design to work, while considering whether an unauthorized person could reach enough locations. Do not improvise secret sharing by cutting an ordinary phrase into pieces.
Do not forget the separate dependencies
An optional passphrase needs its own protected recovery path. Keeping it only in memory can defeat an otherwise intact backup; storing it casually beside the phrase may remove the separation you intended. Trezor’s passphrase guidance stresses the consequences of losing that extra secret. Choose an access arrangement that matches your circumstances rather than adding complexity for appearances.
A family member also needs understandable directions about where to begin. Leave instructions without sharing secrets, explaining the role of the backup and how authorized access works. Do not assume that knowing a container’s location tells someone which device, format or account to use.
Close the loop with a check and a rehearsal
A readable backup can still be the wrong backup. Use an official non-destructive backup check where your device supports one. Then conduct a recovery rehearsal to test location access, compatible replacement options and missing records without resetting the working wallet.
Date the review and repeat it after a move, a changed household, a new backup or a changed access arrangement. Record only actions and outcomes, not secret contents. The objective is a usable recovery path with fewer hidden dependencies, not an impressive-looking storage setup.
Sources
- BIP-39: Mnemonic code for generating deterministic keys — Bitcoin BIPs
- SLIP-0039: Shamir’s Secret-Sharing for Mnemonic Codes — SatoshiLabs SLIPs
- Passphrase FAQ: What every passphrase user should know — Trezor
Reported facts are attributed to their sources. Spotted an error? Read our corrections approach.
Turn this into a preparation plan
Answer 16 calm questions about your setup. Get findings, scenario walkthroughs and a family briefing — on your own device, no account, no wallet connection, no recovery words.