People often come to me with an old USB stick, memory card, or computer and say they think there might be a wallet on it, but they do not know where to start. That process is tedious if you have to manually inspect files one by one.
BTCRecover has always been good at identifying a single wallet file when you pass it directly to the tool. But until now, it did not have a simple batch function for searching an entire system or storage device.
That changes with the new Wallet Finder script in BTCRecover. It is a free, offline-friendly script that can scan a folder and look for two main types of evidence:
- Supported wallet files that BTCRecover can recognize.
- Text-based material such as BIP39 mnemonics, paper wallets, and private keys stored in text or document files.
Watch the video for the full demo, but this article is a standalone written version so you can follow along without needing the video.
Where to find Wallet Finder
The starting point is the BTCRecover repository. From there, you can also reach the official documentation.

The basic installation process for BTCRecover is the same as in my previous videos, and it depends on your platform. Once BTCRecover is installed, you can look under Usage Examples for the new Wallet Scanning section.

The documentation covers how to run walletfinder.py, what it scans for, and how to install extra modules if needed.
Basic demo: scanning a USB stick
For the demo in the video, I used a fresh Windows system with Python installed and BTCRecover ready to go. I plugged in a USB stick that contained several different examples:
- Bitcoin Core wallet
- MetaMask wallet
- Blockchain.com wallet
- Ethereum keystore file
- Paper wallets in PDF files
- A Word document containing seed material
- BIP38 protected wallet example
- Text files with mnemonic-style content
The important thing to understand is that Wallet Finder runs two kinds of checks.
1. Wallet file mode
This looks for supported BTCRecover wallet files and reports the path if it finds one.
2. Text-based mode
This searches text-like content for things such as:
- BIP39 mnemonics
- Paper wallets
- Private keys
- Other seed-related material in documents or plain-text files
In the demo, I pointed the tool at the USB drive by using a folder argument. The command shown is essentially:
python walletfinder.py --folder E:\
where E:\ is the USB stick. You can use any folder path on your computer.

After running it, Wallet Finder reported several wallet files, including a MetaMask wallet, a Blockchain.com wallet, and a Bitcoin Core wallet. It also found some text-based seed matches.

Extra modules for more complete scanning
One of the first things you may see is that Wallet Finder prints warnings about optional Python modules.
In the demo, it warned that some wallet types might not be detected correctly without extra modules, and that document support would not work fully without textract and pypdf.
That matters because some wallets are not stored as plain-text files. They may be inside:
- DOCX
- Excel-style documents
- Other file formats that need parsing
If you skip the extra modules, Wallet Finder can still run, but it may miss things. In my demo, after installing the additional requirements, the scan found more items, including:
- An Ethereum keystore wallet
- Paper wallets inside PDF files
- A BIP38 protected wallet
- Seed material inside a Word document

The documentation gives you commands for installing the required extras. You can install only what you need, or use the broader requirements file if you want more complete support.
A practical approach is:
- Run Wallet Finder once to see what it reports and what warnings appear.
- Install the missing modules shown in the output.
- Run the scan again.
That second run often gives a much better picture of what is actually on the device.
Redirecting output to a file
Wallet Finder can produce a lot of output, especially if you are scanning an entire drive or using debug mode. For that reason, I recommend redirecting the output to a text file for longer scans.
On Windows PowerShell and most Linux shells, you can use standard redirection:
python walletfinder.py --folder E:\ > search.txt
This writes all of the tool’s output into search.txt. That makes it much easier to review later because you can open the file in a text editor and search for keywords such as:
- path
- mnemonic
- checksum
- suppressed
- wallet
- error

The documentation also shows how to watch the live output while it is being written, which can be useful if you want to monitor progress without losing anything.
For large scans, saving output to a file is one of those small steps that saves a lot of pain later. You do not have to scroll through terminal history or worry about missing something.
Understanding matches and false positives
Wallet Finder does not just look for random words. It uses wordlists and checks the structure of potential mnemonics.
A key point is this: a valid BIP39 checksum is treated as a stronger match than a random sequence of valid mnemonic words.
That matters because English text can accidentally contain many valid BIP39 words. For example, license files, documentation, and other long-form text may include enough words from the wordlist to trigger scattered matches. Those are often false positives.
In the demo, I showed an example where a LICENSE.txt file triggered scattered matches because it contained ordinary English text that happened to include valid BIP39-style words. That is not a wallet. It is just noise.

