Keys & Seed Tools

John the RipperFree Password Cracker for Windows Users

Free, open-source password cracker for Windows. Learn what it does, how to install it safely, and how to test your own password hashes.

Free Open source Windows: Yes v1.9.0 Updated 11 Oct 2026
10 min read Last update 11 Oct 2026 github.com/openwall/john

John the Ripper is a free, open-source password cracker for system administrators, security students and anyone who needs to recover a password they have lost. It suits people who are comfortable working in a command-line tool and who test only data they own or are authorized to audit. The program is available for Windows as a ready-made build or installer.

Its original purpose was detecting weak Unix passwords, and it now handles many hash formats used across operating systems. Among crypto users, one practical application is recovering a forgotten password to a wallet file you own, which is why it appears in our Keys & Seed Tools category. The latest release is 1.9.0-Jumbo-1, and the project shows recent code activity. Results depend on password strength and on the guesses you supply, so expect a realistic rather than instant outcome.

02

What Is Password Cracking and Why Hashes Matter

Most software does not store your password as plain text. Instead, it saves a hash, a fixed-length string produced by a one-way mathematical function. When you log in, the system hashes what you typed and compares the results. Because the process runs in one direction, a hash cannot simply be reversed.

Password cracking works differently. A tool takes a candidate password, hashes it with the same method, and checks whether the result matches the stored value. Repeating this across a list of likely passwords is called a dictionary attack. If the original password was simple or common, the match arrives quickly. If it was long and random, the search can take an impractical amount of time.

That is why hash formats matter. Different systems use different hashing methods, and a tool must recognize the format before it can test anything. This is the reason John the Ripper supports several formats out of the box and why its jumbo editions cover so many more.

03

How Wordlists, Rules and Incremental Modes Shape a Test

A password audit is only as good as the guesses it makes. The usual approach starts with a wordlist, a plain text file of likely passwords built from common words, names and patterns. Lists you create yourself, based on what you know about the account owner, often perform better than generic ones.

Rules modify each word. A rule might add digits at the end, capitalize the first letter or swap a letter for a symbol. People often make small, predictable changes to passwords they already use, so rules reflect real behavior rather than random guessing.

Incremental mode goes further by trying character combinations without a fixed list. It can find short passwords that appear in no wordlist, but it usually takes longer and works best on short passwords. Combining methods gives you broader coverage without spending hours on a single approach.

For example, imagine an IT team checking whether staff accounts use passwords that follow common patterns. They would run a wordlist first, then rules, and finally incremental mode on the hashes that remain unbroken.

04

Who Uses Password Recovery Tools, and When Is It Appropriate?

John the Ripper suits a few distinct groups. System administrators use it to find weak passwords in their own organization, typically with written permission and under a clear policy. Security students use it in lab environments to learn how hashing works in practice. Individuals occasionally use it to recover access to their own files, including a wallet password they wrote down in an unclear form.

The common thread is ownership and authorization. Running a cracker against someone else's account, file or wallet is illegal in many places and can cause real harm. Before starting, be clear about whose data you are testing and why.

For personal recovery, expect slow progress if the password was long or unusual. Recovery is not guaranteed. Write down what you remember, such as likely words or patterns, because the quality of your guesses largely decides how far the tool gets. If the wallet software offers other recovery options, check those first.

05

Key features

Free and open source

The program costs nothing, and its source code is published on GitHub. That means you can read how it works, review the code yourself or compile it from source if you prefer. Open code also lets the community spot problems more easily than with closed tools.

Ready-made Windows build or installer

Windows users can get a ready-made build or an installer, so there is no need to compile anything. Once installed, you run the tool from the Command Prompt, point it at a hash file and let it test candidate passwords.

Common hash formats out of the box

The core version recognizes several crypt(3) password hash types common on Unix, along with Kerberos/AFS hashes, Windows LM hashes and DES-based tripcodes. These cover many everyday password storage formats, which makes the tool useful for auditing mixed environments.

Jumbo editions with extra formats

Jumbo versions add hundreds of additional hashes and ciphers. The current jumbo release is 1.9.0-Jumbo-1. When a file uses a less common format that the core version does not handle, a jumbo build is the logical choice.

CPU-based processing with optional parallelization

John the Ripper runs on the processor, which is the hardware it is designed around. Where the build supports OpenMP parallelization, the work can be spread across several cores, which can speed up tests on modern multi-core CPUs.

Built-in usage examples

The documentation includes usage examples that the project strongly recommends reading first. Working through them helps beginners understand the command options before they run a real test on their own files.
06

Supported coins

Out of the box, John the Ripper recognizes several crypt(3) hashes common on Unix systems, Kerberos/AFS hashes, Windows LM hashes and DES-based tripcodes. Jumbo editions expand that list to hundreds of additional hashes and ciphers. For crypto users, the relevant point is that a wallet or encrypted file must first be converted into a hash the tool understands before any cracking can begin.

07

