CRC32 Checksum Calculator

Calculate the CRC32 checksum of any text in hex, decimal and binary

What is it and how does it work?

A checksum is a small fixed-size value computed from a block of data, used to detect errors or verify data integrity. When you download a file and the website provides a checksum (like "SHA-256: a3f4b2..."), you can run the same computation on the downloaded file and compare — if they match, the file is intact; if they differ, the file was corrupted or tampered with. Common checksums: MD5 (128-bit, fast but cryptographically broken), SHA-1 (160-bit, deprecated for security), SHA-256 (256-bit, current standard), SHA-512 (512-bit, higher security), CRC32 (32-bit, fast, used in zip/ethernet/PNG).

This tool computes checksums for text input or file content using multiple algorithms simultaneously, so you can compare against a provided checksum or generate one to distribute with your own files. It distinguishes between cryptographic hash functions (SHA-256, SHA-512, Blake2) designed to detect intentional tampering, and non-cryptographic checksums (CRC32, Adler-32) designed only for accidental corruption detection.

Common use cases

Frequently asked questions

What is the difference between a checksum and a hash?

The terms are often used interchangeably, but strictly: a checksum is any value computed from data to detect errors (includes non-cryptographic: CRC32, Adler-32). A hash or hash function specifically means a deterministic function that maps arbitrary data to a fixed-size output. A cryptographic hash function additionally guarantees: (1) preimage resistance (can't reverse the hash to get input), (2) second preimage resistance (can't find a different input with the same hash), (3) collision resistance (computationally infeasible to find any two inputs with the same hash).

Is MD5 safe to use for file integrity checking?

For detecting accidental corruption (download errors, disk failures), MD5 is fine — it's fast and sufficient. For security purposes (detecting intentional tampering), MD5 is broken: known collision attacks can produce two different files with the same MD5. Use SHA-256 or SHA-3 for security-sensitive integrity checking. Many projects still publish MD5 checksums alongside SHA-256 for legacy compatibility — always prefer the stronger hash.

What is CRC32 and when should I use it?

CRC32 (Cyclic Redundancy Check, 32-bit) is a non-cryptographic error detection code. It's used where speed matters and adversarial inputs aren't a concern: ZIP file integrity, Ethernet frame verification, PNG image chunk validation, POSIX cksum. CRC32 is NOT a secure hash — it's trivial to construct a file with a target CRC32 value. Use CRC32 for error detection in transmission/storage; use SHA-256 for security-sensitive checks.

What is HMAC and how is it different from a plain hash?

HMAC (Hash-based Message Authentication Code) combines a secret key with the message before hashing: HMAC-SHA256(key, message) = SHA256(key ⊕ opad || SHA256(key ⊕ ipad || message)). A plain hash has no key — anyone can compute SHA256("hello"). HMAC requires knowing the secret key to produce the correct MAC, providing authentication (the message came from someone knowing the key) in addition to integrity (the message wasn't modified). Used in JWT signatures, API authentication, webhook verification.

Security

Password Strength Checker · ROT13 Cipher · Base32 Encoder / Decoder · Hex Encoder / Decoder · Caesar Cipher · Vigenère Cipher