Blog
Bitcoin Core wallet.dat Recovery: Where to Start
In short
Recovering a Bitcoin Core wallet.dat starts with preserving the original and identifying why access has failed. An encrypted wallet, an unreadable file, a deleted file and a different wallet loaded by mistake require different checks.
- Work on a separate copy. A password prompt does not mean the file is damaged; a read error calls for checking the exact message and Bitcoin Core version before repair or migration.
- If the file is missing, check existing backups and the configured wallet directory. Avoid writing to a drive that may contain a deleted wallet, and save recovered files elsewhere.
- If the wallet opens but the balance is wrong, confirm which wallet was loaded before investigating synchronization. Watch-only data cannot sign transactions. Detailed password-search methods are covered in the linked guide.
Finding wallet.dat is a starting point, not proof that the file can spend bitcoin. A wallet may contain private keys, encrypted keys, or only public information for watching addresses.
Preserve the original first
Keep the original file and existing backups unchanged. Work on a separate copy; do not replace another wallet’s file. If Bitcoin Core still opens the wallet, its backup function is preferable to copying a database while the application is writing to it. Record which device and version the file came from.
Keep a note of when each copy was made and when you last used the wallet. A newer file date does not prove that a backup is more complete. Retain older copies until you know which addresses and keys each one contains. If the file was deleted or the drive is failing, avoid installing recovery software on that drive: further writes can overwrite data you still need.
Check format and software compatibility
Older legacy wallets use Berkeley DB; descriptor wallets use SQLite. The filename alone does not distinguish them. Bitcoin Core 30.0 removed direct loading of legacy wallets, so “install the latest version and open it” is not a universal procedure.
Check the official migration instructions for the file’s format. Do not use versions 30.0 or 30.1 for migration: Bitcoin Core published a warning about a failure that could delete wallet files. Always preserve independent backups before migration or repair.
Identify the actual recovery problem
- Encrypted but intact: the password is needed to use the private keys. If the wallet opens but asks for a password when signing a transaction, treat this as a password question, not evidence of a damaged file. The password-search guide below covers the next steps.
- Unreadable or damaged: record the exact error and Bitcoin Core version. Check compatibility first, then assess a repair on a separate copy if corruption is still suspected. Do not keep changing software versions or repairing the only original.
- Deleted or missing: check existing backups and the configured wallet directory before assuming the file was deleted. If deletion is confirmed, preserve the source drive and save any recovered files to a different drive.
- Watch-only: a displayed balance does not supply the missing private keys. Locate the wallet or backup that holds the keys; repairing this public-information copy does not add them.
Bitcoin Core does not generate a recovery phrase. Keep file recovery separate from instructions for BIP-39 wallets.
If the wallet is intact but encrypted, the separate wallet.dat password guide explains what information can make a password search assessable. Describe the problem without sending the file or password through an enquiry form.
The file opens, but the expected balance is missing
First confirm the name of the loaded wallet and the directory it was loaded from. Bitcoin Core can manage more than one wallet; opening a different wallet or a newly created empty one does not restore the file you found.
Use a receiving address you know you used. Compare it with the loaded wallet, then check whether Bitcoin Core has synchronized and scanned the relevant transaction history. Rescanning can find transactions for keys already present; it cannot recreate missing private keys.
An old non-HD wallet backup may lack keys generated after that backup was made. This is one reason to compare several surviving copies rather than discarding them as soon as one opens.