What is a CRC32 checksum actually used for?

CRC-32 is an error-detection code that catches accidental corruption. ZIP and gzip archives store a CRC-32 per entry so the decompressor can confirm the bytes came out intact; PNG puts one after every chunk; Ethernet frames carry a CRC-32 trailer so a NIC can drop a packet that picked up noise on the wire. The idea is cheap to compute and very likely to differ if even one bit flips, so a mismatch flags a damaged download or a bad block before you trust it.

Is CRC32 a cryptographic hash like MD5 or SHA-256?

No. CRC-32 is a non-cryptographic checksum. It is fast and great at spotting random errors, but it offers zero protection against a deliberate change: given any input, an attacker can easily craft a different input with the same CRC, or append bytes to force any target value. MD5 is broken too, but SHA-256 is the right tool when you need to prove a file was not tampered with. Treat CRC-32 as a smoke detector, not a lock.

Why does "123456789" give 0xCBF43926?

0xCBF43926 is the standard CRC-32 check value, the single constant every correct implementation must produce for the ASCII string 123456789. It pins down all the framing choices at once: reflected input and output, the 0xEDB88320 polynomial, an initial register of 0xFFFFFFFF and a final XOR of 0xFFFFFFFF. If you compute CRC32 of 123456789 and do not get 0xCBF43926, your variant differs somewhere, so this page deliberately shows it for that exact input.

How is CRC32 different from MD5?

Size and purpose. CRC-32 produces 32 bits (8 hex digits) and exists to detect accidental corruption; MD5 produces 128 bits (32 hex digits) and was designed as a cryptographic fingerprint. CRC-32 is faster and its collisions are trivial to construct on purpose. For example crc32("a") is 0xE8B7BE43 while md5("a") is a 32-character string. Use CRC-32 for quick integrity checks on archives and packets, MD5 or SHA for content fingerprinting.

Does CRC32 detect tampering or just transmission errors?

Only accidental errors, not tampering. CRC-32 reliably catches single-bit flips, short bursts and most random multi-bit damage from a noisy channel or a flaky disk. It does nothing against an adversary, because the math is public and reversible enough to forge a matching value for any chosen content. So a CRC match on a download tells you the bytes were not garbled in transit, never that nobody altered them on purpose. For that you need a signature or a cryptographic hash.

What is CRC32C and when should I use it?

CRC32C uses the Castagnoli polynomial (reflected form 0x82F63B78) instead of the IEEE 0xEDB88320. It detects certain burst-error patterns slightly better and, crucially, modern CPUs implement it directly via the SSE4.2 crc32 instruction, so it is very fast in hardware. iSCSI, ext4 metadata and Btrfs use CRC32C. The check value differs from IEEE: crc32c("123456789") is 0xE3069283, not 0xCBF43926. Toggle the CRC32C option here whenever you need to match one of those systems rather than ZIP or gzip.

Verify a download matches the published checksum

A mirror lists a CRC-32 next to a file. Open the same content here, read the 8-digit hex, and compare. If they match, the bytes arrived intact; if not, the download is truncated or corrupted and you fetch it again before trusting it. This is the original job CRC-32 was built for and the fastest way to do it for short text payloads.

Match a ZIP or gzip entry's stored CRC

Every ZIP and gzip entry carries a CRC-32 of its uncompressed bytes. When you are debugging an archive tool or a custom packer, paste the decompressed text here and confirm the value you compute equals the one stored in the header. Because this page uses the exact IEEE framing, a match proves your compressor wrote the field correctly.

Pick a non-cryptographic key for cache or sharding

CRC-32 is a cheap, well-distributed way to turn a string into a 32-bit integer for hash buckets, cache keys or shard selection, where speed matters and an attacker is not in the picture. Compute the unsigned decimal here and feed it straight into a modulo. Just never reach for it where someone could benefit from forging a collision.

Tell IEEE CRC-32 and CRC32C apart while porting code

Two systems both say CRC32 but disagree on the number, because one is IEEE and the other is Castagnoli. Turn on the CRC32C row and you see both at once: if your target system expects 0xE3069283 for 123456789 rather than 0xCBF43926, you know it wants CRC32C and can switch the polynomial in your code with confidence.

CRC32 Checksum Calculator (IEEE, hex + decimal)

Standard CRC-32 (IEEE) of any text in hex and unsigned decimal, with optional CRC32C, computed in your browser

Runs locally
Category Developer & DevOps
Best for Checking file type, size, metadata, and obvious mismatch signals before sharing.

Input text

0 chars · 0 bytes

UPPERCASE hexAlso show CRC32C (Castagnoli)

CRC-32 hex

0x00000000

CRC-32 unsigned decimal

0

Check value: crc32("123456789") = 0xCBF43926

What this tool does

Free CRC32 checksum calculator. Paste any text and instantly get its standard CRC-32 (the IEEE 802.3 variant used by ZIP, gzip, PNG and Ethernet) as an 8-digit hexadecimal value and as an unsigned 32-bit decimal number. The math is the table-driven reflected algorithm with the polynomial 0xEDB88320, init 0xFFFFFFFF and a final XOR of 0xFFFFFFFF, so the canonical check value comes out exactly right: the string "123456789" gives 0xCBF43926. Text is read as its UTF-8 bytes, which means Chinese, emoji and any other Unicode hash the same way a file or a network packet would. Flip a switch to also see CRC32C (the Castagnoli polynomial used by ext4, Btrfs and iSCSI) so you can tell the two apart at a glance. One click copies the value. CRC-32 is an error-detection code for catching accidental corruption, not a security hash, and this page makes that distinction explicit. Everything runs locally in your tab and a shareable URL reproduces the exact input.

