Guide . MultiBit

How to recover MultiBit Classic keys

MultiBit is dead software, but the coins usually aren’t. This is the hands-on version: where the keys hide, how to decrypt them, and the famous bug that blocks “correct” passwords.

Updated July 2026 · KeychainX — Wallet Recovery since 2017

This is the do-it-yourself companion to our MultiBit Classic recovery page. MultiBit was discontinued years ago, so there’s no app support — but if you still have the backup files, the private keys are recoverable. Work through the steps below.

Step 1: find your backup files

MultiBit Classic saved wallets incrementally inside a multibit-data folder. The parts that matter:

• KEY-BACKUP — single .key files (one private key each, encrypted with your password).
• ROLLING-BACKUP — paired .info (readable, shows the address) and .wallet (the encrypted wallet) files.
• WALLET-BACKUP — where your first wallet was created.

Look under %APPDATA% (Windows), ~/Library/Application Support/MultiBit (macOS) or your home folder (Linux). Copy the whole folder somewhere safe before doing anything.

Step 2: Classic or HD?

Check the file types. .key and .wallet files mean MultiBit Classic — password-encrypted keys. A 15-word phrase or .aes.json backups mean MultiBit HD, which derives everything from the mnemonic. The two need completely different approaches, so settle this first.

Step 3: decrypt a Classic key

A MultiBit Classic .key file is an encrypted private key. For the technically inclined it can sometimes be decrypted with OpenSSL, or you can point a tool like BTCRecover at the .wallet file with a list of your best password guesses. The workflow is: build a candidate list from what you remember, run it against a copy of the file offline, and watch for the one that decrypts a valid key. If your password is close to something you recall, this often succeeds on its own.

Step 4: the special-character bug

This is the reason so many “definitely correct” MultiBit passwords fail. An old version mangled passwords containing special or foreign characters — the underlying library truncated or altered high bytes before encrypting, so the password that actually locked the wallet wasn’t the one you typed. Re-typing the right password today simply won’t work. Reproducing this bug is beyond a plain word list; it’s specific tooling, and it’s where most stuck Classic cases are actually won.

Step 5: the HD zero-balance trap

If you’re on MultiBit HD and a restore shows an empty wallet, don’t panic — a known derivation-path bug can make a restored HD wallet scan as zero even when it holds funds. The coins are fine; the software derived the wrong addresses. Checking the alternate derivation paths reveals the real balance.

Why MultiBit wallets are stranded

MultiBit Classic was one of the most popular Bitcoin wallets of 2011–2014 — the easy desktop choice before hardware wallets and seed phrases were standard. People encrypted a .key file with a password they never expected to need again, and then KeepKey acquired MultiBit and shut development down. No updates, no support, and years later a lot of those wallets hold balances worth far more than when they were made. That combination — defunct software, an old password, and appreciated coins — is why MultiBit is one of the most common legacy recoveries we see. The one thing that makes any of it possible is still having the backup files.

Move to a modern wallet

MultiBit is dead software, so the goal isn’t to keep using it — it’s to recover the keys and get out. Once a key is decrypted, import it into a current, supported wallet and move the funds, then back up the new wallet’s seed phrase properly on paper or steel, kept separate from the device. Don’t leave value sitting in an unmaintained app.

Quick recap

To recover MultiBit Classic keys, in order: find the backup files in the multibit-data folder (KEY-BACKUP, ROLLING-BACKUP, WALLET-BACKUP); determine Classic vs HD from the file types; decrypt a Classic key with OpenSSL or BTCRecover using your best password guesses against a copy; watch for the special-character truncation bug if a “correct” password fails; and check the HD zero-balance derivation trap if a restored HD wallet looks empty. Always work on a duplicate of the files, never the original, and never enter your keys into any website. The bug and derivation cases are where DIY ends and specialised tooling begins — but even then, the coins are almost always still there. Recover the keys, move them to a modern wallet, and back up the new seed properly so you never depend on dead software again.

When to get help from a professional

If you’ve found the files and a basic attempt hasn’t worked — especially if special characters or an HD zero-balance are involved — that’s the point to bring it in. We reproduce the truncation bug, fix HD derivation, and run large structured searches offline, success-based and with no upfront fee. Full technical detail is on the MultiBit recovery page.

Frequently asked questions