CRC-32
Standard CRC-32 checksum for ZIP files and Ethernet - detects accidental data corruption
Short explanation
CRC-32 is a 32-bit checksum used to detect accidental data corruption in files, archives, network frames, and storage systems. It is not a cryptographic hash.
Example input
archive.zipTypical use
Use CRC-32 when you need compatibility with formats or protocols that store CRC-32 checksums.
When to use it
- ZIP, gzip, PNG, Ethernet, and other formats or protocols that specify CRC-32.
- Detecting accidental corruption in trusted storage or transport paths.
- Quick checksum compatibility with existing tooling.
When not to use it
- Security-sensitive integrity checks where an attacker can modify data.
- Password hashing, signatures, tokens, or authentication.
- Large untrusted datasets where collision resistance matters.
FAQ
Is CRC-32 a hash?
It is a checksum and can be treated as a simple non-cryptographic hash, but it is designed for error detection rather than security.
Can CRC-32 detect all errors?
No checksum detects every possible error. CRC-32 is good at common accidental corruption patterns, not malicious tampering.
Should I use CRC-32 or SHA-256?
Use CRC-32 for protocol compatibility and accidental error detection. Use SHA-256 for cryptographic integrity.
Standard CRC-32 checksum for ZIP files and Ethernet - detects accidental data corruption
Adler-32
Fast Adler-32 checksum used in zlib compression - optimized for speed over accuracy
CRC-16
Cyclic redundancy check (16-bit)
CRC-8
Cyclic redundancy check (8-bit)
CRC-64
Cyclic redundancy check (64-bit)
Internet Checksum
RFC 1071 Internet checksum algorithm
Fletcher-4
Compact Fletcher-4 checksum - position-dependent error detection for small data blocks