So maybe you are someone who has been using the old blockchain.info wallet, now blockchain.com, from before you knew any better. You may have found yourself locked out because you do not know your main password, or perhaps you do not remember your second password. If you think you know part of the password, but not all of it, BTCRecover can be a useful tool for trying to regain access to your crypto.
Watch the video for the full walkthrough. This article is a standalone written version so you can follow along without needing the video.
Stuck with a wallet recovery?
I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.
Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.
What BTCRecover Is Good For, and What It Is Not
BTCRecover is not really designed to brute-force a completely unknown password from scratch. If your password was very long, random, or totally forgotten, this will usually take far too long and may not be practical.
It is much more useful when you have some partial knowledge of the password. For example:
- You remember it started with a certain word or phrase.
- You know it contained common words you often use in passwords.
- You suspect you added symbols, numbers, or a year somewhere.
- You only have a short list of likely passwords, but may have made typos.
- You are trying to recover a second password and already know the main wallet password.
In those cases, BTCRecover can test combinations and typo variations against your Blockchain.com wallet file or an extract of it. If you are dealing with lost funds and want extra help understanding whether recovery is realistic, my recovery services and consultations page covers how I approach those situations.
Use the Correct BTCRecover Fork
The first thing you need to do is download BTCRecover from my GitHub fork. This matters because older forks may not support newer Blockchain.com wallet formats. If you use an unsupported version, it can simply report that the password search was exhausted even though a valid result might exist with the correct tool.

When you open the repository, look for the documentation and example files. The video follows a specific set of examples for recovering Blockchain.com wallet passwords, including command lines and template files you can use as a starting point.

You should download the repository, unzip it, and then work from that folder on your own computer. The exact path will depend on where you saved it, but all of the later commands are run from inside the BTCRecover folder.
Important: Wallet File Versus Extract Script
Before running any recovery, understand the two main ways BTCRecover can be used with Blockchain.com wallets.
1. Running BTCRecover on the full wallet file
BTCRecover can work directly on a downloaded Blockchain.com wallet file. If it finds the password, you get the result and can then use that password to access the wallet and move funds. This is convenient, but it means anyone with the full wallet file and the recovered password can spend the funds.
2. Running BTCRecover on an extract
There are also extract scripts that create a small data sample from the wallet. That sample is enough to solve for the password, but not enough to move funds by itself. This is useful if you want to run the recovery on another computer, such as a cloud server, or give the task to someone else without handing over the full spendable wallet file.
If your password is likely long or complex, using an extract can be a safer approach because the person solving it would not have enough information to steal your funds even if they found the password.
Downloading the Blockchain.com Wallet File
To run BTCRecover against the full wallet file, you first need to download that wallet file from Blockchain.com. The process is similar to logging into the normal web wallet, but with an extra authorization step.
Open Command Prompt and navigate to the folder where you unzipped BTCRecover. You will then run the provided download script. Depending on how Python is set up on your machine, you may need to use python instead of python3.

The script will ask for your wallet ID. Enter it and press enter. From there, Blockchain.com should send an email asking you to authorize the login attempt.

This step is important for security. The requesting device may show as unknown because it does not look like a normal browser, but the IP address and country should still be familiar to you if you are running the script from your own machine. If anything looks wrong, reject the request and stop. Do not approve an authorization you did not initiate.
If two-factor authentication is enabled, you will also need to enter that code. Once approved, the wallet file is saved locally in the BTCRecover folder as wallet.aes.json. That file is what BTCRecover can use for password recovery.

Recovering the Main Password with a Tokenlist File
A tokenlist file is useful when you remember fragments of your password rather than one complete candidate. It tells BTCRecover which pieces you believe were used and allows it to test combinations, including typo handling.
For example, you might know that:
- The password started with a certain word or phrase.
- It included some common words you often use.
- You may have added symbols between those words.
- You may have included a year somewhere in the password.
You do not need to guess every possible arrangement yourself. The tokenlist can describe the building blocks, and BTCRecover works through likely combinations.

