Type or paste a string and get all five digests at once: MD5, SHA-1, SHA-256, SHA-384 and SHA-512. Add a key and the same rows become HMAC, which is what you need when debugging a webhook signature or an API that signs its requests. Paste a digest you were given into the compare field and the matching row is highlighted — and the field is forgiving about format on purpose, so a line copied straight out of sha256sum with its trailing filename, or a registry digest with its sha256: prefix, works without editing. Files can be dropped in too, including whole folders. If verifying downloads is the main thing you came for, the File Checksum Generator is built around that job. Everything here runs in your browser; no string and no file is uploaded.
| Algorithm | Length | Use it for |
|---|---|---|
| MD5 | 128-bit | Legacy checksums only — broken since 2004 |
| SHA-1 | 160-bit | Legacy only — collisions demonstrated in 2017 |
| SHA-256 | 256-bit | The default for everything |
| SHA-384 | 384-bit | Where a standard specifies it |
| SHA-512 | 512-bit | Longer digest, often fast on 64-bit CPUs |
No. Hashing happens inside your browser and nothing is transmitted, which is why this is safe to use on a real signing key or a private file.
Only for spotting accidental corruption, like a bad download. Practical MD5 collisions have existed since 2004 and SHA-1 collisions since 2017, which means someone can craft two different inputs with the same digest. Neither proves anything was not tampered with. Use SHA-256 for anything that matters.
HMAC mixes a secret key into the hash, so only someone holding the key can produce or verify the result. A plain hash proves nothing about who computed it, because anyone can hash the same input. Webhooks and signed API requests use HMAC for exactly that reason — enter the shared secret as the key and you can reproduce the signature the sender computed.
The browser's crypto does not offer it, and building it by hand around our own MD5 implementation for an algorithm nobody should be choosing is not worth the risk of getting it subtly wrong. The SHA options are all available.
Almost always a trailing newline. echo adds one, so echo hello | sha256sum hashes six bytes, not five. Use echo -n, or hash a file instead. Encoding is the other cause — text here is UTF-8, the same as command-line tools.
Your available memory, because the browser's digest function needs the whole file at once and cannot be streamed. A few hundred megabytes is fine; a multi-gigabyte image is better handled by a desktop tool.
SHA-1, SHA-256, SHA-384 and SHA-512 come from the Web Crypto API built into your browser, which means they run as native code rather than JavaScript and are as fast as hashing gets in a page. MD5 is not in Web Crypto at all, and that omission is deliberate rather than an oversight: MD5 collisions have been practical since 2004, and the platform will not lend its name to it. Because MD5 is still what checksum files on download pages are written in, it is implemented here directly from RFC 1321 and verified against all seven test vectors in the specification. HMAC uses importKey and sign from the same Web Crypto, and is verified against the RFC 4231 vectors; HMAC-MD5 is refused rather than faked, because the browser does not offer it and hand-rolling the ipad/opad construction around our own MD5 for an algorithm nobody should pick is not a trade worth making. Text is hashed as UTF-8, which is what every command-line tool does, so a digest computed here matches sha256sum on the same string; if you get a different answer somewhere else, the usual cause is a trailing newline that echo adds and this does not. The compare field is deliberately forgiving about format, because otherwise every real-world paste reports a mismatch: case is ignored, surrounding whitespace is trimmed, a sha256: style prefix is stripped, and the trailing filename in sha256sum output is dropped. Files are hashed by reading each one into memory once and feeding the same bytes to every algorithm, so a large file is read from disk once rather than five times — though it does have to fit in memory, since digest() takes a complete buffer and cannot be streamed. Nothing is uploaded.