Hash & Checksum Generator

No. Hashing runs entirely in your browser via the Web Crypto API (and a small local MD5/CRC32 implementation for the legacy group). Nothing is sent to a server, added to the URL, or saved to local storage.

For anything security-relevant — verifying software downloads, integrity of signed data, or anything where an attacker might try to forge a match — use SHA-256, SHA-384, or SHA-512. MD5, SHA-1, and CRC32 are only here for compatibility with older systems that still produce those checksums; none of them should be treated as secure.

No. The Web Crypto API's SubtleCrypto.digest() only implements SHA-1/256/384/512. MD5 output on this page comes from a small pure-JavaScript implementation, included purely for comparing against legacy MD5 checksums.

CRC32 is designed to catch accidental corruption (e.g. a bit flip during a file transfer) cheaply — it is not designed to resist an attacker deliberately crafting a colliding input, unlike SHA-256/384/512.

This tool reads the entire file into memory before hashing, so very large files aren't practical in a browser tab. Files up to a couple hundred MB generally work fine; beyond that, expect slowdowns or the tab to run out of memory.