How to install John the Ripper on Windows

  1. 1

    Download the file from the official source

    Download only from the official website or the project's GitHub Releases page at github.com/openwall/john. Avoid mirrors, search-engine ads and file-sharing sites, even if they claim to offer the same version. Choose the Windows build or installer for the current release, 1.9.0-Jumbo-1, unless you have a specific reason to use another edition.

  2. 2

    Verify the checksum or signature

    Compare the SHA-256 checksum of the downloaded file with the value published alongside the release. Open a Command Prompt, run the built-in certutil tool with the SHA256 option on the file, and check that the output matches exactly. If a signature is provided, verify it as well. Delete the file and download it again if anything does not match.

  3. 3

    Install or extract the program

    If you received an installer, run it and follow the prompts, choosing a folder you can easily find later. If you received a ready-made build, extract the archive to a dedicated folder such as a tools directory. Keep the test files you plan to audit in a separate location so the program folder stays clean.

  4. Run a first test in the Command Prompt

    Open a Command Prompt in the program folder and check that the executable starts. Read the usage examples in the documentation before running any real test. Begin with a small, practice hash that you created yourself so you can confirm the output format before moving to your own files.

08

How to use John the Ripper

John the Ripper works best when you know what you are testing and why. Start with a file or hash you own, then follow these steps.

  1. Download the Windows build or installer and verify it as described in the installation section.
  2. Create a folder for the tool and a separate folder for test material, and keep an untouched copy of any file you plan to work with.
  3. Convert the protected file into a hash the tool can read, using an extraction utility that matches the file type. John reads hash text, not the original file.
  4. Run John from the Command Prompt with a wordlist, then read the documentation examples to confirm the exact syntax for your hash format.
  5. Let the session run, and check progress in the console. A long session is normal for strong passwords.
  6. When it finishes, use the show option to list any recovered entries. Store the result securely and delete temporary copies of hashes and wordlists you no longer need.
09

Pros & cons

Pros
  • Free and open source, with the source code published on GitHub
  • Ready-made Windows build or installer available
  • Supports several common hash formats out of the box
  • Jumbo editions add hundreds of extra hashes and ciphers
  • Documentation with usage examples that the project recommends
  • Recent code activity in the project repository
Cons
  • Command-line interface with a real learning curve
  • Speed depends on CPU hardware and on password complexity
  • Strong passwords can take an impractical amount of time to recover
  • Antivirus software may flag it, which can complicate installation
10

Is John the Ripper safe?

Download John the Ripper only from the official website or the project's GitHub Releases page. After downloading, verify the SHA-256 checksum against the published value, and check the signature if one is provided. A mismatch means you should discard the file and download it again from the official source. Password cracking tools are often flagged by antivirus software, even when they are legitimate. If that happens, verify the file first and add a narrow exception if needed, but never disable your protection entirely. Never enter a seed phrase, private key or wallet password on third-party websites, and run the tool only on files you own or are authorized to test. The project shows recent code activity, which is reassuring, but it does not replace checking the file.

  • Official source only. Download from github.com/openwall/john. Ignore ads and lookalike domains.
  • Check the SHA-256. Compare the installer hash with the value the developer publishes before running it.
  • Never share your seed phrase. No developer, support agent or website — including CryptApps — will ever ask for it.
11

Alternatives

John the Ripper sits in a different corner of the category than most tools listed here. Ian Coleman BIP39 Tool works offline with BIP39 seed phrases, which makes it a good choice for checking derivations on an isolated machine. PaperVault focuses on storing secrets on paper, combining AES-256-GCM encryption with Shamir's Secret Sharing for backups. Vanity generators such as VanitySearch, Vaniton, Galvanity and Cosmosvanity create addresses that match chosen patterns. John the Ripper does none of these. It tests password guesses against existing hashes to recover access to protected data, so it solves a recovery problem rather than a key-generation or backup problem.

12

Specifications

Price
Free
Type
Open source
License
—
Latest version
1.9.0-Jumbo-1
Last update
11 Oct 2026
Windows support
Yes (Windows build or installer)
Source code
github.com/openwall/john
13

Frequently asked questions

Yes, John the Ripper is free and open source, and its source code is published on GitHub. Free access does not change the responsibilities that come with the tool. You should test only passwords and hashes that you own or are authorized to audit. The time a long test takes can matter more than the price, so plan your sessions with that in mind.

Yes. Windows users can install John the Ripper from a ready-made Windows build or an installer, so compiling from source is not required. After installation, you run the tool from the Command Prompt. Most of your work happens with hash files rather than your original documents, which keeps the workflow focused.

It can test password guesses against a hash extracted from a wallet file you own, but it cannot guarantee success. Recovery depends on how strong the original password was and how good your guesses are. A long, random password may never be found in a reasonable time. If you still have a backup, recovering from it is usually more reliable than cracking.

A jumbo version is an expanded edition of John the Ripper that adds hundreds of extra hash types and ciphers beyond the core set. The current release is 1.9.0-Jumbo-1. Choose a jumbo build when the file you are testing uses a format the core version does not handle, since it covers far more formats in a single tool.

Safety depends on where you get the program and whether you verify it. Use the official website or GitHub Releases page, then check the SHA-256 checksum before running the file. Security tools like this are often flagged by antivirus software, so expect warnings and check the file rather than disabling protection. The safety section above covers the full steps.

No. A password manager stores and generates passwords for you, which helps you avoid weak credentials in the first place. John the Ripper tests guesses against existing hashes to find passwords that are already lost or forgotten. The two tools address opposite problems, and auditors often use cracking tools to find weak passwords that a password manager would have prevented.

14

Verdict

John the Ripper is a strong choice for people who need a free, open-source password auditing tool on Windows, especially administrators and security students who are comfortable with the command line. It is less suited to casual users who want a graphical app or a way to recover any password quickly. Its real value lies in testing your own hashes against wordlists and rules, and in learning how weak passwords fail. Before installing, check the latest version on the official website.

Download now