How it works

Compute a SHA-family hash of any text, with the algorithm of your choice, live as you type.

Type or paste the text and pick an algorithm: SHA-1 (20-byte digest, deprecated for security but still common), SHA-256 (32-byte, modern standard), SHA-384, or SHA-512. The result is a hex string, computed via the Web Crypto API. Live update with a small debounce so fast typing doesn't thrash the hasher. SHA-1 is included for legacy use cases (file checksums in older systems, git's internal hash) but should not be used for new security applications because collisions are known. SHA-256 is the modern default. SHA-512 produces a longer digest but isn't more secure than SHA-256 for most purposes, just slower. For hashing files, use the Hash file tool, which streams over the file's bytes.

How to use it

1. Type or paste your text. The hex digest updates live with a small debounce.
2. Pick an algorithm. SHA-256 is the modern default; SHA-1 only for legacy compatibility.
3. Copy the digest. The output matches shasum and openssl dgst on the same input — computed entirely in your browser.

Frequently asked questions

Should I use SHA-1?

Only for legacy compatibility. For security (anything someone might try to forge), SHA-256 or above. SHA-1 has known collision attacks.

What's the difference between SHA-256 and SHA-512?

SHA-512 produces a longer digest (128 hex chars vs 64). It's not more secure for typical use; it's just bigger. On 64-bit CPUs, SHA-512 can be slightly faster than SHA-256.

Is the text uploaded?

No. Hashing runs in your browser via Web Crypto. Text and digest stay local.

Are these the same hashes I'd get from shasum?

Yes. The output matches shasum -a 256 (or 1, 384, 512) and openssl dgst on the same input.