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 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, recovery may be possible. The steps below help identify the available material and the problem.
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: 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
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, check the relevant addresses and transaction history before drawing conclusions about the funds. 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.
What we can’t do
If you have neither the backup files nor the 15-word phrase, there is nothing to work from. If you only have a public address, that’s not recoverable. And beware of fake “MultibitCore” or drainer clients online — installing one and entering your keys will empty your wallet. We only ever work from your own encrypted files, offline, and we never ask for payment upfront.
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, with OpenSSL or BTCRecover if your password is close to something you remember. DIY stops at the truncation bug and HD derivation issues.
How much does help cost?
Success-based: a percentage of the recovered value only if we open the wallet, and nothing upfront.
Stuck on a MultiBit wallet?
Send us your .key/.wallet backups and what you remember of the password. Honest assessment within 24 hours, success-based fee.