Key Takeaways
- A backup that fails to restore is usually incomplete, not destroyed. Most "dead" wallets are missing one word, a passphrase, or the correct derivation path rather than being cryptographically lost.
- Check in the safest order: read it, identify the format, verify watch-only, then restore. You can confirm that a backup matches a known address without ever exposing your private keys online.
- The riskiest step is the recovery attempt itself. Fake validator websites, paid "recovery experts," and careless typing into internet-connected devices cause more losses than aging paper does.
Why Old Backups Stop Working
Coins do not expire. Balances sit on a public blockchain, and the only thing that changes over time is your ability to prove ownership of them. So when an old backup fails, the blockchain is almost never the problem. The problem is on your side of the equation.
Old backups fail for four ordinary reasons:
- The record is incomplete. A seed phrase was written down without its passphrase, its derivation path, or its wallet name.
- The record is damaged. Ink faded, paper tore, a hard drive failed, or handwriting became unreadable.
- The software is gone. The wallet app was discontinued, delisted from app stores, or changed its file format.
- The user is restoring it in the wrong place. The words are correct but the wallet being used derives different addresses from them.
This guide covers backups of your own wallets. It does not cover accessing wallets that belong to someone else.
Step 1: Identify What Kind of Backup You Actually Have
Before you touch any software, work out what you are holding. Different backup formats have very different recovery paths.
| Backup format | What it looks like | Typically usable today? |
|---|---|---|
| BIP39 seed phrase | 12, 15, 18, 21, or 24 English words | Yes, widely supported by most modern wallets |
| Electrum seed | 12 or 13 words that other wallets reject | Yes, but usually only inside Electrum |
| Private key (WIF) | A single long string starting with 5, K, or L | Yes, importable into several wallets |
| Keystore JSON | A file of text plus a password you chose | Yes for Ethereum style wallets, if the password is known |
| wallet.dat | A binary file from Bitcoin Core | Yes, but needs migration in modern releases |
| Paper wallet | A printed address and private key, often with QR codes | Yes, but should be swept and retired |
| Extended public key (xpub) | A long string starting with xpub, ypub, or zpub | Viewing only, cannot spend |
| Exchange screenshot or login note | Account details, not keys | Depends entirely on the exchange still existing |
A quick sanity check: if your backup contains only an address, or only an xpub, you can see the funds but you cannot move them. That is a viewing key, not a spending key.
Step 2: Read the Backup Before You Restore It
Physical inspection comes first, because a damaged record needs different handling than a complete one.
Count the words. BIP39 phrases come in lengths of 12, 15, 18, 21, or 24 words. A phrase of 13, 14, or 23 words is either an Electrum seed or a copying error.
Check the words against the official list. BIP39 uses a fixed list of 2,048 words. Every valid word appears on that list, and the first four letters of each word are unique. If your backup contains a word that is not on the list, it was mis-transcribed.
Look for the classic handwriting traps. Common confusions are a written "l" and the digit "1", the letters "u" and "v", "rn" read as "m", and words that share a stem such as "cabin" and "cabbage".
Note the extras. Was a passphrase used? Was there a wallet name, a date, a derivation path, or a note about a second device? Old multisig setups often need a wallet descriptor or a co-signer key that is stored somewhere else entirely.
At this stage, do not type anything into a website.
Step 3: Verify Without Exposing Your Keys
The safest possible test is one that never puts your secret material on an internet-connected machine.
If you know one address that the wallet used to control, you can confirm the backup matches it before you ever restore for spending. A watch-only wallet loaded with the account's extended public key will show every address in that account and its full history. If your old address appears in that list, the backup and the account belong together.
If you do not know any old address, the more careful route is to restore the phrase on an offline device: a laptop with the network disabled, or a hardware wallet you already trust, then compare the addresses it produces against a block explorer.
Rules that reduce risk during this step:
- Do not type a seed phrase into any web page, search bar, chat window, or note-taking app that syncs to the cloud.
- Do not photograph the backup.
- Treat every "seed phrase validator" or "wallet checker" site as hostile. A tool that can validate your phrase can also take your funds.
- If you must use a browser-based tool, download it, disconnect from the internet, and use a device you are willing to wipe afterwards.
Step 4: Restore and Interpret the Result
When you do attempt a restore, the outcome falls into one of three buckets. What the wallet tells you is diagnostic.
| What you see | What it usually means | What to try next |
|---|---|---|
| "Invalid recovery phrase" or "checksum failed" | One word is wrong, missing, or out of order | Recheck the wordlist, order, and word count |
| Wallet opens, balance is zero | Phrase is valid but you are looking at the wrong account | Try other derivation paths, address types, and the passphrase |
| Wallet opens, balance is correct | The backup is fully usable | Move funds to a fresh wallet and make a new backup |
| Wallet opens, unfamiliar addresses | A passphrase is applied or missing | A wrong passphrase silently produces a different valid wallet |
The zero-balance case causes the most panic and is often the least serious. BIP39 phrases carry a checksum, so a phrase that is accepted is mathematically consistent. Empty results usually point to one of these mismatches:
- Wrong derivation path. Legacy, SegWit-compatible, and native SegWit accounts all derive different addresses from the same words. Many wallets let you enter a custom path.
- Wrong account index. Funds may sit in account 1 rather than account 0.
- A passphrase, sometimes called the 25th word. There is no way for software to tell a wrong passphrase from a right one. Each guess opens a different, valid, empty wallet.
- Wrong chain. The same phrase controls addresses on several networks. Check the network your funds were actually on.
Special Case: Very Old Bitcoin Core Files
If your backup is a wallet.dat file, treat it with extra care. Bitcoin Core removed its legacy wallet system in the 30.0 release, so old files now have to be migrated to the newer descriptor format before use.
There is a further wrinkle worth knowing. In January 2026, Bitcoin Core disclosed a migration bug in versions 30.0 and 30.1 that could, in rare cases, delete files in the wallet directory when a migration of an unnamed wallet.dat failed. The binaries were pulled and a fix shipped in 30.2. The practical lesson is simple and applies to every recovery attempt: make read-only copies of the original file on separate media before you open it in anything. Work on the copy, never the original.
Step 5: Decide the Verdict
| Verdict | Signals | Recommended action |
|---|---|---|
| Usable | Phrase validates and produces a known address or balance | Migrate funds to a new wallet, retire the old backup |
| Partly usable | Phrase validates, no funds found yet | Systematically test paths, accounts, passphrase candidates |
| Recoverable with work | One or two words unclear or missing | Narrow candidates offline, check derived addresses on an explorer |
| Probably unusable | Multiple words lost, no passphrase, no known address | Document what you have and stop; guessing wastes time and creates exposure |
After a Successful Recovery
An old backup that works is still an old backup. It has been in unknown storage conditions, may have been seen by others, and was written under standards that have moved on.
The clean finish is to create a new wallet on a device you control, move the funds across, write a fresh backup, and record the details that the old one was missing: wallet software, derivation path, address type, whether a passphrase exists, and the date. Then test the new backup by restoring it on a second device before you rely on it.
FAQ
Can a seed phrase expire? No. A seed phrase is a number encoded as words. It does not have a shelf life. What ages is the software around it and the paper it is written on.
My phrase restores but the balance is zero. Are my coins gone? Not necessarily. A valid phrase with an empty wallet most often means the wrong derivation path, the wrong account, a missing passphrase, or the wrong network. Check a known old address against a block explorer before concluding anything.
Is it safe to use an online seed phrase checker? No. Any site that receives your words can spend your funds. If you need a tool, download it, go offline, and use a device you can wipe.
Do paid crypto recovery services work? The recovery-services category attracts fraud. Never send a seed phrase or private key to anyone and never pay an unsolicited helper. If advanced recovery is warranted, use transparent offline tools on a device you control and move any recovered funds to a fresh wallet afterwards. No one can recover a phrase that is genuinely lost.
How many words can be missing and still be recoverable? One unknown word in a phrase is often solvable offline because the checksum eliminates most candidates. Two or three unknown words expand the search enormously, and beyond that recovery is usually impractical.
Related Terms
- BIP39 is the standard that turns wallet entropy into a readable list of words drawn from a fixed 2,048-word list.
- Derivation path is the numbered route a wallet follows to generate addresses from one seed, written in a format such as m/84'/0'/0'.
- Passphrase is an optional extra secret added to a seed phrase, sometimes called the 25th word, which produces a completely separate wallet.
- Watch-only wallet is a wallet loaded with public keys only, able to display balances and history but unable to sign transactions.
- Descriptor wallet is the modern Bitcoin Core wallet format that records exactly how a wallet's addresses are derived, replacing the older legacy format.
Sources
- BIP39 specification, Bitcoin Improvement Proposals repository: https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki
- BIP32 hierarchical deterministic wallets: https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki
- Bitcoin Core, "Wallet Migration Failure May Delete Unrelated Wallet Files in Bitcoin Core 30.0 and 30.1", 5 January 2026: https://bitcoincore.org/en/2026/01/05/wallet-migration-bug/
- Bitcoin Core 30.2 release notes: https://bitcoincore.org/en/releases/30.2/
- Electrum documentation, Seed Version System: https://electrum.readthedocs.io/en/latest/seedphrase.html
This article is educational content. It is not financial, legal, or security advice for your specific situation. Always confirm recovery procedures on the official support pages of the services you use, since these processes change over time.
Not sure which problem you have?
Use the Fixing Crypto Mistakes hub to identify the transaction, wallet, network, or exchange issue before taking another action.
OPEN TROUBLESHOOTING HUB



