Use the free CRC32 Hash Generator below: your data never leaves your browser — all work happens on your device, and nothing is uploaded to any server.
A checksum is a short number computed from a file or a piece of text, used to answer one question: did this data arrive unchanged? If the checksum matches, the data almost certainly matches too. CRC32 is one of the oldest and most widely used checksums. It appears in ZIP files, in network protocols, and in many download pages that list an expected value beside the file. The CRC32 Hash Generator computes CRC32 for pasted text and, more importantly, for uploaded files, reading the file in your browser with FileReader and checksumming its bytes.
The file mode is what makes this tool different from a text-only checksum calculator. Text checksums are useful, but the real job of a checksum is verifying a file you downloaded or received. Pasting a file’s contents as text would change it: line endings, encodings, and invisible bytes would all shift, and the checksum would no longer match the original file. Reading the file’s raw bytes in the browser avoids that entirely. The file never leaves your device, because FileReader works locally, and nothing is uploaded to any server.
To use the text mode, paste or type text into the box and press CRC32 of text. To use the file mode, choose a file with the file picker and press CRC32 of file. The result shows the file name, its size in bytes, and the checksum twice: once as hexadecimal, such as 0xCBF43926, and once as an unsigned decimal number. Both forms describe the same value, and different tools show different forms, so having both saves a conversion step.
The algorithm uses the standard CRC32 polynomial table, the one built from 0xEDB88320, which is the variant used by ZIP files and most checksum listings. That detail matters, because CRC32 has several variants with different polynomials and starting values, and mixing variants gives different answers for the same data. If a download page lists a CRC32 value, it almost always means this standard variant, and this tool matches it. The well-known check value for the text 123456789 is 0xCBF43926, which is a quick way to confirm any CRC32 tool is using the same variant.
CRC32 has honest limits that users should know. It detects accidental damage very well: a flipped byte, a truncated download, or a corrupted transfer changes the checksum. It does not protect against a deliberate attacker, because CRC32 is not a cryptographic hash. An attacker who changes a file can also recompute its CRC32, so a matching CRC32 proves the file survived transfer, not that it came from a trusted source. For trust, use a cryptographic hash like SHA-256 and a signed source. For transfer damage, CRC32 is fast and sufficient.
Large files work in this tool because FileReader reads the file into memory in the browser. Very large files, several hundred megabytes, may strain a low-memory device, so for huge files a desktop checksum utility is a better choice. For documents, images, archives, and installers of ordinary size, the browser mode is quick and avoids installing anything.
People use this tool to verify a download against the publisher’s listed checksum, to check whether two copies of a file are identical without opening them, and to confirm that a file survived an email or USB transfer. In each case the rule is simple: compute the checksum on both copies and compare. Equal checksums mean the bytes match for all practical purposes. Different checksums mean something changed, and the file should be transferred again.
How to compute a CRC32 checksum
- For text: paste the text and press CRC32 of text.
- For a file: choose the file and press CRC32 of file.
- Read the hex and decimal forms of the result.
- Compare against the expected value from the source.
- If they differ, download or transfer the file again.
Frequently asked questions
How is this different from a text-only CRC32 calculator? The file mode checksums the file’s raw bytes in your browser, which pasting file contents as text cannot do accurately.
Why does my checksum differ from the download page? The file may be damaged, or the page may list a different checksum type. Check the label: CRC32, MD5, and SHA-256 are different values.
Does a matching CRC32 prove a file is safe? No. It proves the file survived transfer unchanged, not that it came from a trusted source.
Is my file uploaded? No. FileReader reads it locally in your browser, and nothing is sent or stored.
Verify the file before you trust it. A checksum takes seconds, and it is the cheapest insurance against a damaged download.