Hash Generator (SHA)
Compute SHA-1, SHA-256, SHA-384 or SHA-512 digests of any text using the browser's WebCrypto engine — the text never leaves your device.
Reviewed 17 November 2026 · Free · No account needed
How to use
- Paste the text to hash.
- Pick an algorithm (SHA-1, SHA-256, SHA-384 or SHA-512).
- Click Compute and copy the lowercase hex digest.
Example
Input: hello (SHA-256)
Output: 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824
How it works
The input is hashed with the selected algorithm (SHA-1, SHA-256, SHA-384 or SHA-512) using the Web Crypto API. The same input always produces the same hash; the hash cannot be reversed to recover the input.
The text is UTF-8 encoded and digested by the browser's WebCrypto engine (crypto.subtle.digest) with SHA-1, SHA-256, SHA-384 or SHA-512; the digest is printed as lowercase hex. It is a plain hash — no salt, no key, no encryption.
"hello" hashed with SHA-256 gives 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824 — the same input always yields the same digest.
Edge cases to know
- SHA family only — MD5 is not offered because it is cryptographically broken.
- Hashing is one-way: a digest cannot be reversed into the original text, so this is not a password store or an encryption tool.
- WebCrypto requires a secure context (HTTPS or localhost); elsewhere the tool reports the error instead of a digest.
Limits & compatibility
- SHA family only — MD5 is not supported (it is cryptographically broken).
- Hashing is one-way: digests cannot be reversed into the original text.
- WebCrypto requires a secure context (HTTPS or localhost).
Privacy
Digests are computed by your browser's crypto engine. The input text is never sent to a server or stored.
Related tools
Questions about Hash Generator (SHA)
Which hash algorithms are supported?
SHA-1, SHA-256, SHA-384 and SHA-512, computed by your browser's built-in WebCrypto engine. MD5 is deliberately not offered because it is cryptographically broken. The output is a lowercase hexadecimal digest of the UTF-8 encoding of your text — hashing "hello" with SHA-256 gives 2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824, so you can verify the tool against any other implementation.
Can a hash be turned back into the original text?
No — hashing is one-way by design. A digest is a fixed-length fingerprint of the input, and nothing in it lets you reconstruct the text. That is the point: you hash a file or password check-value and compare digests to confirm two inputs match, without ever storing the input itself.
Why does the tool need HTTPS?
WebCrypto, the browser API that computes the digests, only exists in a secure context — a page served over HTTPS or localhost. On an insecure origin the browser withholds the crypto engine and hashing cannot run. There is a privacy benefit too: the digest is computed on your device, and the input text is never sent to a server.
Can I hash a file with it?
No — the tool hashes pasted text only; there is no file input. A file checksum needs the raw bytes, so use a purpose-built checksum tool for that. For text — API tokens, config values, message strings — paste it, pick the algorithm and copy the lowercase hex digest.