About the Bcrypt Generator
This tool creates bcrypt password hashes and verifies passwords against existing bcrypt hashes. You pick the cost factor (4 to 12) and the tool runs entirely in your browser using bcryptjs, which loads only when needed. Nothing is uploaded to a server and there is no installation. Use it to test login flows, create sample hashes for development, or check whether a password matches a stored bcrypt hash. The page warns about common pitfalls like the roughly 72-byte UTF-8 input limit and differences in prefix versions such as $2a and $2b. Developers, testers and security students use it to try cost settings and see timing effects before coding server logic. The page also lists short notes about salt generation, how cost affects hashing time, and verification behavior. Compared with many online generators, FreeToolr shows cost selection, a verify mode, and clear client-side privacy so you can test safely without sending secrets to remote servers.
How to use it
- 1Enter the password text you want to hash or verify.
- 2Choose a cost value between 4 and 12.
- 3Click Generate to create a bcrypt hash or Verify to check a password against a hash.
- 4Copy the produced ~60-character hash or view the verification result.
Worked example
Input: password = "myP@ssw0rd", cost = 10. Sample output: $2b$10$abcdefghijklmnopqrstuvR1c2D3e4F5g6H7i8J9k0LmN. Note: salt is random so your actual hash will differ each run.
How it works
Hashes a password with bcrypt at cost 4 to 12 and checks a password against an existing bcrypt hashRuns in the browser with bcryptjs, loaded only when neededWorks in the browser with nothing to installSource: A Future-Adaptable Password Scheme (Provos & Mazières, 1999)OWASP Password Storage Cheat Sheet. Last checked 5 November 2026.
What it is good for
- Client-side hashing with bcryptjs so data stays in your browser.
- You pick cost 4 to 12 to test speed and strength.
- Built-in verify mode to check a password against a stored bcrypt hash.
- Inputs longer than about 72 UTF-8 bytes may be truncated by some bcrypt implementations.
- Do not paste real production passwords into third-party pages; use local server-side hashing for production.
Questions people ask
What does the cost number mean?
Cost is the work factor exponent. A cost of 10 means the algorithm runs 2^10 internal rounds. Higher cost increases CPU time for hashing and slows brute-force attempts.
Why do two hashes for the same password look different?
Each bcrypt hash uses a random 22-character salt. The salt is stored inside the hash, so verification still works even though outputs differ.
Is this tool sending my password to a server?
No. Hashing runs in your browser with bcryptjs that loads only when you use the tool. Nothing is uploaded or stored on our servers.
Which bcrypt prefix should I expect?
Modern implementations commonly use $2b$ as the prefix. Other prefixes like $2a$ and $2y$ appear in older implementations. Check your system's expected prefix when comparing hashes.
Should I use bcrypt for new projects?
Bcrypt is still widely used and acceptable for many systems. Security guidance such as OWASP and NIST note memory-hard algorithms like Argon2 are preferred when you can tune memory and threads.
What about long passwords and non-ASCII characters?
Bcrypt implementations typically process up to around 72 bytes of input. Use UTF-8 encoding and consider pre-hashing if you need to support longer inputs consistently across libraries.
Help keep every tool free
FreeToolr stays free because people help it grow. Share a tool you like, tell us what to build next, or support us on Ko-fi.