Wallet backup security is about making sure you can always regain access to your crypto assets while making sure nobody else can. A backup that is too fragile leads to loss, and a backup that is too exposed leads to theft, so good design has to address both at once.
This article covers how to plan, create, store, and test backups for self-custody wallets. The step-by-step process of restoring from a backup, and the scams that target people during recovery, are covered in a companion article on wallet recovery security.
Backups Protect Against Loss, Not Just Theft
Many security discussions focus on attackers, but owners lose access to self-custody wallets through ordinary events far more often than headlines suggest. A phone falls into water, a hardware wallet fails, a house floods, or a passphrase is simply forgotten.
In self-custody, nobody else holds a copy of your keys. There is no password reset link and no customer service team that can restore access. If every copy of the information needed to rebuild the wallet disappears, the assets remain on the blockchain but become permanently unspendable.
A backup is therefore insurance against your own devices and circumstances. It must be complete enough to rebuild the wallet without the original device, durable enough to survive years of storage, and protected well enough that finding it does not hand a stranger your funds.
What a Complete Wallet Backup Contains
A frequent mistake is assuming that the seed phrase alone is the whole backup. For many setups it is the most important part, but restoring successfully can depend on several other details that people rarely write down.
- The seed phrase, written exactly and in the correct order, with each word numbered.
- Any BIP-39 passphrase, recorded with exact spelling, spacing, and capitalization.
- The wallet software or device type, plus the derivation path and address type in use.
- For multisignature wallets, every co-signer’s extended public key, the threshold, and the wallet descriptor or configuration file.
- Notes on which networks and accounts hold assets, so nothing is overlooked during a restore.
Only the first two items are secret. The rest are configuration details that cannot spend funds, but without them a correct seed may restore to an empty-looking wallet, causing delays, confusion, and sometimes rash decisions.
Balancing the Risk of Loss Against the Risk of Theft
Every backup decision trades one risk for another. Keeping a single copy in one hidden place minimizes exposure but makes loss likely if that place burns or is forgotten. Keeping many copies everywhere reduces loss but raises the chance one is found.
A useful exercise is to list realistic threats for your situation: fire, flood, burglary, a curious housemate, a targeted attacker, illness, and death. Then ask which backup arrangement survives the most likely of those events without becoming easy for the others to exploit.
The right answer depends on the value involved and your circumstances. A small balance may justify one well-hidden paper copy, while a larger holding may justify durable metal copies, several locations, and a design in which no single location holds the complete secret.
Write the result down as a short threat list stored with your other non-secret notes. Revisiting it during reviews shows whether a move, a new housemate, or a larger balance has changed which risks matter most.
Choosing Durable Backup Media
Paper is easy to use and fully offline, but it is vulnerable to fire, water, fading ink, and pests. If you use paper, choose acid-free stock and a pencil or archival pen, and protect the sheet in a sealed sleeve away from moisture and sunlight.
Metal backups, such as stamped plates, engraved tiles, or capsules with letter tiles, are designed to survive fire and flooding far better than paper. Check that the product uses a corrosion-resistant metal and that the letters cannot slide out of position or wear away over time.
Whatever the medium, avoid storing the secret parts on general-purpose electronics. USB drives and memory cards degrade, may become unreadable after years in a drawer, and can be copied silently by anyone who briefly holds them.
Store the medium where temperature and humidity stay moderate, and inspect it during reviews for corrosion, smudging, or loose parts. A durable medium can still fail if it sits somewhere it slowly degrades unnoticed.
How Many Copies and Where to Keep Them
Location planning determines whether a backup actually survives a disaster. Three questions guide the decision: how many copies to make, how far apart to keep them, and who else can reach them.
Redundancy Without Overexposure
Two or three copies of the secret material is a common choice for individuals, because one copy offers no protection against a single fire or theft. Each extra copy, though, is another place an attacker might find it. Record internally where every copy lives, without writing the words themselves in that record, so you can check them all during reviews.
Geographic Separation
Copies kept in the same building share the same disasters. Placing at least one copy in a different location, such as a safe deposit box or a trusted relative’s secure storage, protects against fire, flood, or burglary at home. Consider how quickly you could reach each location if you needed it urgently.
Access by Trusted Others
Anyone who can reach a backup can potentially read it. A sealed, tamper-evident envelope or bag makes unauthorized access visible, even if it cannot prevent it. For high-value holdings, distributing shares so that no single trusted person holds the complete secret limits the damage if one relationship or location fails.
Encrypted Digital Backups: When They Fit and When They Do Not
Some users want a digital backup alongside their physical copies, often stored in encrypted form in the cloud. Encryption scrambles the data so that only someone with the decryption password can read it, which does reduce exposure.
The weakness is that the encryption password becomes the new single point of failure. If it is weak, an attacker who copies the file can attempt to guess it offline indefinitely. If it is forgotten, the digital backup becomes as useless as no backup at all.
For most individuals, physical backups of the seed phrase are the safer default. Digital storage is better suited to non-secret configuration data, such as derivation paths, wallet descriptors, and co-signer extended public keys, which help a restore but cannot move funds.
Shamir Shares and Multisig as Backup Strategies
Splitting a backup can remove the single location that holds everything. Two established approaches serve this purpose in different ways: Shamir secret sharing and multisignature wallets.
Shamir secret sharing, specified for wallets in SLIP-39, divides a secret into shares where any threshold number, chosen at setup, can rebuild it, while fewer shares reveal nothing useful. Shares can be stored in separate places so that a single theft or disaster does not compromise or destroy the whole.
Multisignature wallets go further by using separate keys, each with its own backup. Spending requires a threshold of signatures, so one exposed backup cannot move funds alone. The cost is more configuration to record and more steps to restore, which must be documented carefully.
Backing Up Multisignature and Smart Contract Wallets
Advanced wallets need advanced backups. A multisignature or smart contract wallet may be secured by several keys, but each key and the wallet’s configuration must be recoverable, or the protection can turn into a lockout.
- Back up every signer’s seed separately, each in its own location.
- Save the wallet descriptor or configuration file in multiple places, including at least one offline copy.
- Record the network, contract address, and threshold for smart contract wallets.
- Document any guardians or recovery modules, including how to contact the people involved.
Test the complete arrangement by restoring it on fresh software with a small balance. A multisig setup that has only ever been used on the original devices has not yet proven that it can be rebuilt without them.
Testing a Backup Without Exposing It
An untested backup is an assumption rather than a safeguard. Testing confirms that the words are correct, legible, and complete, and that you understand the restore process before an emergency forces you to learn it.
The safest test uses a hardware wallet that supports seed verification or a spare device reset to factory settings. Restore the backup, confirm that the expected first receiving address appears, then wipe the test device. Avoid typing the seed into an everyday computer or phone.
A complementary test is to send a very small amount to the wallet, restore it on another device, and confirm the balance appears. Repeating this whenever you change wallet software or setup catches problems while the original device still works.
Record the date and result of each test alongside your non-secret notes. A dated history shows when a backup was last proven to work and reminds you when the next check is due.
Keeping Backups Current as Wallets Change
Backups age as setups change. Adding a passphrase, moving to a new address type, creating a new account, or switching wallet applications can all make an older backup incomplete without any obvious warning sign.
Make updating the backup part of every configuration change. When you add a co-signer, change a threshold, or migrate funds to a new seed, update the relevant records the same day and retire outdated copies so they cannot confuse a future restore.
Retiring an old backup means destroying it thoroughly, for example by cross-cut shredding paper or physically defacing a metal plate, and only after confirming that the funds it controlled have been moved. An outdated copy that still controls funds is not obsolete.
Label each copy with a version marker or creation date that does not reveal its contents. During a review, that marker makes it obvious whether every location holds the latest version.
Backup Mistakes That Lead to Permanent Loss
Several recurring mistakes turn careful plans into lost funds. Writing words in the wrong order, skipping a word, or confusing similar words such as those that differ by one letter can all produce a backup that cannot restore the wallet.
Forgetting non-secret details is another. Owners who know their seed but not their passphrase, derivation path, or multisig configuration may spend days searching for funds that are technically safe but practically unreachable.
The most painful mistakes involve heirs. Backups hidden so well that nobody else can find them, or stored without any explanation of what they are, may never be used. Clear, sealed instructions for a trusted executor close that gap without revealing the secret itself.
Simple safeguards prevent most of these errors: number every word, compare the copy against the device twice, write in clear block letters, and review configuration notes in the same cycle as the secret material.
A Backup Plan You Can Maintain for Years
Begin by writing down what your wallet setup actually includes, then build backups that cover every item on the checklist. Choose durable media, decide on a sensible number of copies, and place them where likely disasters cannot reach all of them at once.
Schedule an annual review. Check that each copy is present, legible, and undisturbed, confirm that configuration notes still match the wallet in use, and test a restore on a clean device whenever your setup changes significantly.
As wallet technology moves toward smart contract accounts, social recovery, and descriptor-based configurations, backup needs will keep shifting. Revisit your plan whenever you adopt new tools, so your backups always match the wallet you actually rely on today.