Free Password Hash Generator

Create secure password hashes with the right algorithm for the job. Choose battle-tested bcrypt or salted SHA-256/SHA-512, get a fresh cryptographically random salt every time, and verify hashes against passwords — all computed locally, never uploaded.

Password hash


    

Verify a hash

Verification

Private by design. This tool runs 100% in your browser — your code is never uploaded to any server.

How to Use the Password Hash Generator

  1. Type the password to hash.
  2. Choose an algorithm: bcrypt (recommended) or salted SHA-256/SHA-512.
  3. Click Generate — a fresh random salt is created automatically.
  4. Use the verifier to check any password against a generated hash.

Features

Bcrypt mode uses the proven bcryptjs implementation with adjustable cost and per-hash random salts in standard $2a$ format. Salted SHA modes generate a 128-bit random salt via the Web Crypto API and output a self-describing salt$hash string. The built-in verifier handles both formats, so you can confirm hashes without writing any code.

Benefits & Use Cases

Developers seed local databases and test fixtures with realistic hashes; teams prototype auth flows before choosing a library; students compare how bcrypt output differs from salted SHA. Because everything runs on your CPU, test passwords never cross the network.

Tips

For anything resembling production, choose bcrypt with cost 10–12 — plain salted SHA is too fast and therefore too guessable for password storage. And remember: real user passwords must be hashed on your server, never in a user’s browser.

Frequently Asked Questions

Which password hashing algorithm should I use?

Bcrypt (or Argon2/scrypt) for real password storage — they are deliberately slow, which defeats brute-force attacks. Fast hashes like SHA-256, even salted, are only acceptable for non-security purposes.

What is a salt and why does it matter?

A salt is random data mixed into the hash so identical passwords produce different hashes. It defeats rainbow-table attacks, where attackers precompute hashes of common passwords.

Can I store the salt next to the hash?

Yes — salts are not secret. Bcrypt embeds the salt in its output string; this tool’s salted-SHA mode outputs salt and hash together so verification is self-contained.

How do I verify a password later?

Hash the candidate password with the same algorithm, salt, and cost, then compare the results — exactly what the verifier on this page does. Never compare plaintext passwords directly.

Is it safe to hash real passwords here?

Hashing is local, so nothing is transmitted. But as a rule, generate hashes for test and development use here; real user registration and login hashing belongs on your server.

Why is bcrypt slower than SHA?

That slowness is the security feature: it makes each password guess expensive for attackers while remaining unnoticeable (a fraction of a second) for legitimate logins.

Related Tools