Found an Old MultiBit Wallet File? How to Extract and Sweep It

You found the file. Maybe it was on a hard drive you haven’t plugged in since 2016, in a folder you almost deleted, or in a cloud backup you’d forgotten about. A .wallet or .wallet.aes file, and possibly bitcoin still attached to it.

MultiBit was discontinued in 2017, so the program that made the file no longer gets fixes or support. That doesn’t touch the coins. They were never inside MultiBit: they sit at addresses on the Bitcoin blockchain, and the keys in your file, or the seed phrase of a MultiBit HD wallet, still control them. Unless someone else has moved them, your bitcoin may still be exactly where you left it. What happened to MultiBit covers the shutdown itself.

Finding the file is often the hardest part. What comes next is more predictable: extracting the private key, and moving the funds to a wallet you control today. This guide goes from file to swept funds. For the overview of every MultiBit route (Classic, HD, password and deleted files), see the MultiBit wallet recovery guide.

Before you do anything else: make two copies

Copy the file to two separate locations, such as two USB drives or two different external drives, before running any tool against it. Keep both copies offline: an unencrypted Classic file stores its private keys in plain form, so anyone who gets a copy can move the coins. With two copies stored safely, no failed attempt can cost you the file.

If the original is on a drive that’s been sitting in a drawer for years, treat it as fragile. Old spinning drives sometimes fail on the second or third read, not the first, so clone it before browsing it if you have any doubt about its reliability. On Windows, use a disk-imaging tool that makes a full sector-by-sector copy. On Linux or macOS, GNU ddrescue is built for failing drives: it copies the readable areas first instead of stopping at the first read error, and its mapfile lets a later run fill in only the gaps.

What not to do with an old MultiBit wallet file

Four mistakes can cost you the file or the coins, whichever route you take below:

• Don’t run recovery tools on the original file. Every attempt runs on a copy: decryption scripts, file repair tools and anything else that touches the wallet data.
• Don’t download MultiBit from anywhere other than its archived project pages. Its last owner, KeepKey, deprecated it, and the old multibit.org address now forwards to an unrelated software forum. Unofficial downloads found through search engines can contain malware designed to capture wallet files and passwords silently. The original code and the last MultiBit HD releases remain archived on GitHub, for MultiBit Classic and MultiBit HD.
• Don’t enter your private key or seed phrase into any website. No legitimate online tool needs your private key to help you recover funds. Any site asking for it is designed to steal them.
• Don’t broadcast a sweep transaction without checking the fee. Bitcoin network fees are not what they were in 2015 or 2016, and an underpaid transaction can sit unconfirmed for days, or indefinitely.

Identify which MultiBit made the file

The file extension tells you which version of MultiBit created it, and that decides the route.

• A .wallet file (no additional extension) is a MultiBit Classic wallet. It contains one or more private keys stored directly in Google’s Protocol Buffer format. If you set a password at the time, those keys are AES-256 encrypted inside the file.
• A .wallet.aes file is a MultiBit HD wallet. The HD wallet file is named mbhd.wallet.aes, and the entire file is encrypted. If you have the password, you can decrypt it and read the seed phrase inside. If you don’t, but you have the seed phrase written down, you can work from the phrase and leave the file aside.

If you’re not sure which you have: Classic files are typically found as standalone .wallet files in a MultiBit folder. HD wallets are usually inside their own folder, whose name starts with ‘mbhd-’ followed by a long string of characters. That folder contains the .wallet.aes file along with supporting files. Keep the whole folder if you find one.

Recovering a MultiBit Classic .wallet file

Classic MultiBit wallets store private keys in Protocol Buffer format. If the wallet was not password-protected, the keys can be extracted directly. If it was password-protected, you need the original password first; there is no other way in.

Unencrypted Classic wallet

The official export tool is read-multibit-wallet-file, published in the MultiBit project’s own GitHub account. It is a small command-line program that runs on Node.js and installs as mbexport. Pointed at a copy of a Classic .wallet file, it prints the private keys in WIF (Wallet Import Format), the format modern wallets accept for imports. Other tools that parse the Protocol Buffer structure can read an unencrypted file the same way.

Do the extraction on an offline machine. Once you have the WIF key, you can import it into Electrum, downloaded only from electrum.org, using the “Import Bitcoin addresses or private keys” option when creating a new wallet. Electrum looks up the key’s address and shows its balance. To move the funds, sweep the key rather than keep it imported, as described below.

Password-protected Classic wallet

If the wallet was encrypted, you need the password before any key can be extracted, and mbexport asks for it. The keys inside are AES-256 encrypted: without the correct password, they are inaccessible. There is no workaround.

