Hashcat to John Rule Converter

Paste Hashcat rules — get a John the Ripper config file ready to use.

How it works

John the Ripper supports Hashcat rule syntax natively via the !! hashcat logic ON directive. This tool wraps your Hashcat rules in a valid John config section so you can drop it straight into a John command.

1. Paste your Hashcat rules: one rule per line, exactly as they appear in a Hashcat .rule file (e.g. l $1 so0).
2. Set a ruleset name: the name used in the config section header and the --rules flag when running John.
3. Download the .conf file: the tool wraps the rules in the required John format and generates the ready-to-use config.
4. Run John: pass the .conf file with --config and the ruleset name with --rules. John applies every Hashcat rule to each wordlist entry before hashing.

Generated .conf structure

[List.Rules:yourRulesetName] !! hashcat logic ON <your hashcat rules> !! hashcat logic OFF

Common Hashcat rule functions

Any valid Hashcat rule function passes through unchanged — the converter only wraps, never modifies. Common examples:

Rule	Effect	Example
:	No-op: pass the word unchanged	password → password
l	Lowercase all characters	PaSSworD → password
u	Uppercase all characters	password → PASSWORD
c	Capitalise first letter, lowercase rest	pASSWORD → Password
r	Reverse the word	password → drowssap
$X	Append character X	password → password1
^X	Prepend character X	password → !password
sXY	Replace all X with Y	password → p@ssword (sa@)
d	Duplicate the word	password → passwordpassword
t	Toggle case of all characters	Password → pASSWORD

FAQ

Why not just use John's built-in rule syntax?

Hashcat rules are more widely shared. Leaked rulesets like OneRuleToRuleThemAll, d3adhob0, and best64.rule are all in Hashcat format. This converter lets you use them in John without rewriting every rule manually.

Are all Hashcat rules supported?

John's hashcat logic mode supports the vast majority of Hashcat rule functions. A small number of advanced Hashcat-only functions (such as complex memory rules) may not execute. John will skip unrecognised functions rather than error.

Is my ruleset stored on the server?

No. Rules are processed in memory on submit and immediately discarded. Nothing is logged or stored.

Can I chain multiple rules?

Yes. Each line is an independent rule chain applied to every wordlist entry. John processes all rules in the section, generating one output candidate per rule per word.