In this example, I am using the wallet file that was downloaded earlier. The command tells BTCRecover:
- Where the wallet file is located.
- That it should try some typo handling for capitalization mistakes.
- Which tokenlist file to use.

When you run this, you may see a security warning. That is expected when using the full wallet file rather than an extract, because the tool has access to data that can be used to spend funds if the password is found. Keep your machine safe, close unnecessary network exposure, and do not share the wallet file with people you do not trust.
The search will run for a while. Depending on how many combinations are possible, it may finish quickly or take much longer. If it finds a match, it displays the result in the terminal.

In the video example, the result was found relatively early, but that is largely luck of the draw. The size of the search space matters a lot. If your remembered fragments are too broad, the number of possible passwords can become enormous.
Recovering the Second Password with a Passwordlist File
Some Blockchain.com wallets also have a second password. To recover that one, you need to already know the main wallet password. BTCRecover will prompt you for it when running the second-password search.
A passwordlist file is different from a tokenlist file. Instead of giving BTCRecover fragments and letting it build combinations, you give it a list of complete candidate passwords. This works well when:
- You are fairly sure what the password was.
- You only have three or four likely options.
- You want to test common top passwords from a public wordlist.
- You suspect small typos, such as wrong capitalization or missing characters.
In the example, the passwordlist includes some candidate passwords with deliberate typos: incorrect capital letters and an extra letter at the end. It also includes common passwords from a public list. BTCRecover tests each line in the list and applies the requested typo handling.

The command for this example is similar, but with important differences:
- It uses a wallet file that has a second password enabled.
- It tells BTCRecover you are looking for the second password, not the main password.
- It enables typo handling for capitalization changes and deleted characters.
- It uses
--passwordlistinstead of--tokenlist. - It points to the passwordlist file containing your candidate passwords.
When you run it, BTCRecover asks for the main wallet password. You type it in, even though it does not display on screen as you type. If the main password is wrong, it will tell you. Once accepted, it begins testing the second-password candidates.

If a match is found, it prints the recovered second password. In the video example, the main and second passwords happened to be similar enough that this could feel slightly confusing, but the important point is that the tool successfully identified the second-password result using the provided list and typo options.
Using an Extract Script for Second-Password Recovery
You can do the same second-password recovery without giving BTCRecover the full wallet file. Instead, you use one of the extract scripts to create a small data sample that is enough to solve the password but not enough to move funds.
This is especially useful if you want to run the search on another machine or ask someone else for help. They can find the password from the extract, but they still would not have the full wallet file needed to spend the coins.

The process is:
- Run the appropriate extract script for the second password.
- Enter the main wallet password when prompted, because extracting the second-password data requires it.
- Copy the resulting extract string from the terminal output.
- Run BTCRecover using the
--data-extractargument instead of pointing to a full wallet file.

The final command is very similar to the previous second-password example, except you are no longer telling BTCRecover which full wallet file to use or that it should treat the input as a second-password wallet. Instead, you paste in the extract data produced by the script.

If everything is correct, BTCRecover will search through your candidate passwords and typo variations just like before, but it is working only on the extracted sample.
Blockchain.com Wallet Warning: Move Funds to Better Security
I cannot do a video or article about the Blockchain.com wallet without emphasizing that, in my opinion, it is not a good wallet to keep using for long-term security. If you have regained access, now is a great time to upgrade your security significantly and move your funds to a hardware wallet.
A Ledger Nano S can be a good value place to start, or a Ledger X if you are more of a mobile user. The exact device matters less than the principle: after recovering old exchange-style or web-based wallets, move what you need into something where you control the keys in a safer way.

