SHA Hash Generator
Hash any text into SHA-1, SHA-256, SHA-384 and SHA-512 hex digests at once, using your browser’s native Web Crypto engine. Nothing leaves your device, and each digest has its own copy button.
How to use
- Type or paste the text you want to hash into the input box.
- Click "Compute hashes" — all four digests are calculated with the Web Crypto API.
- Copy the digest you need with its own button, or compare it against an expected checksum.
Frequently asked questions
Which hash should I use?
For file integrity, build artifacts and checksums, use SHA-256 — it is fast, widely supported and secure. SHA-384 and SHA-512 suit the same jobs with a longer digest. Avoid SHA-1 for anything new: it has been broken for collision resistance since 2017, so treat it as a legacy format for verifying old systems only.
Can I hash passwords with this tool?
No — and you should not store plain SHA hashes of passwords anywhere. Hashing passwords requires a dedicated key-derivation function such as bcrypt, scrypt or Argon2, which are deliberately slow, use a per-user salt and resist GPU cracking. Plain SHA digests are computed in microseconds and fall to dictionary attacks almost instantly.
Is my text uploaded anywhere?
Never. The digests are computed locally with crypto.subtle, part of the Web Crypto API built into your browser, over an HTTPS page. Your text and the resulting hashes never leave your device, so you can safely hash snippets of code, keys or confidential strings for comparison.
Why do the hashes look different for similar texts?
SHA functions are avalanche-sensitive: changing a single character, adding one space or switching a letter case completely changes the output. That is the property that makes them useful for verification — even the tiniest tampering with a file or message produces an entirely different digest that is impossible to miss.
How do I verify a downloaded file?
Publishers often publish a SHA-256 checksum next to downloads. Compute the digest of your copy, paste both values side by side and compare them character by character — or let your operating system’s checksum utility do it. Matching digests mean the file arrived bit-for-bit identical; any difference means it is corrupted or tampered with.