Hashcat vs John the Ripper: Which Is Faster?

Hashcat is GPU-first and needs the right hash mode; John self-detects and ships the converters that pull hashes out of files. Where each wins, and how to use both together.

Short answer: With a GPU and a hash mode you already know, Hashcat is much faster. With an unusual file format or a hash you cannot identify, start with John, whose converters and auto-detection get you to something crackable at all. Most audits use John to extract and identify, then hand the fast hashes to Hashcat.

Executive Verdict: When to Choose Each

Choose Hashcat if…

Best for raw speed: hundreds of hash modes on the GPU, a mature rule and mask engine, and a canonical example for every mode so a wrong format shows up immediately.

Choose John the Ripper if…

Best for getting started at all: format auto-detection, the *2john converters for archives, PDFs, keys and vaults, and a CPU engine that still works on a laptop with no discrete GPU.

Feature-by-Feature Technical Matrix

Dimension Hashcat John the Ripper
Engine GPU-first: OpenCL, CUDA, HIP, Metal CPU-first with OpenMP; GPU support is limited and build dependent
Choosing the algorithm You pass -m 1000; hashcat 7 can guess with --identify Auto-detects by default; --format= forces a format when the guess is wrong
Hash modes / formats 500+ modes, each with a fixed input layout Hundreds of formats in the jumbo build
Getting hashes out of files Nothing built in; a converter has to run first The *2john suite: zip2john, rar2john, pdf2john, office2john, ssh2john, keepass2john
Masks -a 3 ?l?l?l?d?d --mask=?l?l?l?d?d
Rules -r rules/best64.rule, with a large rule ecosystem --rules, and jumbo builds also ship --rules=Jumbo
Show recovered passwords --show john --show hashes.txt
Strongest at Fast unsalted hashes at scale: NTLM, MD5, SHA-1, SHA-256, WPA Slow or unusual formats, encrypted containers, anything that needs a converter first

Speed is the wrong question to answer from a blog table

Search this comparison and you will find confident numbers: 20x faster, 184,000 hashes per second, a neat table of modes. Each of those describes one GPU, one build and one hash mode on the day it was measured. On your hardware the same test can be wrong by an order of magnitude, and for deliberately slow algorithms the gap collapses, because bcrypt, scrypt and Argon2 are designed so that parallelism buys much less.

Measure it instead. Two commands, thirty seconds, on the machine you actually own. Compare the two rates for the mode you need, not for MD5, and let that decide the tool.

Where John is not optional

Hashcat takes a hash in a documented layout. It does not know how to open an archive, a PDF, a KeePass database or an SSH private key and pull the verifier out of it. The converters do that, and they ship with John.

Even when the plan is to crack on the GPU, the normal path is: convert with the matching script, load the result in John to confirm the format, then move the fast hashes to Hashcat. Skipping the converter is how a session ends before it starts.

Where Hashcat is not optional

Rule-based mutation is the home turf. A base wordlist plus a rule file tests far more realistic password shapes per second than brute force, the rule files are portable, and the community has spent years tuning them.

Every mode also has a canonical example, so the exact layout can be copied instead of guessed. That one command removes most of the wrong format pain.

A workflow that uses both

In a real engagement the two tools are not competitors, they are stages.

  • Identify: list the supported formats, or paste the string into a hash identifier, before choosing anything.
  • Extract: run the matching converter for a file, and check a raw hash against the canonical example for the mode.
  • Benchmark: run the GPU benchmark and the CPU benchmark for that exact mode, then pick the faster engine.
  • Attack with a plan: wordlist plus rules first, masks second, brute force last. Switching tools will not fix a bad candidate set.
  • Record: show the recovered passwords from both tools, then turn the recovery rate into a policy finding.

Which to install first

If a discrete GPU is available and the hashes are fast, install Hashcat first. If the input is a file, an unusual format or a hash of unknown type, install John first and add Hashcat once the hashes are extracted and identified. On a laptop with no GPU, John across all cores is the practical starting point, and Hashcat gains little.

Side-by-Side CLI & Operational Workflow

Hashcat Example

# Benchmark this GPU for the mode you actually need
hashcat -b -m 1000

# Wordlist plus rules, then show what was recovered
hashcat -m 1000 -a 0 hashes.txt rockyou.txt -r rules/best64.rule
hashcat -m 1000 hashes.txt --show

John the Ripper Example

# Benchmark this CPU for the same mode
john --test=10 --format=nt

# Wordlist plus rules, then show what was recovered
john --format=nt --wordlist=rockyou.txt --rules hashes.txt
john --show hashes.txt

Frequently Asked Questions

Is Hashcat always faster than John the Ripper?

No. It is faster when a GPU is available and the hash is cheap to compute. For slow memory-hard algorithms the gap narrows sharply, and for a format only John supports the speed question does not arise.

Can John the Ripper use a GPU?

Partially, through OpenCL in some jumbo builds, but GPU throughput is not the design centre. If GPU speed is the goal, that is Hashcat.

Can Hashcat read converter output?

Often yes once the matching mode is known, but the layouts differ and converter output can carry fields a mode rejects. Load it in John first to confirm the format, then move it.

Which is easier for a beginner?

John, because it detects the format for you. Hashcat needs a mode number first, and the canonical example list is the fastest way past that step.

Are these tools legal to use?

Both are legal to install and to use on hashes you own or are authorised to test. Running them against credentials that are not yours is a criminal offence in most jurisdictions.


Related Tools, Cheat Sheets & Comparisons