A little help goes a long way. Find a tool/

Security

Checksum Calculator

Free checksum calculator: compute the CRC-32, Adler-32 and FNV-1a (32-bit) checksum of any text, shown in hex and decimal. Runs entirely in your browser.

YOUR WORKSPACEFree to use. No sign-up.
—
Enter text above, then press Calculate checksums.

Deep dive guides

A LITTLE CONTEXT · 5 MIN READChecksums vs Hashes: What's the Difference?

How checksum calculator works

A checksum is a short fingerprint computed from data so that accidental changes are detectable. Unlike cryptographic hashes such as SHA-256, classic checksums are designed to be fast and simple rather than tamper-proof — they catch corruption, not attackers. This tool computes three of the most widely used 32-bit checksums: CRC-32 (the cyclic redundancy check used by zip, gzip and PNG), Adler-32 (the rolling checksum inside zlib) and FNV-1a (the Fowler–Noll–Vo hash popular for hash tables and quick fingerprinting).

Each algorithm processes the UTF-8 bytes of your text directly: CRC-32 runs the bytes through a precomputed 256-entry polynomial table (the reflected 0xEDB88320 polynomial used by IEEE 802.3, so it matches the check value CBF43926 for the standard test string "123456789"); Adler-32 maintains two 16-bit running sums modulo 65,521; and FNV-1a XORs each byte into a running value before multiplying by the FNV prime. Every result is shown both as an 8-digit hexadecimal value and as a decimal number, because different tools and file-format specifications display checksums differently.

Use checksums to verify that a download, a serialized file or a network payload survived the trip intact: compute the checksum of the original and the copy and compare them. They are also handy for spotting duplicate content and teaching checksum arithmetic. Remember their limits — CRC-32 and Adler-32 will deliberately collide under adversarial modification, so for security-sensitive verification use the site's hash generator with SHA-256 or stronger instead.

Frequently asked questions

What is the difference between a checksum and a hash?
Both condense data to a fixed-size value, but they optimize for different goals. Checksums like CRC-32 and Adler-32 are built for speed and for detecting accidental corruption — bit flips from a bad transfer or disk. Cryptographic hashes like SHA-256 are built so that no one can craft different data with the same digest. Use checksums for integrity, cryptographic hashes for security.
Which checksum does my zip file use?
ZIP files store a CRC-32 (IEEE 802.3, reflected) value for every entry, and gzip and PNG use CRC-32 for whole payloads, so this tool's CRC-32 matches what those formats record. zlib streams carry an Adler-32 of their uncompressed data. If you text-encode the same bytes this tool sees, the values line up.
Why do hex and decimal values differ in length?
They do not — all three checksums are 32 bits. The hex form always shows 8 hexadecimal digits (32 bits ÷ 4 bits per digit), while the decimal form varies between 1 and 10 digits depending on the value. Both represent exactly the same number, so 0CBF43926-style leading zeros in decimal are simply not shown.
Can a checksum verify authenticity, not just integrity?
No. Because CRC-32 and Adler-32 are linear and fast, an attacker can modify data and recompute a matching checksum trivially. They prove data was not corrupted by accident, not that nobody tampered with it. For authenticity, use an HMAC or a cryptographic hash comparison — the site's HMAC generator covers keyed verification.
Does text length change the checksum values?
Yes. Checksums depend on every input byte, so a one-character edit almost always changes all three values. Note that multi-byte characters (é, emoji) contribute several UTF-8 bytes each — the tool reports both the character count and the exact byte count it checksummed, so results match byte-oriented tools.