I recently saw a couple of Reddit threads where people were having trouble with old Bitcoin paper wallets. They could not import the wallet or sweep the private key because they got messages like “private key is invalid,” “no balance found,” “incorrect checksum,” or they simply could not click Next in Electrum.
These are usually small damage problems: a missing character, a mistyped letter, a smudged printout, or a page that was folded and damaged over time. In many cases, the private key can still be recovered if you know which format it is in and where the problem might be.
In this article, I’ll walk through how to use BTCRecover for raw Bitcoin private key recovery from paper wallets, especially ones generated with Bitaddress.org. You’ll see two practical examples: one WIF key with missing trailing characters, and one hexadecimal key containing typos.
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.
Why paper wallet private keys can fail to import
A Bitcoin private key is just a number. But when you print it or write it down, that number has to be encoded into some human-readable format. If even one character is wrong, the result may no longer decode to the same private key.
This is especially true with text-based private keys. A single bad character can make an otherwise valid-looking string unusable. That’s why old paper wallets often fail validation checks in wallets like Electrum.
You might see the wallet address on the paper, but when you try to import the private key, the wallet refuses it. Or the wallet accepts a different-looking key that produces a completely different address. Or the key passes some basic format check but fails checksum validation.
The important thing is not to panic and start guessing randomly. If the damage is small and localized, BTCRecover can help you test likely corrections systematically.

Private key formats supported by BTCRecover
Before using BTCRecover for this kind of recovery, you need to understand the format of the private key you are trying to repair.
The most common paper wallet format is Wallet Import Format, often called WIF. A standard compressed WIF private key is a 52-character Base58Check string that usually starts with L or K. An uncompressed WIF private key is 51 characters and usually starts with 5.
There is also the raw hexadecimal format: 64 hexadecimal characters, using digits 0-9 and letters A-F. This is the actual private key number represented in hex.
Over the years, Bitcoin private keys have been encoded in other ways too, such as Base64 or mini private keys. But for this article, we are focusing on what BTCRecover supports today: compressed WIF, uncompressed WIF, and hexadecimal raw private keys.
If your paper wallet shows a long string starting with L or K, you are probably dealing with compressed WIF. If it starts with 5, it is likely uncompressed WIF. If it is 64 characters of hex, that is the raw hex key.

What you need before starting
These examples assume you already have a working installation of BTCRecover. If you do not, set it up first using the official documentation or my setup videos. You will be running commands from your local BTCRecover folder.
You should also decide what information you actually have:
- The damaged private key string.
- The wallet address printed on the paper wallet, if available.
- Any known damage pattern, such as missing characters at the end or a suspected typo in one position.
- A computer where BTCRecover can run for some time.
If you have both the damaged private key and the correct address, that makes recovery much easier because BTCRecover can check each candidate against the expected address. If you do not have the address, BTCRecover can also check candidates against an address database of known Bitcoin addresses.

Example 1: recovering a WIF key with missing characters
The first example is a common paper wallet problem: the private key is mostly intact, but some characters are missing from the end.
Imagine you have a compressed WIF key that should be 52 characters long, but you only have 48 characters. You know the last four characters are gone because of damage, cropping, or poor printing.
In this case, we can use BTCRecover’s password list feature with wildcards. A wildcard tells BTCRecover to try every possible character in a missing position.
For Base58 WIF keys, the relevant wildcard is %B. It represents one Base58 character. If four characters are missing at the end, you would put your partial key into a text file and add four %B wildcards at the end.
Steps to recover a damaged WIF key
- Open your BTCRecover folder.
- Create a plain text file, for example
passwordlist.txt. - Put your partial WIF private key on one line in that file.
- Add one
%Bwildcard for each missing Base58 character. - Save the file.
- Open a command prompt or terminal inside the BTCRecover folder.
- Run
btc_recover.pywith the raw private key option, your password list file, and the target address from the paper wallet.
The important flags are:
--rawprivatekey: tells BTCRecover this is a raw private key recovery.--passwordlist: points to the text file containing your partial key and wildcards.--haswildcards: enables wildcard expansion in the password list.--address: specifies the expected Bitcoin address from the paper wallet.
If you do not have the address, you can use BTCRecover’s address database feature instead. This checks candidates against known addresses rather than one specific target address.

Once the command is running, BTCRecover will test combinations of possible characters in the missing positions. When it finds a candidate that matches the expected address, it reports the recovered key.
In the video example, only four trailing WIF characters were missing, so the recovery finished quickly. That was done for simplicity and speed. In practice, if you know exactly where the missing characters are, recovering around six missing WIF characters is often feasible on a normal PC within one or two days. The exact time depends on your hardware, how many candidates BTCRecover has to test, and whether duplicate checking is enabled.
One practical tip: if a recovery run will take more than a couple of hours, consider enabling the no dupe checks option. This helps avoid running out of RAM while BTCRecover stores information about already-tested candidates.
Example 2: recovering a hexadecimal key with typos
The second example uses a hexadecimal private key. Here, the key is the correct length, but one or more characters were mistyped when transcribed by hand.
This type of problem is trickier because you may not know which character is wrong. You might have copied an 8 as a B, or missed a small difference between similar-looking characters.
Hexadecimal private keys are 64 characters long and use only 0-9 and A-F. For these, the relevant wildcard is %H, representing one hexadecimal character.
Before we get into the command, there is an important security point: unlike WIF keys with checksums, a hex key can be changed in a way that produces no obvious error message. It may simply create a different address. That means you cannot always tell from the wallet interface alone that your hex key has a typo. You need to compare it against the known paper wallet address.
Steps to recover a damaged hex key with typos
- Put the damaged hexadecimal private key into
passwordlist.txt. - Make sure each line contains one candidate key.
- Use BTCRecover’s typo replacement feature with the
%Hwildcard. - Tell BTCRecover how many typos to allow.
- Provide the expected address from the paper wallet.
By default, BTCRecover checks up to one typo in a password list entry. If you suspect two mistakes, you must tell it to check for two typos. In the video example, the hex key had two character errors, so the first run with only one typo found nothing. After increasing the typo count to two, BTCRecover found the correct private key.

