MultiBit Wallet Recovery: Classic, HD and Password Routes

MultiBit was discontinued in 2017 without a migration plan for its users. The original software no longer runs reliably, official downloads are gone, and the straightforward recovery options that once existed have mostly disappeared with them. What remains is a wallet file somewhere on an old drive, a password you may remember only in part, and Bitcoin on the blockchain that hasn’t moved.

The route depends on what you have, and a wrong first step can close off the others. If you already found a .wallet file and want the hands-on path from file to swept funds, the found-an-old-MultiBit-file guide walks through that scenario step by step. For the history and why the wallet disappeared, see what happened to MultiBit.

Which MultiBit wallet did you use?

Before doing anything else, establish which version of MultiBit you were running: the recovery approach is entirely different between the two.

MultiBit Classic stored your private keys directly in a .wallet file. If you set a password, that file was encrypted with AES-256. Without the correct password, the file is completely locked. There is no seed phrase for Classic wallets. Recovery depends on the wallet file or another usable backup, including the .key private-key backups described below. An encrypted file or backup still needs its corresponding password. If no copy remains, the next question is whether one can be retrieved from storage.

MultiBit HD was the later version and worked differently. When you created the wallet, you were given a 12-, 18- or 24-word seed phrase as a backup. The wallet file (.wallet.aes) was encrypted with a password, which in theory gave you two separate ways in. In practice, MultiBit HD had design problems: the wallet file was fully encrypted with the wallet password, the derivation path was non-standard, and wallets created before the 2015 Beta 8 fix had a mnemonic-conversion bug. This means you can’t just enter your words into Electrum and expect to find your funds, even if every word is correct.

If you’re not sure which version you used: a .wallet file without .aes means Classic. A .wallet.aes file means HD. If you remember being shown a 12-, 18- or 24-word phrase when you first set up the wallet, that was the HD version.

Step 1: Find your wallet file

Before attempting any recovery, locate your wallet file. Many people assume it’s gone when it’s sitting on an old hard drive or USB stick they haven’t plugged in for years. Search thoroughly before concluding anything.

MultiBit stored wallet files in the following locations:

• Windows: C:\Users\[username]\AppData\Roaming\MultiBit\
• macOS: /Users/[username]/Library/Application Support/MultiBit/
• Linux: /home/[username]/MultiBit/

Windows and macOS hide these folders by default. Enable hidden-file display before navigating to them.

If the default locations come up empty, search your entire system for files with .wallet or .wallet.aes extensions. Also check cloud storage accounts you were using at the time, any old email attachments from when you set up the wallet, external drives, and USB sticks. The file is small and could be anywhere you were storing documents in those years.

When you find it: make a copy immediately. Work only with that copy. Never run any recovery tool on the original. This is the single most important rule in the entire process: one wrong step on the original file can permanently close off recovery options you still have.

MultiBit's backup files: .key, mbhd.wallet.aes and the backup folders

MultiBit made more copies in the background than most users realise, and those automatic backups are often the reason a case is still recoverable when the main file is damaged or the password is missing. What exists depends on the version.

MultiBit Classic kept a folder named <walletname>-data next to each .wallet file. Its key-backup subfolder holds the .key files: every time you set or changed the password, created a new receiving address or imported private keys, Classic wrote out an export of all private keys, encrypted with the wallet password and timestamped, for example walletname-20140407200743.key. The same folder holds rolling-backup (the previous version of the wallet file, kept on every save) and wallet-backup or wallet-unenc-backup (full timestamped copies). If Classic could not open the main file, it tried the most recent backup itself.

The .key files matter for two reasons. They contain the private keys needed to move the coins, so a .key backup is a complete starting point even when the .wallet file is gone. And for password work they are the better target: the BTCRecover documentation recommends testing candidates against a .key file rather than the full .wallet file because it is much faster. Keep every .key file you find — one export does not necessarily contain keys that were created later.

MultiBit HD stored each wallet in its own folder, named mbhd- followed by a long wallet ID, inside the MultiBitHD application folder:

• Windows: C:\Users\[username]\AppData\Roaming\MultiBitHD\mbhd-[wallet-id]\mbhd.wallet.aes
• macOS: /Users/[username]/Library/Application Support/MultiBitHD/mbhd-[wallet-id]/mbhd.wallet.aes
• Linux: /home/[username]/.MultiBitHD/mbhd-[wallet-id]/mbhd.wallet.aes

