CRC16 Checksum Calculator
HG-17Paste text to get its CRC-16 in hex and decimal for the variant you pick. The text 123456789 gives bb3d for ARC and 4b37 for Modbus.
Runs in your browser. Nothing is uploaded.
Text (checksummed as UTF-8)
CRC-16
How to use it
- Type or paste your text into the input box. Sample loads 123456789, the standard check text.
- Choose the CRC-16 variant your device or protocol uses.
- The checksum appears as you type, in hex and in decimal. Tick UPPERCASE hex if you need capitals.
- Copy the result, or download it as a .txt file.
CRC-16 is a family
There is no single CRC-16. Variants differ in polynomial, starting value, bit order and final XOR, and the same text gives a different result in each. This page offers five from the CRC catalogue. For the text 123456789 they give: ARC bb3d, CCITT-FALSE 29b1, XMODEM 31c3, MODBUS 4b37 and KERMIT 2189. If your result differs from a device manual, the variant is the first thing to check.
Picking the right variant
ARC and MODBUS share the polynomial 0x8005 and reflected bits; ARC starts at 0 and MODBUS at 0xFFFF. CCITT-FALSE, XMODEM and KERMIT share the polynomial 0x1021: CCITT-FALSE starts at 0xFFFF, XMODEM at 0 without reflection, and KERMIT at 0 with reflection. Variants such as X-25, DNP and USB are not included here, so a protocol that names one of them cannot be checked on this page.
What it checksums
The text is encoded as UTF-8 and the CRC is taken over those bytes, so a trailing space or line break changes it. It is not a way to checksum a hex string of bytes or a binary file. A CRC finds accidental corruption; it is not a security hash, since anyone can craft data that matches a given CRC.
Questions people ask
How do I calculate a CRC16 online?
Paste your text, pick the variant, and read the hex and decimal result. Tick UPPERCASE hex if you want capitals, then copy it or download it as a .txt file. Everything runs in your browser.
What is the CRC16 of 123456789?
It depends on the variant: ARC bb3d, CCITT-FALSE 29b1, XMODEM 31c3, MODBUS 4b37, KERMIT 2189. These are the catalogue check values, so they make a good test for any CRC-16 code you write.
Which CRC16 does Modbus use?
Modbus RTU uses CRC-16/MODBUS, with polynomial 0x8005, a starting value of 0xFFFF and reflected bits. Pick MODBUS in the select. Pay attention to byte order when placing the result on the wire; this page shows the 16-bit value only.
What is CRC-16/CCITT-FALSE?
It is the CRC with polynomial 0x1021, a starting value of 0xFFFF, no bit reflection and no final XOR. It is often called CRC-16/CCITT in code, though the catalogue name CCITT-FALSE separates it from the reflected KERMIT variant.
Why does my CRC16 not match my device?
Most often the variant is wrong, or the bytes differ: a hex string typed as text is hashed as characters, not as the bytes it describes. This page takes the text you type as UTF-8, so non-text frames cannot be entered.
Is CRC16 a hash?
It is a checksum, not a cryptographic hash. It is cheap and catches accidental bit errors, but it is trivial to forge and only 16 bits long, so unrelated inputs collide often. Use SHA-256 when you need a fingerprint.
About this tool
CRC-16 is a family, and the same text gives a different value in each variant. The five here follow the CRC catalogue parameters and are checked against its check values for the text "123456789": ARC bb3d, CCITT-FALSE 29b1, XMODEM 31c3, MODBUS 4b37 and KERMIT 2189. Other variants such as CRC-16/X-25 or DNP are not included. Pick the one your device or protocol names. A CRC catches accidental corruption and is not a security hash. The text is checksummed as UTF-8, not as a hex string of bytes.