Write down everything you remember about the password before running anything: structure, length, capitalization habits, numbers or years you used at the time, any words that were important to you. A partial memory is far more useful than an exhaustive random search. BTCRecover is the standard open-source tool for this, and its documentation lists password recovery for both MultiBit Classic and MultiBit HD. It runs locally and tests candidate combinations against the file. The MultiBit wallet recovery guide covers the password route in more depth.

How to sweep a MultiBit private key

Importing a private key and sweeping it are different operations, and for old MultiBit wallets, sweeping is the right choice. An import keeps the original key active in your wallet, which means it can be exposed again if that wallet is ever compromised. A sweep moves all funds from the old key to a fresh address in your new wallet, and the old key is effectively retired.

Step-by-step sweep in Electrum

These steps follow Electrum 4.8.2, the current version.

1. Download Electrum from electrum.org only, and verify the GPG signature if you know how. Create a new standard wallet with a fresh seed phrase. Write the seed phrase down on paper and store it separately.
2. Once the new wallet is set up, go to Wallet → Private keys → Sweep.
3. Paste the WIF private key from your Classic wallet into the field “Enter private keys to sweep coins from”. Leave “Send to address” on the address Electrum suggests, an unused address of your new wallet.
4. Press Sweep. Electrum collects the coins held by that key and opens a New Transaction window with the full amount. Review it before proceeding.
5. Set the fee in that window. Check the current recommended fee rate at mempool.space first.
6. Press OK. Electrum signs the transaction and broadcasts it, and the funds arrive in your new wallet once it confirms.

The sweep transaction is irreversible once broadcast. Confirm the destination address and fee before you press OK.

What to do if the balance shows zero after import

When an imported key shows a zero balance, check three things: whether the address was ever funded, whether the funds were already moved, and whether Electrum is showing the address that actually holds the coins.

The address type needs no setting. Electrum reads a plain WIF key, one without a prefix such as p2wpkh:, as a legacy key whose address starts with 1, the type Classic MultiBit used. What can differ is the form of the key. One private key has two legacy addresses, one for its compressed public key and one for its uncompressed public key, and the WIF text records which form it is: compressed keys start with K or L, uncompressed keys with 5. mbexport prints every key in compressed form, so a key the wallet held in uncompressed form shows up in Electrum at an address that was never used. Compare the address Electrum shows with one from your old MultiBit records before concluding anything.

If the address matches and the balance is still zero, look it up on a blockchain explorer like mempool.space to confirm whether funds ever arrived there and whether they’ve already been moved.

Recovering a MultiBit HD wallet with your seed phrase

If you have the 12-, 18- or 24-word seed phrase of a MultiBit HD wallet, which MultiBit HD called the wallet words, you can restore access without decrypting the .wallet.aes file at all. If you have the file and its password but not the words, mbexport decrypts the file and prints the wallet words. Keep the file and its backups even when you have the words.

MultiBit HD words are BIP-39, so Electrum, BlueWallet and Sparrow will accept them. The complication is the derivation path. MultiBit HD used a non-standard one, so a modern wallet that uses its default path generates different addresses from the same phrase and shows a zero balance, not because the phrase is wrong, but because it is looking in the wrong place. Our page on a zero balance after a restore covers the other causes.

The correct derivation path for MultiBit HD

MultiBit HD kept its accounts under m/0' and used legacy addresses starting with 1; the first receiving address sits at m/0'/0/0. To restore in Electrum:

1. Create a new wallet, choose “Standard wallet”, then “I already have a seed”.
2. Type the words, click “Options” and select “BIP39 seed”.
3. On the “Script type and Derivation path” screen, press “Detect Existing Accounts”. Electrum checks the standard paths and m/0'.
4. If nothing is found, choose “legacy (p2pkh)” and enter m/0' as the derivation path yourself. Electrum adds the receiving and change branches itself, so enter m/0', not m/0'/0.

Compare the first address with one you know the wallet used. One group of wallets will still show nothing: those created with MultiBit HD’s Beta 7 release, which turned the words into keys in a way that is not BIP32-compliant. MultiBit HD’s own restore screen had a separate option for them, and a standard BIP-39 restore will not reproduce their keys; that case needs a tool that repeats MultiBit HD’s original conversion.

Check each word carefully before concluding the phrase is wrong. A typo or a word copied from the wrong line usually makes the phrase fail its checksum, and if it passes anyway, it opens a different, empty wallet. The BIP39 wordlist has exactly 2,048 words, so a word that isn’t on it is either misspelled or comes from a different list.

If the seed phrase is incomplete

