CRC32 Checksum
Paste text and read the checksum.
About this tool
The polynomial is the common reflected CRC-32.
This detects accidental changes. It is not a cryptographic hash.
How to use it
- Open this page and provide the input it asks for.
- Set the options that are visible, then use Checksum.
- Read the result in the panel. Copy it or download it when a file is offered. The input stays in this browser.
Limitations
- This detects accidental changes. It is not a cryptographic hash.
An 8-digit accidental-change check
The polynomial and the bytes
The page encodes the textarea as UTF-8 and runs CRC-32. The register starts at 0xffffffff. Each byte is folded with the reflected polynomial 0xedb88320, and the final register is inverted and printed as eight lowercase hex digits. The well-known check value for the ASCII digits 123456789 is cbf43926, which is the same function the unit test locks in. The same text always yields the same eight digits. Nothing is keyed, and no salt is mixed in.
CRC-32 is a checksum for accidental damage: a flipped bit, a truncated paste, a bad copy. It is not a cryptographic hash. It is not collision-resistant against someone who is trying. It is not a signature, and it is not encryption. Do not use it for new authentication, password storage, or any decision where an attacker might craft a second text with the same residue. MD5 and SHA-1 are already the wrong tools for those jobs, and CRC-32 is weaker than both. It stays on this page because zip files, PNG chunks, and a lot of older protocols still publish this residue and you may need to match one.
What it will not absorb
The bytes are UTF-8 of the paste. A different newline, a BOM, or a different Unicode form is a different checksum. The file checksum page can run the same CRC on raw file bytes, which matches the case where you hold a file rather than a paste. This page does not offer SHA-256. If you need a fingerprint that is hard to forge, use SHA-256 on the hash page for text or on the file page for a file, and still deliver that fingerprint over a channel you trust. A CRC next to the text it covers does not authenticate the text, because anyone can recompute it.
No failure on ordinary text
Empty input has a defined residue. The function does not throw for normal strings. There is nothing to “decrypt.” If your goal was to reverse a checksum into the original paragraph, that is impossible here and is the wrong shape of problem. If two pastes share a CRC, that is a hint they might match, not a proof, and it is a weak hint once someone might be crafting collisions. For a legacy comparison, compute it and compare the eight digits. For a new integrity design, pick a SHA-2 digest instead.
Privacy
Your input is processed in your browser and is not uploaded to UtilChain. File names, text, and results are not sent to analytics.

