Generate the MD5, SHA-1, SHA-256, or SHA-512 checksum of any file and verify a download's integrity in seconds. The calculator is free and runs entirely in your browser — the file is hashed on your own device and never uploaded, so you can safely checksum installers, backups, and private documents of any size. A checksum is a fingerprint: if your computed hash matches the value published by a download page, the file arrived intact and unmodified; if it differs by even one character, the file is corrupt or has been tampered with. Compute the hash, paste the expected value, and the tool compares them for you. The table below shows what each algorithm is for today.
| Algorithm | Output | Status |
|---|---|---|
| MD5 | 128-bit (32 hex chars) | Broken for security; fine for accidental-corruption checks |
| SHA-1 | 160-bit (40 hex chars) | Deprecated; legacy compatibility only |
| SHA-256 | 256-bit (64 hex chars) | Current standard for integrity verification |
| SHA-512 | 512-bit (128 hex chars) | Stronger variant, faster on some 64-bit CPUs |
The tool supports MD5, SHA-1, SHA-256, and SHA-512. SHA-256 is the most commonly used for verifying file integrity.
Paste the expected checksum in the verification field. The tool will compare it against the computed hash and show you if they match.
All processing happens entirely in your browser using the Web Crypto API. Your files are never uploaded to any server.
A checksum is a fixed-size string computed from file data. Even a tiny change in the file produces a completely different checksum, making it useful for verifying file integrity.
Checksum generation uses the Web Crypto API's SubtleCrypto.digest() method to compute cryptographic hash functions over file contents. Supported algorithms include MD5 (128-bit, considered weak but fast for non-security purposes), SHA-1 (160-bit, deprecated for security), SHA-256 (256-bit, current standard), and SHA-512 (512-bit, maximum security). Large files are processed incrementally using FileReader in chunks (typically 64KB) to avoid memory overflow, with each chunk fed to an incremental hash state. The resulting hash bytes are converted to hexadecimal strings using byte-to-hex mapping, and the tool displays checksums in uppercase hex format. Verification mode allows pasting expected checksums for comparison, with instant match/mismatch feedback to detect file corruption or tampering.