Guide . MultiBit
How to recover a MultiBit Classic wallet password
MultiBit Classic wallet password recovery may be possible from an intact .wallet file or exported .key backup and usable password context. Identify Classic versus MultiBit HD first because their backup and recovery paths differ. Work only on copies; neither an old file nor a remembered password guarantees recovery.
What you need: Keep the complete backup folder and record the original MultiBit version if known. For an assessment, describe the file extensions, whether the password is rejected or the balance appears empty, and non-sensitive password context.
Limits: A public address alone is insufficient. Corrupted files, missing recovery material or a strong unknown password can make recovery infeasible. Special characters do not by themselves establish a software bug.
Fee: Free assessment; 20% of recovered value only on success, with no upfront payment. Request an assessment.
First contact: Describe the problem and which backups or devices you still have. Do not send wallet files, passwords, seed words or passphrases in your first message; our team will explain the agreed handling process if the case is suitable.
Example: Illustrative diagnostic example: A Classic .key export that rejects a password needs a file-format and password assessment; an HD restore showing zero balance needs the restored addresses checked against the previously used addresses. These are different problems, not a reported customer success. See our MultiBit format and input-handling reference.
This guide explains the distinct MultiBit Classic and HD recovery routes. Both applications are discontinued. If you want an assessment of the files you still hold, KeychainX’s legacy-wallet recovery work includes supported MultiBit cases. The steps below help identify the material before choosing a method.
Step 1: find your backup files
MultiBit Classic saved wallets incrementally inside a multibit-data folder. The parts that matter:
- KEY-BACKUP — exported .key files; an export can contain multiple private keys and may be password-encrypted.
- 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?
Use the original application name, folder and file format together. A filename or word count alone can be misleading; preserve the complete backup set so it can be identified correctly.
| Backup type | What to preserve | Recovery route and limits |
|---|---|---|
| Classic | Original .wallet files, exported .key files and associated backup folders. |
Assess file encryption and password hints. A .key export may contain one or several keys; preserve all entries. Classic does not have an HD seed phrase that replaces every file. |
| HD | Wallet words (often 12 words), the mbhd.wallet.aes file, backup archives and original wallet folder. |
Restore from the correct mnemonic or assess encrypted wallet data and the password. Verify addresses and the original version’s derivation behavior; an empty restore does not by itself identify a bug. |
The archived MultiBit export documentation identifies Classic .wallet and HD mbhd.wallet.aes locations. Historical HD derivation issue #445 concerns particular early software behavior; it is not a diagnosis for every HD wallet.
Step 3: decrypt a Classic key
An exported Classic .key file may be encrypted or unencrypted; inspect its format on a copy before choosing a tool. Supported encrypted exports can be assessed with OpenSSL or BTCRecover, while a .wallet file needs its own format handler. When a password is missing, a targeted offline search uses your hints. Keep recovered private keys off websites and verify the corresponding addresses.
Step 4: investigate password-input differences
Special or non-ASCII characters can justify checking the original input path, but they do not prove a universal truncation bug. A rejected password can also reflect an incorrect candidate, file damage or the wrong file-format handler. Our MultiBit reference separates documented reports from their limits.
Step 5: the HD zero-balance trap
An empty restored wallet does not by itself establish that funds are lost or that a derivation bug occurred. Compare the restored addresses with previously used public addresses and their transaction history; then check backup selection, account paths and synchronization. Funds may also have moved.
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
Preserve the full MultiBit folder, identify Classic versus HD, then choose the file-password or mnemonic route. A Classic .key export and an HD mbhd.wallet.aes file are different formats. Investigate password-input differences only where evidence supports them; for an empty HD restore, compare known addresses, backup selection, derivation paths and transaction history.
When to get help from a professional
Professional assessment can help identify backup formats, evaluate a password search and investigate an HD restore that does not show the expected addresses. Special characters and zero balances are symptoms to investigate, not proof of a known bug. We work offline under an agreed process, with the standard 20% success fee and no upfront payment.
What we can’t do
Without usable wallet files, HD wallet words, private-key backups or a device from which recovery material can be retrieved, a public address alone is insufficient. Strong unknown passwords or overwritten files may also defeat recovery. Avoid unofficial replacement clients and online forms asking for keys or wallet words.
Frequently asked questions
Is MultiBit still supported?
No. MultiBit Classic and HD were discontinued after KeepKey acquired MultiBit, so there are no updates or support. The wallets still work for recovery if you have the files, but you should move funds to a modern wallet afterward.
Where are MultiBit Classic keys stored?
In the multibit-data folder — KEY-BACKUP (.key files), ROLLING-BACKUP (.info + .wallet) and WALLET-BACKUP — under %APPDATA% (Windows), ~/Library/Application Support/MultiBit (macOS) or your home folder (Linux).
My MultiBit password is correct but won’t open the wallet. Why?
Possible causes include an incorrect candidate, file damage, format mismatch or differences in how the password was entered. Special characters alone do not establish a truncation bug.
My MultiBit HD wallet shows zero balance — are my coins gone?
A zero balance needs investigation. Check previously used addresses and transaction history, then the backup, derivation paths and synchronization; do not assume the funds are still present.
Can I decrypt a .key file myself?
Sometimes. First identify whether the export is encrypted and which format it uses. Supported encrypted exports can be tested offline with the correct password or a practical candidate search; preserve the original file and verify the resulting addresses.
How much does help cost?
Free assessment; the standard fee is 20% of recovered value, payable only on success. No upfront payment. The scope and handling arrangements are agreed in writing before recovery work.
Stuck on a MultiBit wallet?
For a first assessment, describe the file types, original MultiBit version and what went wrong. Keep files, wallet words and password guesses out of the initial message; we agree the handling process before they are transferred.
Official KeychainX contact: mail@keychainx.io. Describe the problem first; keep recovery secrets out of the initial message.