SHA Hash Generator computes SHA-1, SHA-256, SHA-384 and SHA-512 digests of text using the browser's built-in Web Crypto implementation, so the text is never sent to us.
How to read the result
All four digests are shown as lowercase hexadecimal strings, with the algorithm you chose listed first. Text is hashed as its UTF-8 bytes, so the digest matches what sha256sum and similar tools give for the same text saved as a UTF-8 file without a trailing newline. SHA-1 is included for legacy compatibility and identification only; treat it as deprecated for anything security-relevant, the same caution that applies to MD5.
Defender tips
- Use SHA-256 or stronger for integrity checks (file hashes, commit hashes, checksums published alongside a download).
- Never use a raw SHA hash, at any length, to store a password; these algorithms are fast by design, which is exactly wrong for password storage. Use argon2id, bcrypt or scrypt instead, which are deliberately slow and salted.
- When comparing a computed hash to a published one, compare the full string exactly; a hash is either an exact match or it tells you nothing.
FAQ
Why is SHA-1 still offered if it is deprecated?
It is still encountered in legacy systems, git commit identifiers and some file-verification workflows, so being able to compute and check it remains useful even though it should not be used for new security-relevant work.
Does hashing a password here store it anywhere?
It is never sent to us or logged: hashing runs in your browser through the Web Crypto API. The text is not treated as a secret, though: after a run it is put in the address bar unless it is very long (and so reaches your browser history and any link you share), and if you have accepted optional storage it is kept in this tool's history in your browser for seven days. Do not hash real passwords here.
Does this hash files or only text?
Only the text you enter; it is not a file-hashing utility.