Hashing tools / Bcrypt

Bcrypt Hash Generator

Generate salted password hashes or verify a password against an existing bcrypt hash locally.

01

Generate bcrypt hash

Each hash uses a fresh cryptographically random salt.

BCRYPT
Work factor

Higher work factors slow down both attackers and legitimate checks. 10 is the baseline selected for this browser tool.

Ready to hash?Bcrypt is intentionally slow and cannot be reversed to recover the password.
02

Verify bcrypt hash

Compare a password to an existing $2a$, $2b$, or $2y$ bcrypt hash.

VERIFY
60 characters
Ready to verify?The result only confirms whether the supplied password matches the hash.
Password-security guide

Bcrypt password hashing: how and when to use it

Learn how bcrypt salts and hashes passwords and why password hashing is not encryption.

Bcrypt is a password-hashing function, not an encryption algorithm. A password hash is intentionally one-way: an application stores the hash and, at sign-in, hashes the supplied password using the same settings to see whether it matches. Unlike a reversible encrypted password, a bcrypt hash is designed to make large-scale guessing costly. Each newly generated bcrypt hash includes a random salt, so the same password produces different stored values over time.

This tool can create a bcrypt hash or verify a candidate password against an existing bcrypt value. The work factor controls how expensive the calculation is; increasing it slows down both legitimate logins and attackers. Select a cost that is appropriate for your infrastructure, then revisit it periodically as hardware improves. When verifying, use the complete stored bcrypt string exactly as saved. It already carries the information needed to repeat the calculation, including the cost and salt.

For a real service, hash passwords on a trusted server using a maintained library, enforce rate limiting and multi-factor authentication where appropriate, and protect the account-recovery flow. Bcrypt has practical input-length limitations, so applications should define and test their password-handling rules. Never encrypt a password merely to store it, never log passwords, and never use MD5 or SHA-256 alone as a password hash. This browser workspace is useful for understanding values and compatibility checks; avoid entering high-value production credentials into any page you do not fully operate.

How it works

A careful workflow

  1. Enter a test password and choose a cost factor appropriate for a test or compatibility check.
  2. Store the complete resulting bcrypt value, including its prefix, cost, salt, and hash.
  3. To verify, compare using the full bcrypt value rather than generating a fresh hash yourself.
Common questions

FAQ

Why do matching passwords generate different hashes?

Bcrypt uses a random salt, which makes identical passwords produce different stored hashes.

Can bcrypt decrypt a password?

No. Verification compares a candidate password with a stored hash; it does not recover the original password.

What is the cost factor?

It controls the amount of computational work bcrypt performs. Higher values make guessing more expensive but also slow legitimate checks.