Learn
History for this tool
The most recent data you entered in this tool, stored only in this browser.
Save what you type here, in this browser? Your work would go into this browser's local storage, so a refresh or a trip to another tool does not wipe it. You also get a short list of previous entries under the form, each one restorable with a click. Nothing is ever uploaded, and there is no account.
Being straight about the trade-off: anything kept there can be read by anyone who can use this browser profile, and by any script that later runs on this site. A tool page can hold a private key, a password or a signed token. Saving is convenient; it is not private.
Saved on this device
Your inputs and history are stored locally.
Not saved
This page forgets your work when you leave it.
About this tool
Hash a password with bcrypt, or verify a password against an existing bcrypt hash. The cost factor controls how much work each hash takes, and that expense is the whole point.Questions
- Which cost factor should I use?
- Test the cost on the system that will verify the passwords, and follow your application’s current security policy. Higher costs take more work. This tool does not measure or report hash duration, so it cannot choose a cost for your server. Cost
4in the example above is for learning only. - Why does the same password give a different hash every time?
- Because bcrypt generates a random salt per hash and stores it inside the result. That is what stops two users who chose the same password from having the same hash.