JSON WalletPrivacy-first JSON & API workspace

Hash Generator

Compute a cryptographic hash of any text using the browser's Web Crypto API. Choose the algorithm below — the digest is computed locally.

Text
Hash (hex)

Generate a cryptographic hash

A cryptographic hash turns any text into a fixed-length fingerprint. The same input always produces the same digest, while the smallest change produces a completely different one — which makes hashes ideal for verifying integrity, indexing content and deduplication. This tool computes SHA-1, SHA-256, SHA-384 and SHA-512 digests with the browser's built-in Web Crypto API, so your text never leaves the page.

How to use it

  1. Type or paste the text you want to hash into the input.
  2. Choose an Algorithm (SHA-256 is a good default).
  3. Copy the hex digest that appears on the right.

A worked example

Hashing the text:

The quick brown fox jumps over the lazy dog

with SHA-256 produces:

d7a8fbb307d7809469ca9abcb0082e4f8d5651e46d3cdb762d02d0bf37c9e592

Change a single letter and the entire digest changes — the hallmark of a good hash function.

When you would reach for it

Computing a checksum to confirm a file or message arrived intact, generating a cache key from content, deduplicating records by their digest, or comparing a value against a known hash. For random identifiers rather than content-derived ones, use the UUID generator.

Privacy

Hashing runs entirely in your browser and works offline once loaded. Your input is never uploaded or stored, so it is safe to hash sensitive text.

Frequently asked questions

Is MD5 supported?

No. The Web Crypto API does not provide MD5 because it is cryptographically broken. Use SHA-256 or stronger.

Which algorithm should I use?

SHA-256 is the sensible default — fast, widely supported and secure. Choose SHA-384 or SHA-512 when a longer digest is required. SHA-1 is included only for compatibility with legacy systems; do not use it for new security-sensitive work.

What is a hash good for?

Verifying that data has not changed (checksums), indexing content by its digest, deduplication, and as a building block in signatures. A hash is one-way — you cannot recover the input from the digest.

Why does the same input always give the same hash?

Hash functions are deterministic: identical input always produces an identical digest. That is exactly what makes them useful for integrity checks — any change to the input, even one character, produces a completely different hash.

Should I use this to store passwords?

No. Plain SHA hashes are too fast for password storage. Use a purpose-built, salted algorithm such as bcrypt, scrypt or Argon2 on your server instead.

Where does hashing happen?

Entirely in your browser via crypto.subtle.digest — your input is never sent anywhere.

Press ⌘ K for commands