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 attached to it.

Finding the file is actually the hardest part for most people. What comes next is more predictable: extracting the private key, and moving the funds to a wallet you control today. For the general 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

This is the only rule that matters more than the steps that follow. Copy the file to two separate locations: a USB drive and a cloud folder, or two different drives before running any tool against it. Recovery attempts, especially decryption scripts, should always operate on a copy.

If the original file is on a drive that’s been sitting in a drawer for years, check whether it mounts correctly first. Old spinning drives sometimes fail on the second or third read, not the first. Clone it immediately if you have any doubt about its reliability. On Windows, Macrium Reflect Free does this without requiring a paid license. On Linux, ddrescue handles failing drives better than most other tools because it retries bad sectors systematically rather than aborting.

Once you have two copies stored safely, you can proceed without the risk of an irreversible mistake.

Identify What You’re Working With

The file extension tells you which version of MultiBit created it, and that determines everything about what comes next.

• 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 entire file is encrypted. If you have the password, you can decrypt it and access the seed phrase inside. If you don’t, but you have the seed phrase written down somewhere, you can bypass the file entirely.

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 a folder with a name starting 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

An unencrypted .wallet file can be read with tools that understand the Protocol Buffer format. The most commonly used approach is to run the file through a Python script that parses the protobuf structure and outputs the private keys in WIF (Wallet Import Format) the format that modern wallets accept for imports.

Do this on an offline machine. Once you have the WIF key, import it into Electrum (downloaded only from electrum.org) using the ‘Import Bitcoin addresses or private keys’ option when creating a new wallet. Electrum will scan the blockchain and show you the associated balance.

Password-protected Classic wallet

If the wallet was encrypted, you need the password before any key can be extracted. The decryption is AES-256 without the correct password, the file contents are inaccessible. There is no workaround.

Write down everything you remember about the password before running anything: structure, length, capitalisation 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, it runs locally and tests candidate combinations against the file. The MultiBit wallet recovery guide explains how to configure it correctly.

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 the old key is effectively retired.

Step-by-step sweep in Electrum

• Download Electrum from electrum.org only. 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.
• Once the new wallet is set up, go to Wallet → Private Keys → Sweep.
• Paste the WIF private key from your Classic wallet into the field provided.
• Electrum will show the balance associated with that key. Review it before proceeding.
• Set a fee. Check the current recommended fee rate at mempool.space fees have changed significantly since MultiBit was in use, and underpaying can leave a transaction stuck for days.
• Broadcast. The funds will arrive in your new wallet once the transaction confirms.

The sweep transaction is irreversible once broadcast. Confirm the destination address and fee before clicking send.

What to do if the balance shows zero after import

A zero balance after importing a private key almost always means one of two things: the key belongs to an address that was never funded, or Electrum is looking at the wrong address format. Classic MultiBit used legacy Bitcoin addresses (starting with 1). If Electrum is configured to show native SegWit addresses, it may not display the balance until you switch the address format in the settings.

If the address format is correct and the balance is still zero, check the address 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 still have the recovery phrase for MultiBit HD, you may be able to restore access without decrypting the file. The derivation settings and early-version compatibility still matter. The MultiBit recovery guide covers that route, including incomplete phrases. Keep the file and its backups even when you have the words.

Recovering a Deleted MultiBit Wallet File

If the file has not yet been recovered from the drive, stop using that drive. Work from a disk image and save recovered files to a different drive. Follow the deleted-file section of the MultiBit recovery guide before returning to the extraction steps here.

Check a recovered file before opening it

If the scan returns the file, verify its size before doing anything with it. A .wallet file that’s only a few bytes has likely been partially overwritten and may not be usable. A file at a plausible size typically several kilobytes to a few hundred kilobytes is worth attempting to open.

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.

What Not to Do With an Old MultiBit Wallet File

A few mistakes are common enough to be worth stating directly.

• Don’t download MultiBit from anywhere other than an archived, verified source. Unofficial MultiBit downloads found through search engines frequently contain malware designed to capture wallet files and passwords silently. The original software is no longer distributed by its developers.
• Don’t enter your private key or seed phrase into any website. There is no legitimate online tool that needs your private key to help you recover funds. Any site asking for it is designed to steal them.
• Don’t run recovery tools on the original file. Always work on a copy. This applies to decryption scripts, file repair tools, and anything else that touches the wallet data.
• Don’t broadcast a sweep transaction without checking the fee. Bitcoin network fees are not what they were in 2015 or 2016. An underpaid transaction can sit unconfirmed indefinitely.

Official legacy tooling for MultiBit Classic

MultiBit Classic exports private keys with the official legacy command-line tools mbexport and read-multibit-wallet-file. Run them on a copy of the .wallet file, then import or sweep the exported keys into a current wallet. MultiBit HD words are BIP-39, so Electrum, BlueWallet and Sparrow will accept them — but MultiBit HD derived from m/0'/0, so with default settings the balance reads zero; the HD vault file is an encrypted mbhd.wallet.aes in the wallet's own folder.

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 worked through these cases on MultiBit HD wallets since 2019. No recovery, no fee.

Frequently asked questions

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

Almost never. A wallet that cannot sync shows an outdated or empty balance because it cannot see the network - the coins did not move. 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, its download links are gone from the official site, and many versions found through search results have been modified to steal wallet data. Extracting keys through a 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 under 1 KB is probably incomplete. A file at a normal size that won’t parse may have a damaged header this 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.

The 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, try the alternative address format. Both should be checked before concluding the wallet is empty.