Create bcrypt password hashes for your app's users or config files, or check whether a password matches a hash from your database, all without the password leaving your browser. Choose the cost to balance security and login speed, see the salt and cost inside any hash, and get a warning when bcrypt would silently cut a long password.
| Cost | Rounds | Typical use |
|---|---|---|
| 4 | 16 | Tests only |
| 10 | 1,024 | Common default |
| 12 | 4,096 | Stronger logins |
| 14 | 16,384 | High security, slow |
10 to 12 for logins. Each +1 doubles the time to hash, for you and for an attacker.
Each hash gets a new random salt. Every one of them still verifies against the same password.
Yes. $2y$, $2a$ and $2b$ use the same algorithm for normal passwords.
bcrypt only uses the first 72 bytes. Longer passwords are cut silently, and the tool warns you.
No. Hashing and checking run in your browser.
Hashing uses bcryptjs, a pure-JavaScript implementation of bcrypt. A fresh 16-byte salt comes from the browser's cryptographic random generator, and the cost sets the number of key-expansion rounds to 2^cost. The work runs in small chunks with a progress bar, so the page stays responsive even at cost 15. The result is a standard $2b$ string: cost, 22 salt characters, then 31 hash characters. Verification re-hashes your password with the salt and cost read from the existing hash. $2y$ (PHP) and $2x$ prefixes are read as $2b$, because the algorithm is identical for normal passwords. bcrypt only uses the first 72 bytes of a password (UTF-8 bytes, not characters), so the tool warns when a password is longer. The time estimate is measured on your device and doubles with each step of cost.