Hex to text
Decode hex bytes back into readable text in UTF-8, UTF-16, EUC-KR or ASCII.
Result
More octal, code points
Settings
Recent
To read hex as text, turn every pair of hex digits into a byte and decode the bytes with the right encoding. Paste something like 48 65 6C 6C 6F, with or without spaces, 0x or \x, and the words show up; if they look garbled, try another encoding. No account is needed.
How to do it by hand
- Strip separators and prefixes so only hex digits are left.
- Cut the digits into pairs. Each pair is one byte from 00 to FF.
- Decode the bytes with the encoding they were written in, or UTF-8 if you are not sure.
- If odd symbols appear, the encoding is probably wrong or a byte has gone missing.
Worked examples
4F 4B
4F = 79 = O, 4B = 75 = K
OK
E2 82 AC (UTF-8)
three bytes that decode to U+20AC
€
B0 A1 B3 AA (EUC-KR)
B0 A1 = 가, B3 AA = 나
가나
Common mistakes
- Leaving an odd number of digits. Every byte needs two, so 4F4 is incomplete.
- Decoding UTF-8 bytes as EUC-KR or the other way round, which turns Korean into nonsense.
- Mixing up the digit 0 and the letter O when copying from a printout. Only 0 to 9 and A to F are valid, and the tool points at anything else.
Reading UTF-8 by the first byte
| First byte | Bytes | Code point range | Example |
|---|---|---|---|
| 00-7F | 1 | U+0000-U+007F | A = 41 |
| C2-DF | 2 | U+0080-U+07FF | é = C3 A9 |
| E0-EF | 3 | U+0800-U+FFFF | 가 (Korean) = EA B0 80 |
| F0-F4 | 4 | U+10000-U+10FFFF | 😀 = F0 9F 98 80 |
| 80-BF | - | Continuation byte (never first) | |
| C0, C1, F5-FF | - | Never used in UTF-8 |
Questions people ask
Why do I see a question mark in a diamond?
Some bytes do not form a valid character in the chosen encoding. Try another encoding or look for a missing byte.
Can I paste hex with 0x before every byte?
Yes. 0x, \x, spaces and commas are all stripped before decoding.
Does it read old Korean files saved in EUC-KR?
Yes. Pick EUC-KR and Korean bytes such as B0 A1 come back as 가.