CRC32 Calculator

About CRC32 Calculator

This CRC32 calculator computes the 32-bit Cyclic Redundancy Check checksum of any text input. CRC32 is widely used for detecting accidental data corruption in file transfers, archive verification, and network communications.

The calculation uses the standard CRC-32 polynomial (0xEDB88320) compatible with ZIP, PNG, GZIP, Ethernet, and many other formats.

How CRC32 Works

The CRC32 algorithm processes input data byte by byte:

1. Initialize: Start with CRC = 0xFFFFFFFF (all bits set)
2. Process each byte: XOR the byte with the lowest byte of CRC
3. Table lookup: Use the result as index into a precomputed 256-entry table
4. Update CRC: Shift CRC right 8 bits, XOR with table value
5. Finalize: XOR final CRC with 0xFFFFFFFF to get result

CRC32 Algorithm Implementation

// Generate CRC32 lookup table
function makeCRCTable() {
  const table = [];
  for (let n = 0; n < 256; n++) {
    let c = n;
    for (let k = 0; k < 8; k++) {
      c = (c & 1) ? (0xEDB88320 ^ (c >>> 1)) : (c >>> 1);
    }
    table[n] = c;
  }
  return table;
}

// Calculate CRC32 checksum
function crc32(data) {
  const table = makeCRCTable();
  const bytes = new TextEncoder().encode(data);
  let crc = 0 ^ (-1);

  for (let i = 0; i < bytes.length; i++) {
    crc = (crc >>> 8) ^ table[(crc ^ bytes[i]) & 0xFF];
  }

  return (crc ^ (-1)) >>> 0;
}

// Output as hexadecimal
const checksum = crc32("Hello World").toString(16);
// Output: "559d8f05"

CRC32 Use Cases

CRC32 Checksum Examples

Input: "" (empty string)
CRC32: 00000000

Input: "Hello World"
CRC32: 559d8f05

Input: "The quick brown fox jumps over the lazy dog"
CRC32: 414fa339

Input: "ABCDEFGHIJKLMNOPQRSTUVWXYZ"
CRC32: 360794d8

Input: "123456789"
CRC32: cbf43926  (standard test vector)

CRC32 vs Other Checksums

Understanding CRC32 Output

• Format: 8 hexadecimal characters (0-9, a-f)
• Range: 00000000 to FFFFFFFF (0 to 4,294,967,295)
• Case: Typically lowercase, but case-insensitive for comparison
• Uniqueness: 2^32 possible values; collisions possible but unlikely for accidental changes

Limitations of CRC32

• Not cryptographically secure: Intentional collisions can be created
• Limited space: Only 32 bits means ~1 in 4 billion collision chance for random data
• Not reversible: Cannot recover original data from CRC32 alone
• No authentication: Does not verify data source, only integrity

Common Applications

• File Transfer Verification: Confirm downloaded files match source
• Archive Integrity: Verify ZIP/PNG/GZIP files haven't been corrupted
• Database Page Checks: Detect storage corruption in database pages
• Network Packet Validation: Ensure Ethernet frames arrived intact
• Backup Deduplication: Quick comparison to detect changed files
• Embedded Systems: Firmware image verification before flashing