Forgotten encryptwallet passphrase
The dominant case. The file is fine; the passphrase set years ago is not remembered exactly.
Bitcoin Core Wallet Recovery
Bitcoin Core keeps everything in a local database rather than a seed phrase, so recovery revolves around one file, one passphrase, and whether the client can be persuaded to see all of your addresses.
How Bitcoin Core stores your access
Core writes keys into wallet.dat inside the data directory — %APPDATA%\Bitcoin on Windows, ~/Library/Application Support/Bitcoin on macOS, ~/.bitcoin on Linux. Running encryptwallet seals the master key with a passphrase-derived key; the rest of the database structure stays intact.
Wallets created before HD support contain a finite pool of pre-generated keys, typically a hundred at a time. Newer wallets are HD and derive addresses from an internal seed, but Core still does not present that seed as a 12-word phrase, so a file backup remains the only backup.
Because Core is a full node wallet, a restored file often shows a zero balance until the chain is rescanned from the wallet's birthday. That is a display state, not a loss.
Typical Core access-loss cases
Backup older than the addresses used
A pre-HD backup missing keys generated after it was made, so part of the balance is invisible.
Data directory moved or lost
The blockchain data was deleted to reclaim space and wallet.dat went with it, leaving only backups to find.
Very old client version
A wallet from an early Core or Bitcoin-Qt release that needs careful handling rather than a direct upgrade.
Corrupted database
An unclean shutdown or failing disk left the file unloadable, requiring low-level parsing.
Balance shows zero after restore
Usually an incomplete rescan or a wallet birthday set too late, not missing coins.
What may help in a Core case
- The wallet.dat file, plus every copy of it you can locate, unmodified.
- The whole data directory if available, including any backups subfolder.
- Which Core or Bitcoin-Qt version created the wallet, and roughly when.
- Any receiving address or transaction ID from the wallet.
- What you remember about the passphrase's structure and length.
- Whether the wallet was ever dumped with dumpwallet, producing a plaintext key file somewhere.
Realistic outcomes
Worth assessing
- Intact encrypted wallet.dat with partial passphrase recollection.
- Unencrypted legacy wallet that only needs correct loading and a rescan.
- Damaged file where key records survive in the readable portion.
- A dumpwallet output file found in an old backup.
Not recoverable
- Random passphrase with no recollection and no hint file.
- Data directory deleted with no backup on any medium.
- A wallet address alone, with no key material anywhere.
Related pages
Bitcoin Core questions
Does Bitcoin Core have a seed phrase?
Traditionally no. Modern descriptor wallets are HD internally, but Core does not present a BIP39 phrase for you to write down, so the file backup is what protects you.
I restored my wallet and the balance is zero.
Rescan the chain from before the wallet's first transaction. On a pruned node this may require reindexing or a full sync. The coins are on-chain regardless of what the client displays.
Can salvagewallet fix a corrupted file?
Sometimes, but it modifies the file. Always make copies first and treat the original as evidence — specialist parsing frequently recovers more than the built-in tools.
My backup only has some of my coins.
That is the classic pre-HD key-pool gap. Look for a later backup; keys created after the backup date are simply not present in it.
Not sure whether your case is recoverable?
Describe the wallet, what happened and what information you still have. You will get an honest assessment of whether recovery is technically feasible — without sending any secret credentials.
Assess My Bitcoin Core Recovery Case