This is why Wallet Finder suppresses some weaker matches by default. If you are not an experienced recovery person, seeing a long list of weak matches can send you down the wrong path. The tool tries to reduce that confusion.
That said, if you have reason to believe something should be there, debug output can help point you in the right direction. It may show suppressed matches that could be:
- Damaged seed phrases
- Partially corrupted files
- Unusual storage formats
- False positives from ordinary text
If a file contains a long sequential mnemonic with a valid checksum, that is much more interesting than scattered words alone.
Using the exclusion list to reduce noise
Another important part of Wallet Finder is the exclusion list.
By default, it skips many common sources of false positives, such as:
- Browser data files
- System-related files
- Application data folders
- Some Linux system paths
- Source-code trees from crypto libraries and wallet projects
- BTCRecover’s own bundled test wallets and examples
This is especially useful when you point the tool at a whole hard drive or USB stick. Without exclusions, it can spend time on old logs, browser caches, driver files, and development folders that are not real user wallets.

In the demo, I ran Wallet Finder against the BTCRecover folder itself. That folder contains many test wallet files. With the default exclusion list active, it ignored most of them and only reported a real example I had added separately.
When I removed the bottom block from the exclusion list and saved the file, the scan then found many more items because those test wallets were no longer being skipped.
That is not an error. It simply shows how the exclusion list works. You are free to edit it yourself if you know what you are doing. For most people, though, keeping the default exclusions enabled is a good idea when scanning broad folders or whole drives.
Tuning search arguments
Wallet Finder also has several command-line options that let you tune the scan. You can see them by running:
python walletfinder.py --help

Some of the useful options include:
--folder DIR
This is required. It tells Wallet Finder which folder to scan.
--depth N
By default, the tool can recurse deeply through folders. If you set a lower depth, it will not go as far into subfolders. For example, a depth of 1 limits how deep it digs.
--skip-wallet-mode
If you are only interested in text-based matches and want to reduce false positives, you can disable wallet file mode.
--skip-text-mode
Conversely, if you are specifically looking for wallet files and do not care about document scanning, you can disable text mode.
Sequential and scattered match thresholds
You can adjust the minimum number of sequential or scattered wordlist words required before something is reported. The default shown in the demo was 12 for both.
This can be useful if you know what you are looking for. For example:
- If you are looking for a 24-word seed, raising the threshold may help filter out weaker matches.
- If a seed might have been split across documents or stored unusually, lowering it may help you find partial evidence.
Status bar display
Wallet Finder has a progress-style status display because scanning can happen in stages: first discovering files and folders, then examining them. If you prefer less visual output, you can disable the status bar and just get counts as it goes.
What finding a wallet file does not prove
There are two important limitations to keep in mind.
First, finding a wallet file does not confirm that it contains funds. You still need to verify the wallet manually. For many encrypted wallets, that means you will need the correct password before you can access anything.
Second, this tool is not trying to determine balances or transaction history. It helps you locate possible wallet material. It does not replace the next step of safely importing or recovering the wallet.
If you find a seed-based wallet, I strongly recommend using a hardware wallet rather than typing the seed into an unknown hot wallet on an internet-connected machine and hoping for the best. Security matters at this stage.
Keep the recovery environment offline
Another point I always make with BTCRecover is that it should be run completely offline once you have installed what you need.
If a device contains wallets, or if you find wallets that may hold funds, keep the computer used to run BTCRecover offline until you have moved the funds into a new wallet under your control. Do not browse the web with that machine while doing recovery work. There is too much malicious software out there that can steal keys in seconds.
If installing and running tools like this feels too difficult for your situation, or if you want help working through an old drive or storage device safely, I offer private consultations and trusted recoveries. You can request one through the web form at cryptoguide.tips/recovery-services-consultations.
Conclusion
The new Wallet Finder script in BTCRecover is a practical tool for people who have old USB sticks, memory cards, hard drives, or folders and suspect there may be wallets hidden somewhere on them.
It helps you move from “I have no idea where to start” to a structured list of possible wallet files and text-based matches that are worth investigating further. It is free, designed to run offline, and useful for making sense of storage media that has been sitting around for years.
The most important habits when using it are:
- Install the optional modules if you need document scanning or extra wallet support.
- Save long scan output to a file so you can review it carefully.
- Keep the exclusion list enabled unless you know why you need to change it.
- Treat weak matches with caution and prioritize valid checksums and stronger evidence.
- Verify any found wallets manually before assuming they contain funds.
- Use an offline machine and prefer a hardware wallet when importing seed material.
If this helps you find your way through old storage devices, leave a comment below or ask a question in the video thread. I do my best to reply to everyone.
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.







