Your crypto seed phrase — the sequence of 12 or 24 words generated when you set up a hardware wallet or self-custody wallet — is the single most sensitive piece of personal data most crypto holders possess.
It’s not a password. Passwords can be reset, accounts can be recovered, and customer support can help you back in. A seed phrase is the mathematical root of your entire wallet. Every private key, every address, every asset under that wallet derives from it. Anyone who has your seed phrase has your crypto. Anyone who loses their seed phrase — without any backup — has permanently lost access to everything it controlled.
The question of where to store a seed phrase isn’t a technical edge case. It’s the central security question for anyone holding meaningful crypto. And the answers most people reach for first — photos of the word list, a note on the phone, an email draft — are among the worst possible choices.
Why the Default Instincts Are Wrong
When people generate a seed phrase for the first time, they’re staring at 12 or 24 words on a screen and told to write them down. The natural instinct is to photograph them, type them into Notes, email them to yourself, or save them in a Google Doc. These feel like safe, backed-up locations. They’re not.
Screenshots in cloud photo libraries. A screenshot of your seed phrase uploaded to Google Photos or iCloud is indexed, synced across devices, potentially scanned for content by the provider, accessible to anyone who gains access to your account, and subject to legal requests served to the provider. A government subpoena, an account breach, a phishing attack that captures your cloud credentials — any of these exposes your seed phrase. The photo may also appear in cloud search features or AI photo tagging systems that process images server-side.
Notes apps. Apple Notes with iCloud sync, Google Keep, Notion, Evernote — all of these sync to cloud servers. Your note containing 24 words sits on a server operated by a third party, subject to all the same access vectors as cloud photo storage. If the app is breached, if your account is compromised, if the company faces a legal request, your seed phrase is exposed.
Email drafts. A common workaround people devise: saving a draft email to themselves that never gets sent, reasoning it won’t be captured in transit. The draft still sits on mail servers, is accessible to the email provider, and is exposed by account compromise or legal request. Email is not a secure storage medium for any sensitive data.
Password managers. Password managers are appropriate for credentials — usernames, passwords, TOTP secrets. Storing a seed phrase in a password manager creates a dangerous dependency: if you lose access to your password manager (forgotten master password, provider breach, service shutdown), you lose your seed phrase along with everything else. Seed phrases should be stored independently of password managers.
Encrypted files on cloud storage. Storing a seed phrase in an encrypted file on Dropbox or Google Drive is better than plaintext, but it introduces complexity. The security now depends on the encryption passphrase, which is itself a credential that has to be stored somewhere. It’s layers of dependency, not genuine isolation.
The Core Security Requirement
Storing a seed phrase well requires satisfying two properties simultaneously:
-
Not accessible to remote attackers. The phrase cannot live on any internet-connected system, because internet connectivity is the primary attack surface. Remote attackers can’t physically steal a piece of paper in your home safe.
-
Not lost to physical events. A single paper copy in a single location is vulnerable to fire, flood, or physical loss. A seed phrase that exists in only one place fails the redundancy test.
These two requirements pull in opposite directions. Keeping a seed phrase offline reduces remote attack exposure but makes redundancy harder. Digital backups improve redundancy but introduce online attack surface. The solutions that work well are those that satisfy both requirements simultaneously.
What Actually Works
Handwritten paper in a secure location. Write the seed phrase on paper — not printed from a printer (printer logs and shared printer memory are risks) but handwritten — and store it somewhere physically secure. A home safe that’s fire-rated and bolted to the structure is appropriate. A bank safe deposit box is another option. Don’t store it in a wallet, a drawer, or an unlocked filing cabinet.
This is the baseline. It works. The vulnerability is a single point of physical failure: if that location is lost in a fire, flood, or burglary, the phrase is gone.
Multiple paper copies in multiple locations. The simplest redundancy solution: make two or three physical copies of your seed phrase and store them in different secure locations. Two fire-rated safes at different addresses, or one home safe and one bank safe deposit box. If one location is lost, another still holds the backup.
The vulnerability: each additional copy is an additional exposure point. More copies means more locations for a physical attacker to potentially find one.
Metal plate backup. Paper is vulnerable to fire and water. Several products — Cryptosteel, Bilodal, and others — allow you to engrave or stamp your seed words into stainless steel. A metal backup survives conditions that would destroy paper. The same redundancy principles apply: consider keeping a metal backup in a fireproof location.
Shamir’s Secret Sharing (SSS). For holders with large positions or sophisticated threat models, Shamir’s Secret Sharing is a cryptographic method for splitting a seed phrase into multiple shares, where any subset of those shares (for example, any 3 of 5) can reconstruct the original. You distribute the shares across separate physical locations. A thief who finds one or two shares gets nothing. You can still recover with any threshold number.
SSKR (Shamir’s Secret Key Recovery) is an implementation standard supported by some hardware wallets. This approach requires careful management: you need to track which shares exist, where they are, and ensure you haven’t lost enough of them to fall below the reconstruction threshold.
Multisig wallets. Multisig (multi-signature) wallet setups require multiple private keys to authorize transactions, rather than a single key derived from one seed phrase. For example, a 2-of-3 multisig requires any two of three hardware wallets to sign a transaction. Losing one wallet doesn’t mean losing access to funds — and any single compromised device doesn’t let an attacker move funds either.
Multisig adds significant complexity in setup, transaction workflows, and recovery. It’s appropriate for large holdings or high-threat-model situations where the operational overhead is justified.
What About Encrypted Digital Storage?
For people who want a digital backup as a layer of redundancy — in addition to, not instead of, a physical copy — the considerations are:
Client-side encrypted storage (zero-knowledge). Some services encrypt files entirely on your device before upload, meaning the provider’s servers never see your plaintext data. If you use a zero-knowledge service with a passphrase stored separately and securely, this provides a meaningful level of protection for a digital backup copy. The trade-offs: if you forget the decryption passphrase, you’re locked out; the service must be genuinely zero-knowledge and not just marketing-speak.
Server-side encrypted storage. Services that encrypt data at rest with keys they manage — the model used by most mainstream cloud storage — provide protection against storage-layer breaches, but the provider can technically decrypt and access your data. This means legal requests, insider threats, or provider-level breaches could expose a seed phrase stored this way. It’s better than unencrypted cloud storage, but it relies on trusting the provider’s operational and legal situation, which can change.
If you use any digital storage for a seed phrase backup, it should be a secondary redundancy layer on top of a solid physical solution — not a replacement for it.
The Inheritance Problem
Seed phrase storage has a dimension that most how-to guides don’t address: what happens to your crypto holdings when you die, if your heirs don’t have access to the seed phrase?
Unlike a bank account, there’s no institution to contact, no authority to petition, no legal process that unlocks a wallet without the keys. If your seed phrase dies with you, the crypto is gone.
Building a seed phrase storage solution should include a plan for inheritance: someone you trust has access to the physical backup, or you’ve established a legal mechanism (a sealed envelope in a will, instructions to an estate attorney) that conveys the necessary information to the right person at the right time without exposing it prematurely.
This is another argument for multiple trusted physical locations over a single-location approach, and for documenting the existence and recovery process even if not the phrase itself in your estate planning.
The Threat Model Question
The right storage approach depends on your threat model — specifically, who you’re protecting against and what they’re capable of.
General protection (against opportunistic attackers, account breaches, credential theft): handwritten paper copy in a home safe or bank safe deposit box, no digital copies anywhere.
Higher-value holdings: two or more physical copies at separate secure locations, possibly on metal for durability, with inheritance planning in place.
Very high-value or professional holdings: Shamir’s Secret Sharing across multiple geographic locations, or a multisig setup that removes single-point-of-failure risk from both storage and transaction authorization.
What you don’t need, at any threat level: a screenshot in Google Photos, a note in a synced notes app, a draft in your email, or a password manager entry that lives on a cloud server.
The seed phrase is the one thing crypto security absolutely cannot recover from if mishandled. Every other element of wallet security — the hardware wallet itself, the PIN, the backup device — can fail or be replaced as long as the seed phrase is intact and available. Treat it accordingly.