Type text (sent as UTF-8 bytes) or a run of hexadecimal bytes. See the CRC-32 used by Ethernet, ZIP and gzip, and the 16-bit Internet checksum used by IPv4, TCP and UDP headers.
Checksums catch accidental changes, not deliberate ones: they are not a security hash. The text you type stays in your browser and is never put in a shared link.
- CRC-32 (hexadecimal)
- –
- CRC-32 (decimal)
- –
- Internet checksum (hexadecimal)
- –
- One's complement sum before inverting (hexadecimal)
- –
- Number of bytes
- –
Assumptions
- Text is turned into bytes with UTF-8, so a letter outside English can take 2 to 4 bytes.
- CRC-32 is the reflected 04C11DB7 polynomial, start value FFFFFFFF and final XOR FFFFFFFF, as in RFC 1952 and zlib.
- Internet checksum: bytes are paired big-endian, an odd last byte is padded with a zero byte (RFC 1071).
Checked 3 November 2026 RFC 1952, GZIP file format: CRC-32 definition and sample code (§2.3.1, §8) All sources
How it is calculated
- CRC-32: c = FFFFFFFF; for each byte b: c = T[(c XOR b) AND FF] XOR (c >> 8); result = c XOR FFFFFFFF
- Table T[n]: start with n, 8 times: c = (c AND 1) ? EDB88320 XOR (c >> 1) : c >> 1
- Internet checksum: sum the 16-bit words [A,B] = A × 256 + B with end-around carry; checksum = NOT sum (16 bits)
Worked example
The nine ASCII digits 1 to 9, the standard check string for CRC algorithms.
| You enter | |
|---|---|
| Data | 123,456,789 |
| Read the data as | Text (UTF-8 bytes) |
| You get | |
| CRC-32 (hexadecimal) | CBF43926 |
| CRC-32 (decimal) | 3,421,780,262 |
| Internet checksum (hexadecimal) | F62A |
| One's complement sum before inverting (hexadecimal) | 09D5 |
| Number of bytes | 9 |
Over 9 bytes the CRC-32 is CBF43926. The 16-bit one's complement sum is 09D5, so the Internet checksum, its complement, is F62A.
Questions
Why does my tool show a different CRC-32?
There are many 32-bit CRCs. This is the one in gzip (RFC 1952), PKZip and Ethernet. Others use a different polynomial, start value or final XOR, and give different values; check that your tool reports CBF43926 for 123456789.
How do I check a received packet with the Internet checksum?
Run the sum over the bytes including the checksum field. RFC 1071 says the check succeeds when the result is all 1 bits, so the Internet checksum shown here is 0000.
Sources and checks
- RFC 1952, GZIP file format: CRC-32 definition and sample code (§2.3.1, §8)
- RFC 1071, Computing the Internet Checksum (its §3 example is a test here)
- Ross Williams, A Painless Guide to CRC Error Detection Algorithms (1993), RFC 1952 reference [8]: CRC-32 parameters and check value CBF43926
Last checked: 3 November 2026. This tool passes 8 automatic tests before every release. How we check our tools
Cite this page
CRC-32 and Internet Checksum Calculator. GlanceDesk Compute. Last checked 3 November 2026. https://glancedeskcompute.com/
Your numbers stay on your device unless you share them.
For learning and checking data by hand. A checksum is not a cryptographic hash and does not prove a file has not been tampered with. Results are estimates for planning and learning. They are not a design check and do not replace a qualified engineer or your local building/electrical code.