Hash Generator
SHA-256, SHA-512, SHA-384, and SHA-1 digests of any text, computed with the browser's WebCrypto API — all four at once, nothing uploaded.
| SHA-256 | — | |
| SHA-512 | — | |
| SHA-384 | — | |
| SHA-1 (legacy — collision-broken, avoid for security) | — |
How to use this tool
- Type or paste your text.
- All four digests compute instantly — copy the one you need.
How it works
Hashes are computed with the browser's native WebCrypto API (crypto.subtle.digest), so they're fast and your text never leaves the page. A hash is a one-way fingerprint: the same input always yields the same output, and any change — even one character — produces a completely different digest.
MD5 is deliberately absent: it's cryptographically broken, and WebCrypto doesn't implement it. SHA-1 is included because legacy systems still reference it, but it too is considered broken for collision resistance — use SHA-256 or better for anything new.
Frequently asked questions
Can I hash a file or compute an HMAC?
Yes — switch to File mode to hash a local file (up to 200 MB, read locally via the Web Crypto API) or HMAC mode to compute keyed HMAC-SHA digests. The HMAC implementation matches the RFC 4231 test vectors.
Why is there no MD5 option?
Browsers' built-in Web Crypto API deliberately omits MD5 because it is cryptographically broken. If you need an MD5 checksum for a legacy system, use a local command-line tool — and never use MD5 for anything security-related.
Which hash should I use?
SHA-256 is the safe default for checksums and fingerprints; SHA-512 where you want a larger digest. Avoid SHA-1 and MD5 for anything security-relevant — both have practical collision attacks.
Why is MD5 missing?
It's been broken for two decades and the browser's WebCrypto API rightly doesn't implement it. If a legacy system demands MD5, treat that as the bug.
Can a hash be reversed to get my text?
No — hashes are one-way. But identical inputs give identical hashes, so short or guessable inputs (like passwords) can be brute-forced by trying candidates. That's why password storage uses salted, slow hashes instead of plain SHA.