CRC32 Checksum
Compute IEEE 802.3 CRC32 of text (UTF-8) or any file. Matches ZIP archives, PNG IDATs, zlib.crc32, and cksum -a crc. Runs in your browser.
0 characters · 0 bytes (UTF-8)
How to compute a CRC32 online
Switch to Text and type/paste content — the CRC32 updates as you type. Or switch to File and drop any file; ToolChop reads it as raw bytes and computes the IEEE 802.3 CRC32 using a 256-entry lookup table (the standard table-driven algorithm). The hex result is always 8 characters, zero-padded, for easy visual comparison against published checksums.
Why a local checksum matters
The files you typically checksum are firmware blobs, release archives, enterprise installers, internal release artifacts — material that should not casually travel to third-party servers. ToolChop runs the algorithm in your browser. DevTools → Network confirms no request fires.
CRC32 vs MD5/SHA — when each fits
CRC32 is an error detection code, not a cryptographic hash. It is extremely fast and great for catching accidental corruption (network transmission errors, disk bit-flips), which is why it is built into ZIP, PNG, and Ethernet. But it is trivial to forge — anyone can construct two files with the same CRC32. For integrity against any adversary (package signing, code verification), use SHA-256 from our Hash Generator.
What you can do
- CRC32 of UTF-8 text or any arbitrary file
- Matches
zlib.crc32, ZIP archive CRCs, PNG IDAT CRCs,cksum -a crc - Hex output zero-padded to 8 characters for easy comparison
- Decimal output for tools that expect a plain integer
- One-click copy
Frequently asked questions
How do I compute a CRC32 checksum online for free?
Switch to the Text tab and type/paste content, or switch to File and drop any file. ToolChop computes the IEEE 802.3 CRC32 instantly and shows it in hex and decimal. Click Copy. No account, no upload, no daily limit.
Does ToolChop send my data to a server?
No. The CRC32 computation runs entirely in your browser using a pure-JS implementation. Your text or file never leaves your device — useful when verifying downloads, comparing firmware blobs, or checksum-ing internal release artifacts.
Why is the privacy story for a checksum tool important?
Checksums are most often used to verify integrity of files: enterprise installers, firmware updates, downloaded release archives, customer-supplied attachments. The files you checksum are often proprietary or pre-release. Uploading them to a third-party CRC32 calculator is a needless leak. ToolChop runs the algorithm in your browser.
What variant of CRC32 does ToolChop compute?
IEEE 802.3 with reversed polynomial 0xEDB88320 — the most common variant. This is what ZIP archives store, what PNG IDAT chunks include, what Ethernet frames use, and what Python's binascii.crc32 / zlib.crc32 / Perl's String::CRC32 / GNU cksum (default) all produce. Standard CRC32 in every practical context.
Will the output match my ZIP file's CRC, GNU cksum, or zlib.crc32?
Yes — byte-for-byte identical. ZIP archive entry CRCs, the value Python's zlib.crc32(data) returns, and the result of crc32 (the command) on the same bytes will all match what ToolChop shows.
What is the difference between CRC32 and MD5/SHA?
CRC32 is a 32-bit error-detection checksum, not a cryptographic hash. It is fast and great for catching accidental corruption (network transmission errors, disk bit-flips) but trivial to forge — anyone can construct two files with the same CRC32. For integrity against an adversary, use SHA-256 from our Hash Generator instead.
When should I use CRC32 vs SHA-256?
Use CRC32 when speed matters and the threat is accidental corruption — verifying a download against the publisher's stated checksum, comparing two file copies for bit-identical equality, building a content-addressing cache where the keys are not adversary-controlled. Use SHA-256 when there is any adversary in the threat model — code signing, package verification, signature checks.
Is the output a 'cksum' value?
Close but not identical. GNU cksum has multiple algorithms — its default (-a sysv) is a different checksum, but its -a crc (CRC32) flag produces the same value ToolChop shows. So `cksum -a crc file` matches.
Is there a file size limit?
Only your browser's memory. ToolChop comfortably checksums hundreds of MB. The CRC32 algorithm itself is O(n) over the bytes — very fast — most of the time on a large file is the read step.
What encoding does the text mode use?
UTF-8 — the universal default. So 'café' is the 5 bytes 0x63 0x61 0x66 0xC3 0xA9. If you are comparing against a CRC32 computed with a different encoding (UTF-16, Latin-1), the result will differ. Make sure both sides use UTF-8.
Why is the hex always 8 characters?
CRC32 is a 32-bit value — 8 hex digits exactly. ToolChop zero-pads the result so a value like 0x12 always displays as 00000012 for consistent visual matching against published checksums.
Why use ToolChop instead of an online CRC32 tool that uploads my file?
Privacy. The files you typically need to checksum are firmware blobs, release archives, internal installers — material that should not casually travel to third-party servers. ToolChop runs the algorithm in your browser. DevTools → Network confirms no request fires.