Tool details

Input: Text; The page exposes text boxes, numeric controls, file pickers, or structured inputs depending on the tool.
Output: Live result + Copy + Download; The result area focuses on usable output, with copy, download, or preview actions when supported.
Privacy: Browser-side processing; The main tool logic does not call an external API, so inputs normally stay in the current tab.
Save / share: Shareable URL state; Key settings are encoded in the URL so another person can reopen the same setup.
Performance budget: Initial JS <= 9 KB; No WASM budget is declared, keeping the tool quick to open on mobile.
Best fit: Developer & DevOps · Developer; Category and role tags drive related tools, internal links, and quick fit checks.

How to use

1. Input

Paste or drop your content into the tool panel.
2. Process

Click the button. All processing is local in your browser.
3. Copy / Download

Copy the result or download to disk in one click.

How CRC32 Checksum Calculator fits into your work

Use it before upload, handoff, archive, support review, or any moment where a file needs one local check before it leaves your machine.

File jobs

Checking file type, size, metadata, and obvious mismatch signals before sharing.
Preparing mixed folders for upload, archive, intake, or review.
Keeping sensitive files in the browser instead of sending them to an account-based service.

File checks

Do not treat the extension alone as proof of the real file type.
Review metadata before a file goes to customers, vendors, or a public page.
Keep the original file until the copied, converted, or exported result is verified.

Good next steps

These links move the current task into a more complete workflow.

Real-world use cases

Verify a download matches the published checksum
A mirror lists a CRC-32 next to a file. Open the same content here, read the 8-digit hex, and compare. If they match, the bytes arrived intact; if not, the download is truncated or corrupted and you fetch it again before trusting it. This is the original job CRC-32 was built for and the fastest way to do it for short text payloads.
Match a ZIP or gzip entry's stored CRC
Every ZIP and gzip entry carries a CRC-32 of its uncompressed bytes. When you are debugging an archive tool or a custom packer, paste the decompressed text here and confirm the value you compute equals the one stored in the header. Because this page uses the exact IEEE framing, a match proves your compressor wrote the field correctly.
Pick a non-cryptographic key for cache or sharding
CRC-32 is a cheap, well-distributed way to turn a string into a 32-bit integer for hash buckets, cache keys or shard selection, where speed matters and an attacker is not in the picture. Compute the unsigned decimal here and feed it straight into a modulo. Just never reach for it where someone could benefit from forging a collision.
Tell IEEE CRC-32 and CRC32C apart while porting code
Two systems both say CRC32 but disagree on the number, because one is IEEE and the other is Castagnoli. Turn on the CRC32C row and you see both at once: if your target system expects 0xE3069283 for 123456789 rather than 0xCBF43926, you know it wants CRC32C and can switch the polynomial in your code with confidence.

Common pitfalls

Trusting CRC-32 against tampering. It only catches accidental corruption. Anyone can craft a different input with the same CRC, so a match never proves a file was not deliberately altered. Use SHA-256 when you need that guarantee.
Comparing values computed with different framing. CRC-32 has many variants. If your other tool omits the final XOR, starts at 0 instead of 0xFFFFFFFF, or uses the non-reflected polynomial, the numbers will not match even though both are "CRC32". Check that it produces 0xCBF43926 for 123456789 first.
Confusing IEEE CRC-32 with CRC32C. They use different polynomials and give different results. 123456789 is 0xCBF43926 under IEEE but 0xE3069283 under Castagnoli. Make sure you are computing the variant your target system actually uses.

Privacy

The whole computation runs as plain JavaScript in your browser tab. Your input text is read as UTF-8 bytes, run through the CRC table locally, and never sent anywhere. There is no upload and no logging of what you hashed. The one caveat: the shareable URL encodes your input in the query string, so a link pasted into chat records that text in the recipient server's access log. For anything sensitive, copy the result instead of sharing the URL.

FAQ

Tool combos

Folks in your role tend to reach for these alongside this tool.

Developer

Browse all tools for this role

CRC32 Checksum Calculator (IEEE, hex + decimal)

What this tool does

Tool details

How to use

1. Input

2. Process

3. Copy / Download

How CRC32 Checksum Calculator fits into your work

File jobs

File checks

Good next steps

Real-world use cases

Verify a download matches the published checksum

Match a ZIP or gzip entry's stored CRC

Pick a non-cryptographic key for cache or sharding

Tell IEEE CRC-32 and CRC32C apart while porting code

Common pitfalls

Privacy

FAQ

Base64 Encoder & Decoder

JWT Decoder

File Hash Calculator

MD5 / SHA Hash Generator

HMAC Generator

Text to Hex Converter

AI Eval Planner

API Key Generator

ASCII Table Generator

ASCII Table Reference

awk + sed Cheatsheet

AWS CLI Cheatsheet