The file mbhd.wallet.aes is the wallet itself, encrypted with the wallet password; there is no separate ".mbhd" file type. Two backup folders sit beside it. rolling-backup holds recent copies of the wallet file, timestamped and encrypted with the same password (mbhd-[timestamp].wallet.aes); the last four were kept, and MultiBit HD loaded one automatically when the main file failed to open. zip-backup holds encrypted zip copies of the whole wallet folder, the files ending in .zip.aes, up to sixty of them with the first two and the last eight always kept. Those zip backups are encrypted with a key derived from the wallet words rather than with the password, and they contain the wallet password in encrypted form — which is why MultiBit HD could restore a forgotten password for anyone who still had the wallet words. If a cloud backup folder was configured, the same zip files were copied there too.

"Wallet words" is MultiBit HD's own name for its recovery phrase: 12, 18 or 24 words, written down together with a datestamp. The datestamp only speeds up synchronisation when restoring; the keys are derived from the words alone.

Two failure modes are easy to misread. The first is a correct password being refused. The project's issue tracker documents MultiBit HD wallets that stopped opening with a password that was demonstrably right; in one case the log showed the file decrypting successfully and the software then failing to read the stored transaction data, and the developers' advice was to restore an older backup, which worked. If a password that used to work is suddenly rejected, do not modify mbhd.wallet.aes and do not keep typing variants: keep the password, the whole wallet folder and every older backup, because the keys inside are usually intact. The second is a wallet that no longer synchronises or opens at all. MultiBit was an SPV wallet built on bitcoinj; it stored block-chain data separately from the wallet (multibit.spvstore, mbhd.spvchain) and has received no maintenance since 2017, so stalling during sync, showing a wrong or unconfirmed balance, or refusing to start is a software and network problem. It does not mean the private keys in the wallet file are gone, and reinstalling old MultiBit versions over the data folder risks overwriting the very backups that would have helped.

You have a MultiBit Classic .wallet file and the password

If you have the .wallet file and know the password, recovery is technically possible but requires care. The original MultiBit software is no longer safe to use. Unofficial downloads found online are frequently compromised, designed to capture your wallet file and password the moment you enter them. Don’t use any MultiBit version you found through a web search.

Extract the private keys from a copy of the file with verified tools, using the password if the file is encrypted. Keep key extraction offline. The found-file guide explains importing and sweeping in Electrum, checking the relevant address and reviewing the destination and fee before sending. If you are not comfortable handling private keys, seek specialist help before proceeding.

You have the file but forgot the password

A forgotten password is where most people get stuck, and it’s also where the most avoidable mistakes happen. Randomly trying combinations without a plan is slow, and if the tool you’re using limits failed attempts, you can lock yourself out of the file entirely before finding the right answer.

Start by writing down everything you remember about the password before touching any software. Not just guesses, but the elements you typically used in passwords at that time: length, capitalisation habits, numbers or years you’d include, symbols you liked, words that were important to you. Go through old notebooks, any password manager you were using then, and anywhere else you might have written it down. A partial memory, even just a rough structure or a few characters, is far more useful than a list of random attempts.

For technically confident users, BTCRecover is an open-source tool that tests password combinations against a MultiBit wallet file locally on your machine. It requires setup and some understanding of how to configure it correctly, but it’s free and doesn’t require sending your wallet file anywhere. Run it only on an offline machine.

If you’ve been through this process already and haven’t found the password, the issue is usually one of two things: elements you haven’t included in your search, or a search space that’s too large for consumer hardware to cover in a reasonable time. GPU-based software can test several orders of magnitude more combinations per second, which is where professional recovery becomes the practical option rather than a last resort.

You have a MultiBit HD seed phrase

If you have your 12-, 18- or 24-word phrase, you have a strong starting point, but there’s an important complication. MultiBit HD used a non-standard derivation path, which means most wallets won’t find your funds even if every word is correct. Entering the phrase into Electrum with default settings will show a zero balance, and many people conclude the phrase is wrong when it isn’t.

Use Electrum downloaded only from electrum.org. Create a wallet from your existing phrase and enable the BIP39 option when entering the words. On the address-type and derivation screen, select legacy (p2pkh) and enter m/0' as the derivation path. Electrum adds the receiving branch /0 and change branch /1 itself, giving addresses under m/0'/0 and m/0'/1; do not enter either branch as the account path. Compare an address with one known to belong to the original wallet. MultiBit HD wallets created before the Beta 8 fix in 2015 can also have a mnemonic-conversion problem, which requires a separate compatibility check even with the correct path.

Before assuming anything is wrong with the phrase itself, check each word carefully for typos. A single incorrect character makes the entire phrase invalid. Also try the most plausible word orders if you’re not fully certain of the sequence. Rule that out before looking for other explanations.

What to do if your seed phrase is incomplete or contains errors

If your phrase is mostly intact but missing a word or two, recovery is often still possible. The BIP39 word list contains exactly 2,048 words, and valid phrases must also pass a checksum. This means the number of plausible combinations is far smaller than it appears: a single missing word from a 12-word phrase means 2,048 possibilities, which a computer can test in seconds.