For hex keys, a reasonable rule of thumb is that up to about four typos may be recoverable on a normal PC in a practical amount of time, assuming you know roughly where the damage occurred or can constrain the search. For WIF Base58 keys, around three typos is often more realistic than larger numbers.
The bigger issue with missing characters is exponential growth. Every additional unknown character multiplies the number of possible combinations. One or two missing characters may be easy. Four or five may still be manageable if their positions are known. But once you get into many missing characters, especially in an unknown position, recovery can become impractical no matter how much computing power you have.

QR codes are far more damage-resistant than text strings
This is one of the most important lessons from dealing with old paper wallets: a printed QR code can survive much more physical damage than a printed private key string.
In the video, I demonstrated this using a Bitaddress.org-style QR code. A fresh QR code scanned immediately. Then I drew lines through it. It still scanned. I added more damage. It still scanned. Only when almost a third of the QR code was covered did it finally fail.
That is because QR codes include error detection and correction. Depending on the encoding level, they can recover from significant missing or damaged portions. Bitaddress.org’s default QR setup is especially robust in this regard.
A text private key does not have that same resilience. One wrong character can be enough to break it. That is why I strongly recommend storing both forms if you are dealing with an old paper wallet:
- Store the QR code.
- Store the printed private key text.
- Print them clearly, preferably on a laser printer rather than inkjet if possible.
- Laminate or protect them from water and wear.
- Do not rely only on the written private key string.
If you still have an old paper wallet in 2024, treat it as fragile. It may be valuable, but it is also easy to damage accidentally.
Verifying candidates using the address
When recovering a raw private key, the best verification method is to compare each candidate against the address printed on the paper wallet.
If you have the correct address, BTCRecover can test whether a candidate private key derives that exact address. This is much faster and more reliable than manually importing every guess into a wallet.
If you do not have the address, or if it has been damaged beyond recognition, you can use BTCRecover’s address database feature. This checks candidates against known Bitcoin addresses from blockchain history. That can still help identify a valid key, especially if the wallet was used at some point.
However, if the paper wallet never received funds and no address is available, recovery becomes much harder because you have less information to verify against. In that case, you may need to rely on other clues, such as known partial keys, generation parameters, or transaction history from another source.
What BTCRecover can and cannot do for paper wallets
BTCRecover’s raw private key recovery is not limited to Bitaddress.org paper wallets. It works with many Bitcoin formats and can also be used for some other cryptocurrencies, including Ethereum and various Bitcoin clones. For modern Bitcoin address formats, it supports native SegWit and Pay-to-ScriptHash SegWit types as well.
That said, there are limits:
- Missing characters in known positions are usually easier to recover.
- Typos in a single key can be recovered if the number of errors is small enough.
- Large sections of missing data may not be practically recoverable.
- A damaged QR code may still be scannable even when the text version is unusable.
- If you do not know where the damage occurred, recovery becomes harder and slower.
The feature is useful for small mistakes: a few missing trailing characters, one or two transcribed typos, a smudged section of a key, or a partially damaged printout. It is not magic for badly destroyed wallets with large unknown gaps.
After recovery: importing or sweeping the private key
Once BTCRecover finds the correct private key, the next step is normal wallet import or sweeping. You can import it into a software wallet if you are comfortable doing so, or move the funds to a more secure long-term storage method.
For larger amounts, I would be careful. A paper wallet may have been exposed during generation, printing, scanning, or handling. If the value is significant, consider using offline signing with Electrum or another hardware-based approach that reduces exposure of the private key on an internet-connected machine.
Elipal hardware wallets are one option for importing individual loose private keys and performing offline signing. Even if you do not plan to use them long-term because of their closed-source nature, they can be useful as a bridge from a fragile paper wallet to more robust storage.
If you are unsure how to proceed safely after recovery, or if the wallet value is high enough that mistakes could be costly, professional support may be worth considering. You can request one-on-one support or trusted recovery consultations on my website: recovery services and consultations.
Final thoughts
Old Bitcoin paper wallets are a mixed bag. They can hold real value, but they are also fragile and easy to damage. A single missing character in a WIF key or a small typo in a hex key can make the wallet appear unrecoverable at first glance.
BTCRecover gives you a practical way to repair many of these problems without brute-forcing the entire keyspace. By using wildcards for known missing positions and typo replacement for uncertain characters, you can narrow the search dramatically. The paper wallet address is your best friend in this process because it lets BTCRecover verify candidates quickly.
If you have an old paper wallet:
- Do not repeatedly guess manually.
- Identify whether the key is WIF or hex.
- Note exactly where damage appears to be.
- Use wildcards for missing characters.
- Use typo replacement when a character may be wrong but unknown.
- Verify against the known address whenever possible.
- Store both QR code and text, protected from future damage.
Paper wallets are best avoided in 2024 because they introduce risks at generation, storage, scanning, and import time. But if you already have one, careful recovery can still bring it back to life—especially when the damage is small enough to model with BTCRecover.
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.







