Verify a downloaded file with its checksum

The download page says CRC-32 is 3f8a2c1e. Instead of trusting it, compute the checksum yourself and compare.

Tools used in this guide

The job

Older archives, ROM sets and firmware lists still publish CRC-32 or CRC-16 rather than SHA-256. The check is the same: compute the value locally, compare it with the published one. Mismatch = corrupted download or wrong file.

File or text

Drop a file for a report covering CRC-32, CRC-16-CCITT and Adler-32 at once — different vendors publish different ones. For published text values (ROM filenames often carry the CRC), paste the text and get the checksum of its bytes.

File inputs read up to 256 MiB locally — nothing is hashed on a server.
Text mode caps at 2,000,000 characters; it's for values and short payloads, not whole files.

Comparing

Checksums are case-insensitive hex — compare the digits, ignore case. A match proves the bytes are identical; CRCs aren't collision-resistant, so 'matches the published CRC' is an integrity check, not an authenticity one.