Missing words are a smaller problem than they seem. Each missing word has 2,048 possible values, and for a 12-word phrase the checksum built into BIP-39 rules out about 15 of every 16 candidate combinations before any address is checked. The candidates that remain are tested against an address the wallet is known to have used. Crypto Recovers works with phrases missing up to four words; a phrase lost completely, with no wallet file or other material, cannot be recovered by anyone. Recovering missing words in a seed phrase explains the search in detail.

Recovering a deleted MultiBit wallet file

Deleting a file doesn’t erase its contents immediately; it marks the disk space as available for reuse. If the drive hasn’t been written to much since the deletion, the data may still be there. The window narrows the more the drive is used afterward.

Stop using the drive now. Every write risks overwriting the sectors that hold your wallet file, and a system drive that stays in use keeps writing.

Clone the drive before scanning

Before running any file recovery tool, clone the drive to another drive or to an image file, and work from the copy. It preserves the disk as it is now, and you can repeat a scan if something goes wrong. On Linux or macOS, ddrescue suits older hardware for the reasons above, and its manual advises that the drive being rescued should not be mounted at all, not even read-only. On Windows, use a disk-imaging tool that makes a full sector-by-sector copy.

Scanning for .wallet files

Recuva (Windows) can search for deleted files by name: in its advanced mode, type *.wallet|*.wallet.aes in the “Filename or path” box. PhotoRec, the free file carver from CGSecurity, works differently. It ignores the file system and recognizes files by their content, so a file’s name doesn’t help it. Its list of recognized formats does include a .wallet entry, but that is Armory’s bitcoin wallet, not MultiBit’s, and a .wallet.aes file is encrypted throughout, so it has no header to recognize. Whichever tool you use, save what it finds to a different drive than the one you are scanning.

If the scan returns the file, check its size before doing anything with it. A file of only a few bytes is incomplete: a single private key alone takes 32 bytes, before the rest of the wallet structure. Compare the size with any other copy or backup you have, and try opening a file of plausible size on a copy.

If the file is damaged or partially overwritten

A partially recovered .wallet file may not open cleanly. Some corruption is repairable, depending on which part of the file was damaged: for Classic wallets the header region matters more than trailing data. This is territory where the tooling required goes beyond what’s available in standard recovery software, and where professional data recovery specialists are likely to be more effective than additional DIY attempts. Our page on corrupted wallet files explains what can still be read from one.

When the steps above don’t resolve it

If you’ve found the file but the steps above have not resolved the problem (the balance is wrong, decryption fails, words are missing from the phrase, the derivation path still returns zero, or only partial data remains), Crypto Recovers offers a free initial assessment. We have been helping MultiBit users since 2019, on a no recovery, no fee basis.

Some cases have no route, and it’s better to know that before you spend money. An encrypted Classic file opens only with its password. A completely overwritten file is generally not recoverable through software tools alone. And if the explorer shows the funds were already moved out, recovering the key won’t bring them back.

We never hold your bitcoin at any stage. Once the keys are recovered, you sweep the funds yourself into a new wallet you created, and you pay the agreed fee yourself, as a separate payment.

FAQ: old MultiBit wallet files

My MultiBit wallet won’t sync. Is my balance gone?

Not because of the sync failure. A wallet that cannot sync shows an outdated or empty balance because it cannot see the network, and that moves no coins. Look up your address on a block explorer (type the address, never a key) to confirm the real balance in seconds.

Can I use the original MultiBit software to open the file?

Technically possible in some cases, but not recommended. The original MultiBit software is no longer maintained, the old official website no longer offers it, and copies found through search results can be modified to steal wallet data. Extracting keys with mbexport or another Protocol Buffer parser, or using BTCRecover for password recovery, is safer than running the original application.

My recovered file won’t open. Is it corrupted?

It may be, but not necessarily beyond use. Start by checking the file size. A file of only a few bytes is certainly incomplete. A file at a normal size that won’t parse may have a damaged header, which is sometimes repairable, depending on which bytes were affected. A completely overwritten file is a different problem and generally not recoverable through software tools alone.

How long does a sweep transaction take to confirm?

Under normal network conditions, a Bitcoin transaction with an adequate fee confirms within one to three blocks, roughly 10 to 30 minutes. If you set a low fee, the transaction may take hours or days to confirm, or may never confirm if fees rise significantly after broadcast. Use mempool.space to check current recommended fee rates before broadcasting.

My wallet file is from 2013 or 2014. Does that affect recovery?

The format hasn’t changed, so the age of the file doesn’t affect whether it can be parsed. What it does affect is the address format. Very early MultiBit Classic wallets used compressed and uncompressed public keys, which produce different Bitcoin addresses from the same private key. If you import a key and see a zero balance, compare its address with your old records: mbexport prints keys in compressed form, so a key the wallet held uncompressed shows a different, unused address. Both should be checked before concluding the wallet is empty.