CRC-32 Calculator

Calculate CRC-32/ISO-HDLC checksums for UTF-8 text or local files up to 10 MiB, with hexadecimal and unsigned decimal output.

CRC-32/ISO-HDLC only. Text uses UTF-8; empty text is valid. Files stay local (maximum 10 MiB). Checksums detect changes, not authenticity.

Calculate the common reflected CRC-32 variant

This calculator implements CRC-32/ISO-HDLC, also commonly called IEEE CRC-32. It does not offer CRC-32C, CRC-16 or every variant that contains CRC in its name. Confirm the full variant used by the system you are comparing against before treating a mismatch as a damaged file.

The parameters are width 32, polynomial 0x04C11DB7, initial value 0xFFFFFFFF, reflected input and output, and final XOR 0xFFFFFFFF. The reflected implementation uses 0xEDB88320. The checksum calculation used by gzip is described in RFC 1952. Calculating a checksum of a gzip file here reads the entire compressed file; it does not extract or verify its internal uncompressed-data trailer.

Reproduce the supplied example

Load example (switches to text) inserts 123456789, with no newline. Choose Calculate checksum. The result is CBF43926 in hexadecimal and 3421780262 in unsigned decimal for nine input bytes. Adding a space or newline changes the bytes and normally changes the checksum. For an empty input, the expected hexadecimal result is 00000000.

Choose text or exact file bytes

Text mode encodes the textarea contents as UTF-8 without adding a BOM or normalizing Unicode. An existing U+FEFF character contributes its UTF-8 bytes. Browser textareas may normalize pasted CRLF or CR line endings to LF, so use file mode when original line endings matter. Unpaired surrogate code units are rejected instead of silently replaced.

Enable Use local file bytes, choose a file and calculate. The file is read locally as raw bytes, including any BOM, binary values and original line endings. Its filename and extension do not affect the result. Empty files are valid. Switching modes or editing input clears old output; a completed read from an earlier selection cannot replace a newer result.

Limits and exported results

Text is limited to 200,000 UTF-16 code units. Files are limited to 10 MiB, exactly 10,485,760 bytes, before reading. This browser implementation reads the complete bounded file into memory; it is not a streaming checksum service for large archives.

The visible result shows the algorithm, byte count, eight uppercase hexadecimal digits and an unsigned decimal integer. Copy hexadecimal copies only the eight digits. Download JSON exports all four fields without an added newline. The hexadecimal display is a numeric representation, not a statement about byte order in a binary file format.

What a matching checksum means

A checksum can help detect accidental changes, but different inputs can share the same 32-bit result. A match does not prove authenticity or protect against deliberate modification. Compare values produced with the same algorithm and identical input bytes. For signed software downloads, follow the publisher's signature-verification process instead of substituting this calculator.

Use UTF-8 Byte Inspector to understand text byte differences, or Adler-32 Calculator when your expected checksum uses that other algorithm.