Two missing words produce roughly four million combinations, still well within reach. Three or more makes the search space grow significantly, but depending on what other constraints are known (partial words, likely positions), it’s still often worth attempting.

If you have a word that’s slightly wrong rather than fully missing, the BIP39 list provides a finite set of close matches to test against. What would take weeks to work through manually can be covered systematically in hours. The important thing is to never enter your phrase into any online tool or website: this is one of the most effective methods attackers use to steal funds, and the sites are designed to look legitimate.

A valid checksum does not identify your wallet: compare candidate phrases against an address known to belong to it. The BIP39 word list explains the word list and checksum. If a word is not on that list, check its spelling and whether the backup belongs to a different wallet format.

You deleted the MultiBit wallet file

If you’ve deleted your wallet file and haven’t used the drive heavily since, there’s a meaningful chance the data is still present. Deleting a file marks the space as available. It doesn’t immediately erase the contents. Stop using the drive now, before doing anything else.

Clone the drive first using a tool like ddrescue (Linux) or Macrium Reflect (Windows) to create a byte-for-byte copy. Then scan that copy with a file recovery tool (Recuva on Windows or PhotoRec on any platform work well), looking specifically for .wallet and .wallet.aes files. If the tool finds the file intact, extract it to a different drive and proceed with the recovery steps above.

If the file shows as overwritten, forensic-level recovery can sometimes still retrieve partially overwritten data, but results are unpredictable. For wallets holding meaningful amounts it may be worth pursuing, but the realistic success rate drops sharply once the space has been reused.

Keep the disk image so scans can be repeated without rereading the original drive. If using ddrescue, keep its mapfile too: it records which areas were copied and which remain unreadable. Save recovered files to a separate drive. Once a file is recovered, the found-file guide covers extraction, sweeping and checks on a file that will not open.

What can go wrong

The biggest risk in MultiBit wallet recovery is an avoidable mistake that destroys options you still have. The coins themselves are not going anywhere. Downloading software from unverified sources is the most dangerous step. Malicious versions of MultiBit look identical to the original and silently transmit your wallet file and password to a remote server. This has happened to real users who thought they were running a legitimate recovery.

Never enter your seed phrase into any website or online tool. This is one of the most reliable ways to permanently lose access to your funds. Any invalid seed phrase recovery should be done locally, on an offline machine, using verified tools.

Running large numbers of password guesses without a strategy wastes time and can trigger lockouts if the tool limits failed attempts. Build a structured candidate list before starting anything.

Frequently asked questions

Can I recover my Multibit wallet without the password?

It depends on which version you used and what else you have. For MultiBit HD, a correct and complete seed phrase can provide an alternative route to your funds, though MultiBit’s non-standard derivation path complicates this. For MultiBit Classic, the exact password is ultimately required to decrypt the wallet file. The encrypted file remains the recovery target; remembered details can help focus a systematic candidate search, and the complete case requires assessment.

Is it safe to use the original MultiBit software?

Not in any reliable sense. The software hasn’t been updated since 2017, is incompatible with current Bitcoin protocol updates, and unofficial downloads are frequently compromised. If you must use it for any part of the process, do so only on a machine that is completely offline and that you’re prepared to wipe afterward.

Does MultiBit Classic have a recovery phrase?

No. Classic never issued one — it stored your private keys directly in the .wallet file, encrypted with AES-256 if you set a password. Recovery requires the wallet file or a usable backup, such as a .key export, and the corresponding password if that material is encrypted. If no copy remains, deleted-file recovery may be worth assessing. If you are hunting for 12, 18 or 24 words for a Classic wallet, they were never created and nobody can produce them after the fact. To tell the versions apart: a plain .wallet file is Classic, a .wallet.aes file is MultiBit HD, and only HD showed you a word list during setup.

Why does my MultiBit HD recovery phrase show a zero balance in Electrum?

Usually the derivation path, not the words. MultiBit HD used a non-standard path, so a correct phrase entered with Electrum’s default settings returns nothing; use the BIP39 option, legacy (p2pkh) and account path m/0' in Electrum, as described in the HD section above. Electrum adds the receiving and change branches itself. Rule out two other causes too: a single mistyped word invalidates the whole phrase, and wallets created before the Beta 8 fix in 2015 carry a mnemonic-conversion bug that can show zero even on the right path. Never type the phrase into a website to check it.

Can I still recover a MultiBit wallet file I deleted?

Sometimes, and it depends mostly on what the drive has done since. Deleting a file marks the space as free rather than erasing the contents, so stop using that drive before anything else, clone it, and scan the clone; the deleted-file section above lists the tools. Once the space has been reused the realistic odds drop sharply, and partially overwritten data gives unpredictable results.