KeyStone
Get in touch
EN ES
← All articles

DIY · btcrecover

btcrecover explained for people who don’t program

btcrecover is the best-known free tool for recovering wallet passwords and incomplete phrases. It isn’t magic and it guesses nothing: all it does is test, very fast, the candidates you describe to it. Its entire usefulness depends on how well you describe them.

September 27, 2026 · 5-minute read

What it does, in plain terms

You give it your wallet file and a description of what your password was like. It generates every variant matching that description and tests them one by one against the file, far faster than you could. When one works, it tells you.

That is all. It decrypts nothing, breaks nothing and has no privileged access. It is a testing machine, and the value lies in you narrowing down what to test.

What kind of description it understands

You can tell it things like: «one of these six words, with or without an initial capital, followed by a two-to-four-digit number, and sometimes an exclamation mark at the end». From that it generates a few thousand candidates and tests them. It also understands more human things: «this password but with one letter changed», or «these words in any order».

That last capability solves a great many real cases: if you are sure of your password but it won’t open, it very likely fails by one character. Asking it to test every variant one character away is one of the most productive things you can do.

What you need to use it

  • A computer and some patience. Programming isn’t required, but following written instructions precisely is, along with typing commands in a terminal and editing a text file.
  • Your wallet file, as a copy.
  • An honest, organised description of what you remember. That is what decides the result.
  • Time: depending on your wallet, it can take hours or weeks.

What most often goes wrong

  1. Describing the password wrongly. If you tell it the password started with a capital and it didn’t, it will never find it even if it is one character away.
  2. Being too ambitious. Asking for «anything eight characters long» is asking the impossible: the program doesn’t complain, it just takes centuries.
  3. Downloading it from somewhere other than the official source. The real risk in all this. Tampered copies circulate.
  4. Working on the original file. Always on copies.
  5. Giving up after the first configuration. Normally several different hypotheses have to be tried, not one.
Point three is the only one that can cost you the whole wallet. Download only from the project’s official repository, typing the address by hand, and be suspicious of any «easy to use» or «with a graphical interface» version offered on a forum or in a video.

Is it for you?

If you have two or three clear candidates or a well-defined pattern, yes, and you will probably solve it in an afternoon. If your memory is hazy and you don’t know where to start describing it, the tool won’t help you on its own: what is missing there isn’t a program, it is the judgement to order the hypotheses correctly. I expand on it in when it is worth trying it yourself.

Keep reading