How this calculator works
First group digits into bytes, then interpret those bytes using the selected character encoding. UTF-8 uses variable-length sequences. UTF-16 uses two-byte code units and surrogate pairs; automatic UTF-16 mode requires a byte-order mark. Explicit little-endian and big-endian modes accept text with or without a matching mark. Invalid Unicode sequences produce an error rather than replacement characters.
Formula
One byte = 2 hexadecimal digits. UTF-8 ASCII bytes 00 through 7F map directly to the same code points; multi-byte sequences represent higher values.
Worked example
The bytes 48 69 in hexadecimal, or 01001000 01101001 in binary, decode to Hi in UTF-8. C3 A9 in hex decodes to é, one character occupying two bytes.
Advertisement
Frequently asked questions
Why do I get an incomplete-byte error?
The digits must form complete bytes. Add missing digits rather than letting a converter guess the padding.
Which encoding should I choose?
Use the encoding used by the source system. UTF-8 is a common default, but a wrong encoding can produce plausible yet incorrect text.
Why does UTF-16 auto mode require a mark?
The FF FE or FE FF prefix tells the decoder which byte order to use. Select an explicit byte order if there is no mark.