security-privacy
Checksum Calculator
Calculate CRC-32, Adler-32, or an 8-bit byte sum from UTF-8 text in your browser, with hex, decimal, and byte-count output.
Tool workspace
The interactive tool requires JavaScript.
Instructions
Choose CRC-32, Adler-32, or 8-bit byte sum, and confirm whether the other system also uses UTF-8 bytes.
Before copying the value, check line endings, spaces, encoding, casing, and whether the source expects file bytes instead of text bytes.
Paste test text, a configuration snippet, or a sample payload and calculate a checksum in the current browser. The tool is useful for checking copy, transfer, and example-value mismatches, but it does not upload input or present checksums as encryption or tamper-proof authentication.
Direct answer
Checksum Calculator computes CRC-32, Adler-32, or an 8-bit byte sum from the UTF-8 bytes of your input and shows the hexadecimal value, decimal value, and byte count. Checksums mainly catch accidental errors. For tamper resistance, authentication, or stronger integrity, use a hash, HMAC, or the mechanism required by your protocol.
How to use this tool
- Paste test text or a sample payload. Do not paste production secrets, access tokens, session cookies, or private customer data.
- Choose CRC-32, Adler-32, or 8-bit byte sum, and confirm whether the other system also uses UTF-8 bytes.
- Before copying the value, check line endings, spaces, encoding, casing, and whether the source expects file bytes instead of text bytes.
What checksums are good for
CRC-32, Adler-32, and byte sums are commonly used to catch accidental copy, transfer, or storage errors. They are sensitive to small input changes, so they are useful when comparing examples, logs, or protocol documentation.
Not encryption or strong integrity
Checksums can collide and do not use a secret key. An attacker may be able to craft different content with an acceptable checksum. For malicious tampering scenarios, use Hash Generator, HMAC Generator, or the signature mechanism required by the protocol.
Local processing and encoding limits
The tool calculates over the UTF-8 bytes of the current text field. It does not read local files, upload content, or infer another system's character set. Results may differ if another system uses raw file bytes, GBK, Latin-1, BOM-prefixed content, or different line endings.
Frequently asked questions
How is CRC-32 different from SHA-256?
CRC-32 is a checksum for catching accidental errors. SHA-256 is a cryptographic hash with stronger collision resistance, but it is still not keyed authentication. Use HMAC or signatures when message origin matters.
Can empty text have a checksum?
Yes. Empty text has a deterministic checksum and is often useful for test vectors or implementation checks.
Why does another checksum tool give a different value?
Common causes include encoding, trailing line endings, spaces, casing, BOM bytes, file bytes versus text bytes, algorithm initialization, and output format.
Can this prove content was not maliciously modified?
No. A checksum has no secret key and has collision limits. Treat it as an accidental-error check, not a tamper-proof integrity or authentication result.
Last updated: