wallet.dat Recovery
wallet.dat is the Bitcoin Core wallet database. If you still have the file, you still have the keys — the question is whether the encryption passphrase can be reconstructed and whether the file is intact.
What the file actually holds
A wallet.dat file is a Berkeley DB database containing private keys, address metadata, transaction records and, in encrypted wallets, a master key sealed with a passphrase-derived key. Encrypting a wallet does not encrypt the whole file: the structure remains readable, which is why tooling can often confirm that a file is a genuine encrypted wallet and extract the parameters needed to test passphrase candidates.
Wallets created before HD support (roughly pre-2016) hold a pre-generated pool of keys rather than a seed. A backup from that era captures only the keys that existed when it was made, which is why an old backup sometimes shows a smaller balance than expected — later addresses simply are not in it.
File corruption is a separate failure mode from a forgotten passphrase. A truncated or partially overwritten file may still yield key material through low-level parsing even when Core refuses to load it.
Do this first, before anything else
- Copy the file to at least two separate storage devices and work only on copies.
- Do not run chkdsk, fsck or disk repair tools on the drive holding the original.
- Do not overwrite the file by launching a wallet that creates a new one in the same directory.
- Note the file size and modification date; both help identify the era and completeness.
- Look for sibling backups such as wallet.dat.bak or files inside a backups folder.
- Record any Bitcoin address you know belonged to this wallet.
When a wallet.dat case is workable
Promising
- An intact encrypted file with partial recollection of the passphrase.
- An unencrypted legacy file that simply needs the right client version or parsing tool.
- A slightly truncated file where the key records remain within the surviving portion.
- A backup that loads but shows a lower balance than expected — often a key-pool coverage issue.
Dead ends
- A strong random passphrase with nothing remembered about it.
- A file destroyed or overwritten repeatedly, with no other copy.
- Only a filename in an old folder listing, with the file itself gone.
- Recovering a wallet.dat you do not own.
Related pages
wallet.dat questions
How do I know my wallet.dat is encrypted?
Bitcoin Core prompts for a passphrase when you try to send. At file level, an encrypted wallet contains master key records that specialist tools can identify without revealing anything about the passphrase itself.
Can I open wallet.dat without Bitcoin Core?
Yes, several tools can parse the database directly to inspect its structure or extract key material. This is standard practice when the file will not load in the client.
My backup shows fewer coins than expected.
Pre-HD wallets used a fixed key pool. Addresses generated after the backup are not in the file. A newer backup, or a rescan with an extended key pool, may reveal the rest.
Is it safe to upload wallet.dat somewhere?
No. An encrypted wallet.dat is still a copy of your keys protected only by the passphrase. Never upload it to a website, forum or unknown service.
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 wallet.dat Case