CRC32 Checksum Calculator
Compute the CRC32 checksum of text or a small file, for integrity/error-detection checks.
How this tool works
Choose text or file
Type text directly, or upload a file up to 5 MB.
The checksum computes automatically
Using the standard CRC-32/ISO-HDLC table-driven algorithm.
Read the 8-digit hex result
The same format CRC32 values are conventionally displayed in.
Compare against a known value
Match it against a checksum provided alongside a download or archive.
Quick facts
- Category
- Encoders & Decoders
- Best for
- Verifying a file transfer or archive extraction completed without accidental corruption
About this tool
Compute the CRC32 checksum of typed text or an uploaded file (up to 5 MB) using the standard CRC-32/ISO-HDLC algorithm - the same polynomial (0xEDB88320, reflected) and table-driven implementation used by zlib, gzip, and the PNG file format's own chunk checksums. This is a meaningfully different tool from hash-generator: MD5 and the SHA family are cryptographic hash functions designed to resist deliberate tampering, while CRC32 is explicitly not cryptographically secure - it's fast and effective at catching accidental corruption (a flipped bit from a bad disk sector, a truncated file transfer, a transmission error), but a motivated attacker can construct a different file with the same CRC32 value without much difficulty. That distinction matters because CRC32 and cryptographic hashes solve different problems and aren't interchangeable: use CRC32 to verify a download wasn't accidentally corrupted, and MD5/SHA (or better, a keyed signature) if you need to detect intentional tampering. Useful for verifying archive integrity, checking a file transfer completed cleanly, or matching a checksum embedded in a file format that uses CRC32 internally. Runs entirely client-side.
Why use this tool
Distinct from cryptographic hashing
CRC32 is for catching accidental corruption, not for security - clearly scoped apart from hash-generator.
Standard, widely-compatible algorithm
Uses the same CRC-32/ISO-HDLC variant as zlib, gzip, and PNG - matches checksums from those tools.
Works on text or files
Check a pasted string or an uploaded file up to 5 MB from the same tool.
Fast, lightweight computation
A table-driven implementation processes even larger inputs quickly in the browser.
Frequently asked questions
CRC32 is designed purely for error detection - catching accidental data corruption like a bad disk sector or a dropped network packet - and is fast and simple, but it's not cryptographically secure: an attacker can deliberately construct different data with the same CRC32 value without much effort. MD5 and SHA-256 (see hash-generator) are built to resist deliberate tampering, at the cost of being more computationally expensive. Use CRC32 for "did this get corrupted by accident," and a cryptographic hash for "can I trust this wasn't deliberately altered."
CRC-32/ISO-HDLC, the most common variant - the same one used by zlib, gzip, PKZIP, and the PNG file format's internal chunk checksums. It uses the reflected polynomial 0xEDB88320, an initial value of 0xFFFFFFFF, and a final XOR of 0xFFFFFFFF. Other CRC32 variants exist with different initial values or polynomials and will produce different results for the same input, so if you're comparing against a checksum from another source, confirm it uses this same standard variant.
For genuinely accidental corruption, a CRC32 mismatch reliably catches the vast majority of real-world errors like bit flips or truncation, which is exactly what it's designed for. However, CRC32 only has 32 bits of output (about 4.3 billion possible values), so accidental collisions become non-negligible at large enough data volumes, and deliberate collisions are straightforward to construct - which is why it's unsuitable whenever the concern is intentional tampering rather than accidental corruption.
Explore more free tools
Formatters, converters, validators, and generators - all free and running entirely in your browser.
Browse more tools