Hex to Text Converter – Decode Hex to Text Online

How to Convert Hex to Text

Decoding hex back to text is the step you take when reading a hex dump, inspecting a packet capture, or recovering a string from raw binary data. Every pair of hex digits is one byte, and every byte maps to a character.

1. Remove any formatting first: spaces, commas, and 0x prefixes are not part of the data.
2. Split the remaining digits into pairs, working from the left. Each pair is one byte.
3. Convert each pair from base 16 to decimal. The left digit is worth sixteen times the right digit, so 43 is 4 times 16 plus 3, which is 67.
4. Look up each decimal value in an ASCII table and write out the matching character.

Worked example: decoding 43 6F 64 65

43 6F 64 65 = "Code"

Reading a Hex Pair

In a two digit hex byte the left digit carries the high four bits and the right digit carries the low four bits. The left digit is multiplied by 16 and the right digit is added to it, so the range runs from 00 (zero) up to FF (255).

That is the entire range a single byte can hold. Values 32 to 126 are the printable ASCII characters, values below 32 are control codes such as tab and newline, and values above 127 belong to multi byte UTF-8 sequences.

ASCII, Unicode, and UTF-8

ASCII is the original character encoding standard, finalised in 1963. It defines 128 characters: the English alphabet in both cases, the digits 0 to 9, common punctuation, and 33 non printing control codes such as tab, newline, and carriage return. Because 128 values fit in seven bits, every ASCII character fits comfortably inside a single byte.

ASCII covers English and almost nothing else, which is why Unicode exists. Unicode assigns a number, called a code point, to every character in every writing system, plus symbols and emoji. UTF-8 is the encoding that turns those code points into bytes, and it was designed so that the first 128 code points encode to exactly the same single bytes as ASCII. That backward compatibility is why plain English text looks identical in both.

The practical consequence for this tool: English letters, digits, and punctuation each produce one byte. Accented characters, Greek, Cyrillic, Arabic, and CJK characters produce two or three bytes each, and emoji usually produce four. The converter handles all of them correctly using UTF-8.

Where Hex Decoding Fails

• An odd number of hex digits cannot be decoded, because bytes always come in pairs. This usually means a digit was dropped when copying.
• Any character outside 0 to 9 and A to F is invalid. Stray punctuation from a copy and paste is the usual cause.
• Bytes above 7F will not produce sensible characters on their own. They are part of a UTF-8 sequence and need the following bytes to decode correctly.

ASCII Conversion Table

Every printable ASCII character with its decimal code, hexadecimal byte, and binary byte. Codes 0 to 31 are control characters and are not printable, so they are not listed here.

Looking for a different conversion? Browse every developer tool including binary, hex, octal, and Base64 converters.