Bcrypt Hash Verifier
Enter a password and a bcrypt hash to find out whether they match. The check runs in your browser and nothing is sent to a server.
Use the tool
Why this tool exists
When a login fails in development, you need to know whether the stored hash, the password or the code is at fault. Writing a script just to call a compare function is a detour, and web pages that verify on a server would receive both your password and its hash.
This verifier recomputes the hash locally. It reads the version, cost and salt from the hash you give, hashes your password with those same settings and compares the result to the stored value, in a way that does not stop at the first difference. It accepts the 2a, 2b and 2y prefixes and costs up to 16, though high costs can take many seconds. The result is a clear match or no match message. Use test credentials and avoid pasting live production secrets.
How to use it
- Type or paste the password in the first box.
- Paste the full bcrypt hash into the second box.
- Run the tool.
- Read whether it says MATCH or NO MATCH.
Frequently asked questions
What does a valid bcrypt hash look like?
It starts with $2a$, $2b$ or $2y$, then a two-digit cost, then 53 characters: a 22-character salt and a 31-character hash. If the format is wrong, the tool tells you instead of guessing.
Why is it slow with some hashes?
Verification repeats the original work, and each cost step doubles it. A cost of 14 or 16 can take many seconds in a browser, by design, since that is what slows down attackers.
Why does a correct password say no match?
Common causes are a trailing space or newline in the password, a different encoding, a hash truncated when copied, or a password longer than 72 bytes that was altered before hashing. Check each in turn.
Is my password sent anywhere?
No. Both values stay in your browser while the check runs. Even so, do not use this page for live production credentials; prefer test accounts.