CRC-32, MD5, SHA-1, SHA-256/384/512 and HMAC of text or a file —
computed with your browser's own crypto, so the passwords, tokens, and
documents people habitually paste into "online hash generators" never
leave this page.
Text is hashed as UTF-8.
Try:
Digests click a value to copy
Compare against an expected checksum
HMAC (keyed hash)
With a key, the table above shows HMAC-MD5 / HMAC-SHA-* of the same message instead (CRC-32 has no HMAC).
MD5 and SHA-1 are fine as integrity checksums against accidental
corruption, but both are cryptographically broken: collisions can be
manufactured, so don't use them for signatures or fingerprinting
attacker-supplied data. CRC-32 is only an error-detection code — it is
trivially forgeable and not a cryptographic hash at all. Files are
hashed in memory in your browser; very large files (hundreds of MB) may
be slow or fail, but they still never leave your machine.