Do not treat recovered funds as permanently safe just because you got back into the old wallet. The safest next step is to withdraw them from the less secure environment and store them in a way that reduces your attack surface.
Practical Tips Before You Start
Before running any recovery, make sure you understand what you are doing:
- Use the correct BTCRecover fork for newer Blockchain.com wallet formats.
- Keep the full wallet file private if you run searches on it directly.
- Consider using an extract script if you want to avoid exposing the spendable wallet file.
- Start with your strongest password memories, not every vague possibility.
- Use tokenlists when you remember fragments and need combinations.
- Use passwordlists when you have a short list of likely complete passwords.
- Enable typo handling only where it makes sense for how you type passwords.
- Be patient: small search spaces can finish quickly, while large ones may take far longer.
If you run into trouble, open an issue on the GitHub repository or leave a reply under the video. If you successfully recover funds and want to support ongoing maintenance and development of the tool, consider sending a tip.
Conclusion
BTCRecover is not magic, but it can be very useful when you have partial knowledge of a Blockchain.com wallet password. The key is matching the right method to what you remember: tokenlists for fragments and combinations, passwordlists for short candidate lists, and extract scripts when you want to solve the password without exposing the full spendable wallet file.
If you regain access, do not stop there. Move your funds into a more secure setup, such as a hardware wallet, so the next time something goes wrong, your crypto is in a much safer place.
Questions from viewers
Common questions from the comments on this video, with my answers.
What does the error 'Password Search Exhausted' mean and what should I do next?
This message means BTCRecover has tested every combination in your tokenlist or passwordlist and none of them were correct. It does not necessarily mean you have made a setup error; it simply means the correct password is not currently covered by your list. You need to broaden your search by adding more potential words, numbers, or variations to your tokenlist and running the process again.
How do I create and use a tokenlist file if I don't remember my exact password?
A tokenlist is just a plain text file where you list the parts of the password you think might be included. You can place this file anywhere on your computer, but you must specify its location using the `–tokenlist` argument in your command. If you are unsure how to structure it, refer to the documentation on expanding wildcards, which allows you to define ranges for characters or numbers you are uncertain about. The example files provided in the GitHub repository can serve as a starting template.
I am getting an error saying the file path is wrong or 'No such file or directory'. How do I fix this?
Ensure that the path you provide in the `–tokenlist` argument points directly to the file, not just the folder containing it. Also, check for typos in the drive letter or extra characters like a dot before the drive letter. The simplest solution is often to place your tokenlist file inside the main btcrecover folder and name it `btcrecover-tokens-auto.txt`. This allows you to omit the `–tokenlist` argument entirely, as the tool will look for that specific filename automatically.
Why is my recovery taking so long, or why is it running out of memory?
If your search is running for several days, you may run out of system memory. To prevent this, you should enable the `–no-dupchecks` flag in your command. Additionally, the speed depends heavily on your hardware; older wallets generated on weaker CPUs are faster to check than those from modern systems. If you have a GPU, ensure you are following the OpenCL documentation and using the `–enable-opencl` flag to get a significant speed boost, though note that some older wallet types (like Electrum2) do not support GPU acceleration.
Can I recover a password if I don't remember any part of it?
If you have no idea what the password was, recovery is extremely difficult because you would need to brute-force it. For passwords longer than 5-6 characters, this is generally not feasible with standard tools. You would need to use a tokenlist with extensive wildcards to cover all possible character combinations, but success is unlikely unless the original password was very short. If you cannot recall even a small portion of the password, there is limited technical help available beyond trying broad wildcard searches. If you’d like hands-on help, see wallet recovery services.
I am trying to recover the second password but get an error about decrypting the wallet first. What am I doing wrong?
To search for the second password, you must first provide the main password to decrypt the wallet file. You can do this by using the `–blockchain-secondpass` argument, which will prompt you to enter the main password via the command line. If you are using the extract script specifically for the second password, ensure you have correctly specified the main password so the tool can access the encrypted data without needing the full spendable wallet file.
Stuck with a wallet recovery?
I maintain BTCRecover and have helped people recover seed phrases, passphrases and wallet passwords since 2019. Book a one-hour video session and I’ll walk you through doing the recovery yourself, without sharing your seed. Or, if you’d rather I run it, a trusted recovery is charged only if it succeeds.
Private sessions: US$100 per hour. Trusted recovery: 10% of recovered funds. I never contact people first and will never ask for your seed phrase over chat or email.
Found this useful?
These guides are free and ad-free. You can support them by sharing them, subscribing on YouTube, or sending a tip.







