Checksum Calculator

Supports multiple checksum algorithms such as cumulative sum, LRC, and BCC, and can calculate file checksums individually or in batches.

Bug report

Browser execution mode: Your data is processed in your browser and is not uploaded to the server.

Speed and Stability: Processing speed depends on your device and browser. For large batch work, the desktop version may be more stable.

Loading tool, please wait...

If the online tool fails to load or run, try the desktop tool.https://tools.yikeaigc.com/

Instructions

Software Usage Instructions

Select a feature page: The tool provides four pages: “Input Calculation,” “Batch Files,” “File Comparison,” and “Record Settings.” Please set the input format, algorithm, and output format before starting processing.
Input Calculation: Select hexadecimal, text, ASCII code, Base64, or a single file as the data source; you can click “Sample Data” to quickly fill in test content.
Set the algorithm: You can choose SUM8, SUM16, SUM32, LRC, BCC, complement, CRC-8, CRC-16/Modbus, CRC-16/CCITT, CRC-16/XMODEM, CRC-32, MD5, SHA-1, SHA-256, SHA-384, SHA-512, or display all results.
Adjust output: Supports output in hexadecimal, decimal, binary, and all formats. You can set big-endian/little-endian display, HEX uppercase/lowercase, separator, initial accumulated value, result XOR value, and length bytes.
Checksum verification: After calculation is complete, paste the expected checksum value in the “Checksum Verification” area, and the tool will look for matching algorithms in the current results.
Batch Files: Drag and drop or select multiple files, check the algorithms to calculate, then click “Start Batch Calculation.” The interface displays the first 20 files, while exported results include all files.
File Comparison: Select File A and File B separately, then choose SHA-256, SHA-1, SHA-512, MD5, or CRC-32 for comparison to determine whether the contents of the two files are identical.
Export and save: Batch results can be copied, downloaded as CSV, downloaded as JSON, or downloaded as a ZIP report; commonly used settings can be saved by clicking “Save Settings,” and history records can be viewed or exported on the “Record Settings” page.

FAQ

A: A SUM checksum adds bytes one by one and then takes the value according to the bit width; LRC is usually the complement based on the checksum; BCC performs an XOR operation on all bytes. They are fast to calculate and are commonly used in serial communication, simple protocols, and message verification.

A: It is not recommended. Different CRC algorithms may have different polynomials, initial values, input reflection, output reflection, and XOR values, so the same data segment will produce different results. Please choose the corresponding algorithm according to the device protocol or interface documentation.

A: Space-separated, comma-separated, hyphen-separated, 0x-prefixed, and continuous formats are supported, such as “48 65 6C 6C 6F,” “0x48,0x65,” or “48656C6C6F.” Every two hexadecimal characters represent one byte.

A: Big-endian and little-endian mainly affect the display order of multi-byte results. For example, for the same 16-bit result, big-endian displays the high byte first, while little-endian displays the low byte first. In practice, choose according to the communication protocol, device manual, or file format requirements.

A: MD5 is fast and suitable for general file consistency checks; SHA-1 is no longer suitable for security purposes; SHA-256 is better suited for scenarios such as verifying downloaded files and tamper checks. If the source provides a specified algorithm, you should prioritize the algorithm provided by the source.

A: To keep the interface clean, the batch preview only displays the first 20 files. The actual processing will cover all selected files, and the CSV, JSON, and ZIP reports will also include the complete batch results.

A: If even one byte of the file content is different, the hash or CRC result will change. Common causes include different file versions, incomplete downloads, transfer corruption, recompression, metadata changes, or content changes after editing and saving.