Calculate Adler-32 for text or a file
Adler-32 combines two running sums into a 32-bit checksum. It is useful when a format or application explicitly expects Adler-32, such as the checksum field in zlib. It is not interchangeable with CRC-32 or a cryptographic hash.
The first sum starts at 1 and accumulates byte values; the second starts at 0 and accumulates the first sum. Both are reduced modulo 65521. The second sum forms the high 16 bits and the first forms the low 16 bits, as specified by RFC 1950. This page computes a checksum of your selected bytes; it does not decompress or validate a zlib container.
Reproduce the supplied example
Load example (switches to text) inserts 123456789, with no newline. Choose Calculate checksum. The result is 091E01DE in hexadecimal and 152961502 in unsigned decimal for nine input bytes. Adding a space or newline changes the bytes and normally changes the checksum. For an empty input, the expected hexadecimal result is 00000001.
Choose text or exact file bytes
Text mode encodes the textarea contents as UTF-8 without adding a BOM or normalizing Unicode. An existing U+FEFF character contributes its UTF-8 bytes. Browser textareas may normalize pasted CRLF or CR line endings to LF, so use file mode when original line endings matter. Unpaired surrogate code units are rejected instead of silently replaced.
Enable Use local file bytes, choose a file and calculate. The file is read locally as raw bytes, including any BOM, binary values and original line endings. Its filename and extension do not affect the result. Empty files are valid. Switching modes or editing input clears old output; a completed read from an earlier selection cannot replace a newer result.
Limits and exported results
Text is limited to 200,000 UTF-16 code units. Files are limited to 10 MiB, exactly 10,485,760 bytes, before reading. This browser implementation reads the complete bounded file into memory; it is not a streaming checksum service for large archives.
The visible result shows the algorithm, byte count, eight uppercase hexadecimal digits and an unsigned decimal integer. Copy hexadecimal copies only the eight digits. Download JSON exports all four fields without an added newline. The hexadecimal display is a numeric representation, not a statement about byte order in a binary file format.
What a matching checksum means
A checksum can help detect accidental changes, but different inputs can share the same 32-bit result. A match does not prove authenticity or protect against deliberate modification. Compare values produced with the same algorithm and identical input bytes. For signed software downloads, follow the publisher's signature-verification process instead of substituting this calculator.
Use UTF-8 Byte Inspector to understand text byte differences, or CRC-32 Calculator when your expected checksum uses that other algorithm.





