About this tool
Hex dumps, packet captures, database blobs and logs often show text as hexadecimal bytes. Paste them here to read the text: 48 65 6C 6C 6F becomes Hello. The decoder accepts bytes with or without spaces, separated by commas, colons or dashes, and with 0x, \x or % prefixes.
How hex becomes text
Each pair of hex digits is one byte (00–FF, 0–255). The bytes are decoded as UTF-8: for English, one byte per character, matching ASCII (48 = 72 = H). Accented letters and emoji use several bytes, so C3 A9 is é and F0 9F 91 8B is 👋.
UTF-8 bytes or code points?
Computers store text as bytes, usually in UTF-8: English letters take one byte each (the same values as ASCII), while é takes two bytes (C3 A9) and most emoji four (👋 = F0 9F 91 8B). Choose UTF-8 bytes to see or decode the real bytes, as in files, network packets and hex dumps. Unicode code points gives one number per character instead (é = 233, 👋 = 128075). ASCII only rejects anything outside the 128 ASCII characters.
Common inputs
48656c6c6f → Hello (continuous)
48 65 6c 6c 6f → Hello (spaced)
0x48, 0x65, 0x6c → Hel (C array)
\x48\x65\x6c → Hel (escaped string)
48:65:6c → Hel (colon-separated)
If you get “not valid UTF-8”, the data is probably binary (an image, compressed data) or in a legacy encoding such as Latin-1, where é is the single byte E9. To convert a hex number (like FF = 255) rather than bytes, use hex to decimal.
FAQ
How do I convert hex to text?
Paste the hex bytes. Each pair of hex digits is one byte, decoded as UTF-8, so 48 65 6C 6C 6F becomes “Hello”.
Does the hex need spaces?
No. A continuous string is split into pairs. Spaces, commas, colons, dashes and 0x, \x or % prefixes are all accepted.
What is 48 65 6C 6C 6F in text?
“Hello”: 48 is H, 65 is e, 6C is l and 6F is o.
Why do I get “not valid UTF-8”?
The bytes do not form UTF-8 text. They may be binary data or text in another encoding such as Latin-1.