Hash Generator

Not for anything security-related. Both are broken against collision attacks, two different inputs can be constructed to share a digest, demonstrated for MD5 in 2004 and for SHA-1 in 2017, so neither belongs near a signature, a certificate or stored passwords. They remain useful as plain checksums, where nobody is trying to fool you: spotting a download that arrived corrupted, or matching a file against a hash published years ago. That is the only reason they are offered here. Where an attacker could influence the input, use SHA-256 or better.

Web Crypto deliberately omits it, so MD5 is implemented on this page from RFC 1321. It runs on the main thread, which is why file mode feeds it 4 MB at a time with a progress percentage, while the four SHA digests come straight from crypto.subtle.

The whole file is read into memory at once, and the browser gives up somewhere above 1.5 GB.

Almost always the bytes differ, not the algorithm. A file usually ends with a newline you do not reproduce when pasting its contents, a Windows editor may have saved CRLF where the original had LF, and a copied string can pick up a trailing space. Run file mode on the actual file and the digests match exactly.