Bcrypt Hash Generator

Generates a fresh salted bcrypt hash with a cost clamped from 4 through 14; this branch has no verifier.

Bcrypt Generator · Client runtimeSandboxed
Formatted results will render here in real time.

About this bcrypt hash generator

Generates a fresh salted bcrypt hash with a cost clamped from 4 through 14; this branch has no verifier Runs entirely in-memory using Web Crypto primitives to keep sensitive tokens, certificates, and cryptographic keys secure from third-party interception.

Encoding & cryptographic principles

Generates a fresh bcrypt hash for the supplied password with a cost clamped from 4 through 14. This branch returns a hash only; it does not verify an existing bcrypt hash.

Worked verification example

Scenario: Generate a bcrypt hash with an accepted cost value.

Sample input:

{"password":"test-password","cost":10}

Processing: Uses bcryptjs hashSync with a newly generated random salt and clamps cost to the supported range 4–14.

Illustrative output:

A new bcrypt hash on every run; its random salt means the exact encoded hash is not fixed.

Security parameters & input constraints

Noninteger or nonfinite costs are rejected; out-of-range integers are clamped to 4–14. Each run salts anew, so hashes differ. This generator does not compare a candidate with an existing hash or store credentials.

Cryptographic digests, encoded strings, and signatures generated by Bcrypt Hash Generator should be verified against target authentication systems before production use.

Client-side Web Crypto boundary

Key derivation, hashing, and encoding in Bcrypt Hash Generator execute in local memory using Web Crypto APIs without remote socket transmission.

Cryptographic specifications & RFC standards

Technical specifications and cryptographic RFC standards governing algorithms and key representations:

Bcrypt Hash Generator verification · Audit standards

How to use it

  1. Enter a password and optional integer cost in JSON; the default cost is 10.
  2. Run bcryptjs hashSync locally with the cost clamped to 4 through 14 and a fresh random salt.
  3. Read the encoded bcrypt hash and effective cost in JSON.

Frequently asked questions

How are bcrypt `cost` and password handled?+

Missing, `null`, or blank `cost` is 10. A supplied cost must be a finite safe integer, then is limited to 4 through 14. The tool uses `password`, then `text`; an explicit empty password stays empty, including after leading JSON whitespace.

How can I create a bcrypt hash with cost 4?+

Enter `{ "password": "abc", "cost": 4 }`. The returned JSON reports `"algorithm": "bcrypt"`, `"cost": 4`, and a salted hash whose exact value changes on a new run.

Why do identical passwords have different hashes?+

bcrypt creates a fresh salt for each hash, so the encoded result normally changes. Store the returned hash, then verify it against the submitted password in another implementation; this page generates hashes only and does not provide verification.

Is this a complete password system?+

No. It generates a local bcrypt hash. A production account system still needs secure storage, rate limits, password policy, recovery, and server-side access controls.