Old wallet.dat From 2011? How to Open It Without Losing It
If you found an old wallet.dat from 2011, you are probably looking at a hard drive from 2011 or 2013 and one simple question: is there anything inside, and how do I open it without breaking it? The answer changed in 2025. Since Bitcoin Core 30.0 the current software no longer loads old wallets, it only migrates them, and migrating an encrypted wallet requires the password. This guide follows the safe order: copy, identify the format, read the balance without the password, and only then choose between moving the funds, migrating, or attempting password recovery.
In short
- Before anything else, make two copies of the file, one of them on offline media, and never work on the original.
- The Bitcoin Core password locks only the private keys: addresses and balance are readable without it. You can find out whether it is worth the effort before any attempt.
- According to the Bitcoin Core release notes, 30.0 (October 10, 2025) no longer creates or loads legacy Berkeley DB wallets; they must be migrated with
migratewallet, and an encrypted wallet requires its passphrase for migration.
First of all: copy the file twice
The rule is simple: two copies of the original file before any attempt, one on a USB stick or external drive kept disconnected, a recorded hash of each copy so you know if anything changed, and work only on copies. Never open it on a connected machine you do not control, and never send it to anyone before a contract is in place.
If the file sits on an old computer, install nothing on it and do not update the system: copy the file first. On Windows, Bitcoin Core stores the wallet by default under %APPDATA%\Bitcoin; on Linux, under ~/.bitcoin; on macOS, under the Bitcoin folder in Application Support. If the drive will not read or the file was deleted, stop: the corrupted file page describes what to do with the disk before anything is written to it, and the -salvagewallet option, according to the 0.21.0 release notes, was removed from the program and became the salvage command of the bitcoin-wallet tool.
Which format is your file: Berkeley DB or SQLite
Bitcoin Core has used two wallet formats. Legacy wallets, from 2009 until the transition, are Berkeley DB (BDB) databases. Descriptor wallets arrived in version 0.21.0, on January 14, 2021, and, according to the release notes, "use SQLite for the wallet file instead of the Berkeley DB used in legacy wallets". On December 6, 2023, version 26.0 stopped creating legacy wallets through createwallet, "because the legacy wallet is being deprecated in a future release", and gained a menu option to migrate. On October 10, 2025, version 30.0 closed the cycle: "BDB legacy wallets can no longer be created or loaded. They can be migrated to the new descriptor wallet format" through the migratewallet RPC; dumpprivkey, dumpwallet, importwallet and the other legacy-only commands were removed. On January 10, 2026, version 30.2 shipped a "fix unnamed legacy wallet migration failure".
For a 2011 file, the conclusion is direct: any wallet.dat older than 2021 is Berkeley DB, and current Bitcoin Core will not open it without migration. KeychainX puts it the same way: older wallets commonly use Berkeley DB; descriptor wallets use SQLite.
Can I see the balance without the password
Yes, and that is the first step. Wallet encryption arrived in Bitcoin 0.4.0, on September 23, 2011, and the official notes explain that it "only encrypts the actual keys which are required to send your bitcoins, not the full wallet"; someone holding the file "will be able to see all the addresses which belong to you, as well as the relevant transactions".
There are three ways to read the addresses without typing the password. The first is to open a copy in a Bitcoin Core release older than 30, which still loads Berkeley DB, on a machine isolated from the network: the wallet loads, and after rescanning the blockchain it shows the balance; the password is only requested to send. The second is the extraction scripts of btcrecover, an open source project that isolates only what is needed from the file, in the project's words, "without giving btcrecover or whoever runs it access to any of the addresses or private keys in your Bitcoin wallet". The third, for files from 2009 to roughly 2016, is a Berkeley DB reader such as pywallet, according to secondary reports; the tool must run offline.
The only piece of data that may go to a website is the public address, looked up in a block explorer. The file, the password, your password guesses and any key never go into a website, bot or chat.
The three outcomes: no password, known password, forgotten password
Unencrypted file. Every wallet older than September 23, 2011, and any wallet whose owner never set a password, opens without asking anything. In an isolated release older than 30, load the copy, wait for the rescan and send the funds to a new wallet with a fresh backup. On 30 or later, migrate the copy first.
Encrypted, password known. Migrate a copy with migratewallet, which, according to the RPC documentation, first creates a backup named <wallet name>-<timestamp>.legacy.bak in the wallet's directory, requires the passphrase as an argument for encrypted wallets, and may create additional "watchonly" and "solvables" wallets. Check the balance before and after. Then move everything to a modern wallet with a fresh backup. The documentation does not distinguish old loose-key wallets from HD wallets; migration generally preserves the keys, but there are reports of failure in specific cases, with an issue open in the project in 2026. That is why the rule is to always migrate a copy, never the original.
Encrypted, password forgotten. There is no shortcut here; there is a hypothesis attack. Open source tools such as btcrecover support Bitcoin Core passwords with GPU acceleration, and hashcat has a dedicated mode for Bitcoin and Litecoin wallet.dat files, mode 11300. KeychainX describes the work as building hashcat masks and rules for mode 11300, "not blind brute force". With no hypothesis about the password, the attack is pure brute force, and a long random password is out of reach. The post Forgot wallet password: what recovery really costs explains what the list of clues needs to contain; the same reasoning applies to an Electrum file, in Forgot Your Electrum Password? Seed, File or Nothing.
International recovery firms publish distinct terms for Bitcoin Core, consulted on November 9, 2026. Wallet Recovery Services accepts limited information, only the "mkey" section of the file, "so that we cannot steal your bitcoins even if the wallet password is found", and charges 20%, or 15% above US$100,000. KeychainX requires the full wallet file, not just an extracted hash, but only after the service agreement is in place, and charges 20% of recovered value with no upfront payment, warning that "overwritten data or a strong unknown password may make recovery infeasible". ReWallet charges 20% on success and receives data only after a contract. The Bitcoin Core wallet.dat page describes what Vault Recovery reviews at triage: no file, password or guess is requested in the form or the first conversation.
Situation, what to do and the risk
| Situation | What to do | Main risk |
|---|---|---|
| File older than Sept 2011 | Move with an isolated release up to 29 | Overwriting the original |
| Encrypted, password known | Migrate a copy; move to a new wallet | Migrating the original |
| Encrypted, forgotten, with clues | Hypothesis attack on a copy | Sending the file to strangers |
| Encrypted, no clue at all | Read the balance; weigh the attempt | Brute force out of reach |
| File will not open or was deleted | Image the disk; write nothing to it | Loss by overwriting |
| wallet.dat "with balance" for sale | Do not buy | Forged or stolen file |
The "wallet.dat with balance" scam
Forums and marketplaces list wallet.dat files for sale with a balance visible in a block explorer. ReWallet, in "Purchased Bitcoin Wallets: Why You Shouldn't Buy Them", describes two cases: fake wallet files that "show a BTC balance but do not contain the private keys", and real files that are "data sets that have been stolen in a hack", whose purchase is handling stolen goods in most countries; sellers create wallets with strong passwords, infeasible to attack, and sometimes withdraw later. Forklog published an expert's explanation of how to forge a wallet.dat that keeps the funded address and swaps the private key. Kaspersky described, on July 30, 2024, fake wallet "leaks" whose file leads the buyer to a backdoored installer. The post Are Crypto Recovery Services Legit? How to Check One covers the other end: whoever promises to open your file for an upfront payment.
Vault Recovery is a service of Vault Ltda., part of the Vault Capital group, running since 2021. Wallet recovery is not securities advisory and is not regulated by Brazil's CVM. The assessment is free, nothing is requested in the form or the first conversation, and the success fee, from 20% to 15% depending on the recovered value bracket, is only charged if the recovery works.
Frequently asked questions
How can I recover my Bitcoin Core wallet.dat file?
Copy it twice, read the addresses without the password to confirm there is a balance, and pick the path: load it in an isolated release older than 30, migrate a copy with migratewallet (with the passphrase, if encrypted) or, if the password is lost, build the list of clues for an attack on a copy.
What is a wallet.dat file?
It is the wallet file of Bitcoin Core (formerly Bitcoin-Qt), holding private keys, addresses and transactions. Until 2021 it was always a Berkeley DB database; descriptor wallets created since 0.21.0 use SQLite. Since 0.4.0 the password, when set, encrypts only the keys.
Can I see the balance without the password?
Yes. According to the Bitcoin 0.4.0 release notes, encryption covers only the keys needed to spend; addresses and transactions stay readable. An isolated release older than 30 shows the balance after rescanning; extraction scripts and offline readers list the addresses. Only the public address goes to an explorer.
Does Bitcoin Core 30 still open old wallets?
No. According to the 30.0 release notes of October 10, 2025, legacy Berkeley DB wallets can no longer be created or loaded, only migrated through migratewallet; 30.2 fixed a migration failure. An encrypted wallet requires its passphrase for migration; without it, use a release older than 30 on an isolated machine.
Is a wallet.dat sold with balance real?
Almost never what it seems. According to ReWallet, there are forged files that show a balance without containing the keys, and real stolen files, whose purchase is handling stolen goods. In both cases the balance does not become yours. Do not buy.
Let's talk
If you copied the file, saw there is a balance and have hypotheses about the password, or if the file will not open and the disk is old, there is work to do. Vault Recovery's assessment is free, no file, password or guess is requested in the form or the first conversation, and the fee is only charged on what is recovered.
Lost access to a crypto wallet?
Vault Recovery assesses your case for free and only charges a fee if the recovery works. No seed or password requested at this stage.
Assess my case