File Checksum

Key features

• Computes CRC32 plus SHA-1, SHA-256 and SHA-512 for any file — all four in a single read of the bytes.
• CRC32 (the standard IEEE 0xEDB88320 polynomial) is implemented in pure JavaScript; SHA digests use the native Web Crypto API.
• Accepts every file type up to 200 MB — the limit exists because hashing needs the whole file in memory.
• Algorithm chips toggle which digest rows are displayed (computation itself always runs once).
• Paste an expected hash and the tool compares it live, case-insensitively and whitespace-tolerant, telling you which algorithm matched.
• Magic-byte sniffing identifies the real file type — PNG, JPEG, GIF, BMP, PDF, ZIP, GZIP, 7Z, RIFF, MP3, MP4, ELF, text or binary — plus hash time and file size stats.

How it works

1. 1

   Drop in any file

   Drag a file onto the dropzone (or browse). Files over 200 MB are rejected up front with a clear message.

2. 2

   Let it hash once

   The file's bytes are read a single time; CRC32 and all three SHA digests are computed in parallel while a timer measures the duration.

3. 3

   Compare with the expected hash

   Paste the checksum from the download page into the compare field. A green Match badge names the algorithm that agrees; otherwise you'll see No match.

4. 4

   Format and copy the digest

   Switch hex output between lower and UPPER to match your target system, then copy any digest row you need.

Tips for better results

• 💡Use whichever algorithm the publisher provides — SHA-256 is the most common; CRC32 alone detects accidental corruption, not tampering.
• 💡'No match' usually means a wrong algorithm, a truncated download, or a corrupted file — first check you pasted the full digest for the right algorithm.
• 💡The comparison ignores case and whitespace, so digests wrapped across lines in a checksums.txt still match.
• 💡The detected file type comes from magic bytes, not the extension — a mislabeled .exe.txt will reveal itself.

Frequently asked questions