CRC-16 Hash Generator
HG-33Paste text or hex bytes and get the CRC-16 in hex and decimal. Pick one of five common variants, or show all five at once.
Runs in your browser. Nothing is uploaded.
Text (UTF-8) or hex bytes
CRC-16
How to use it
- Type or paste text, or tick Input is hex bytes and paste bytes such as 31 32 33.
- Pick the CRC-16 variant your device or protocol names.
- Press CRC-16 for that variant, or All variants to compare the five.
- Tick UPPERCASE hex if you want capital letters.
- Copy the result, or download it as a .txt file.
Why there are several CRC-16s
CRC-16 is a family. Variants differ in the polynomial, the starting value, whether the bits are reflected and what is XORed at the end, so the same input gives a different value in each. The five here follow the CRC catalogue and match its check values for the text "123456789": ARC is bb3d, CCITT-FALSE is 29b1, XMODEM is 31c3, MODBUS is 4b37 and KERMIT is 2189. Others, such as X-25 or DNP, are not included.
Text or raw bytes
By default the text is encoded as UTF-8 and checksummed. Protocol frames are usually written as hex bytes, so tick Input is hex bytes and paste them; spaces, colons and a leading 0x are ignored, and an odd number of digits is an error. A CRC catches accidental corruption such as noise on a serial line. It is not a security hash: anyone can craft data with a chosen CRC.
Error messages and what to do
| Message | What it means | Fix |
|---|---|---|
The input is not valid hex: it has an odd number of digits. | Hex input mode needs whole bytes, two digits each. | Add the missing digit, for example write 0A instead of A. |
The input is not valid hex: use only 0-9 and a-f (spaces, colons and a leading 0x are ignored). | Hex input mode found a character that is not a hex digit. | Remove that character, or untick the hex option to checksum the text as typed. |
Questions people ask
How do I calculate a CRC-16 online?
Paste your text, or hex bytes with the hex option ticked, pick the variant and press CRC-16. The result is shown in hex and decimal. If you do not know the variant, press All variants and compare with the value you expect.
Which CRC-16 variant should I choose?
The one your device, file format or protocol names. Modbus uses CRC-16/MODBUS, XMODEM transfers use XMODEM, and many older formats use ARC. The same bytes give different results in each, so a mismatch usually means the wrong variant.
What is the CRC-16 of "123456789"?
It depends on the variant: ARC gives bb3d, CCITT-FALSE 29b1, XMODEM 31c3, MODBUS 4b37 and KERMIT 2189. These are the catalogue check values, and this page reproduces them.
Can I checksum raw bytes instead of text?
Yes. Tick Input is hex bytes and paste the bytes in hex, with or without spaces or a 0x prefix. The tool then checksums those bytes directly instead of encoding your text as UTF-8.
Is CRC-16 a secure hash?
No. It is built to catch accidental errors, and it is easy to produce different data with the same CRC on purpose. For tamper detection use a cryptographic hash such as SHA-256.
About this tool
CRC-16 is a family, and the same input 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. By default the text is checksummed as UTF-8; tick the hex option to checksum raw bytes written in hex (spaces and a leading 0x are ignored), which is how protocol frames are usually shown.