🔑 Bcrypt Hash Generator
Generate and verify bcrypt password hashes in your browser.
Last updated: November 8, 2026 · By the BoltQuickTools team
Generate Hash
Each step up in cost doubles the work. OWASP suggests a cost of at least 10.
Verify Hash
Create a bcrypt hash or check one against a password
Seeding a test user, resetting a local admin account by hand, or confirming that a stored hash really matches a password all need a bcrypt value on demand. This page makes one, and checks one, without writing a script.
The two panels
- In Generate Hash, enter a Password, set Cost with the slider (4 to 15, default 12) and click Generate Hash.
- Click the finished hash to copy it.
- In Verify Hash, enter a Password and paste a Hash, then click Verify. The answer reads
MATCH - password matches the hashorNO MATCH - password does not match the hash.
Reading a hash, piece by piece
A hash at cost 12 looks like this:
$2a$12$a6QdohzZ5BWv1erFgtNHPOvtHY88VYpRD.7mMxNM/n2IcEGAI4o8m
| Part | Meaning |
|---|---|
$2a$ | bcrypt version |
12 | cost: 4,096 rounds of the key schedule (2 to the power of 12) |
a6QdohzZ5BWv1erFgtNHPO | random salt, 22 characters |
vtHY88VYpRD.7mMxNM/n2IcEGAI4o8m | the hash itself, 31 characters |
Yours will differ, because a new random salt is generated each time. Two hashes of one password look different but both verify, since the salt travels inside the string.
Limits to plan around
- The hashing library comes from a CDN. The page downloads bcrypt.js 2.4.3 from cdnjs when it opens. Hashing then happens in your browser, and the tool's code does not send your password anywhere. If the CDN is blocked, you will see
Error: bcrypt is not defined. - Only the first 72 bytes count. A hash of 72 letters also verifies as a MATCH against those 72 letters plus anything added to the end. Accented characters and emoji take several bytes each, so the limit arrives sooner than the character count suggests.
- A malformed hash can look like a wrong password. Anything that is not exactly 60 characters returns NO MATCH, including a hash truncated by a copy mistake. Only a 60-character string with a bad header reports
Invalid hash format. - The tab freezes while hashing. The work is synchronous, and every step of cost doubles it. High costs in the browser can hold the page for several seconds.
- The time beside the slider is an estimate from a formula, not a measurement of your device. To choose a cost for production, time it on your own server.
Will these hashes work in my backend?
The output always uses the $2a$ prefix, which mainstream bcrypt libraries accept. The verifier here also accepts $2b$ and PHP's $2y$ strings.
Should I type a real password here?
Use throwaway values where you can. The password field shows plain text, and in a normal application the server should hash real passwords at signup, so a browser tool is rarely the right place for them.
Can I use this for file checksums?
No. bcrypt is deliberately slow, salted and limited to 72 bytes, which suits passwords only. For checksums, use the hash generator. For choosing between bcrypt and newer options, read the password hashing article.