Work through “Hi”: the characters are codes 72 and 105, which as bytes in hex are 48 and 69 — so “Hi” in hex is 48 69. Multi-byte characters take more pairs: 你 is code point U+4F60, which UTF-8 stores as three bytes, giving E4 BD A0. If the mechanics of hex itself are new, binary vs hexadecimal covers why one hex digit is exactly four bits.
Hex to Text Converter
Decode hexadecimal into readable text, or turn text into hex — Unicode-safe, with forgiving input and byte-level detail.
Result
Waiting for input — conversion happens instantly in your browser.
What Hex to Text Conversion Actually Does
Hex is just bytes spelled in base 16 — two digits per byte. Text to hex is a two-step pipeline: text → UTF-8 bytes → hex. Decoding reverses it.
Forgiving Input, Honest Reports
Hex arrives in every imaginable format, and this converter accepts all of them: spaced pairs (48 69), continuous strings (4869), comma-separated lists (48,69) and 0x-prefixed bytes (0x48 0x69). Everything removed is counted in a cleaning report, so nothing changes silently. What it will not do is guess: an odd number of digits or a non-hex character gets flagged with its exact position.
One honest limit: hex only respells bytes. If decoded output looks like gibberish, the bytes were probably never text — or they belong to a different encoding than UTF-8. Hex itself cannot tell you which.
Where Hex Shows Up (and When to Pick Which Notation)
You will meet hex in debugging sessions, log files, memory dumps and color codes like #0F70E6 — anywhere a human reads raw bytes. The quick rule across notations: binary when individual bits matter (our binary to hex page bridges those two), hex when a human reads byte values, and Base64 when bytes must travel through text-only channels like JSON or email (our Base64 converter handles that).
Common Mistakes
- Mistake: an odd digit count.
486is one digit short of a byte. Correction: hex comes in pairs — re-copy the original before trusting the output. - Mistake: treating hex as an encoding. Correction: hex is notation.
48, 72 and01001000are the same byte; what the byte means comes from UTF-8 or ASCII, not from the spelling. - Mistake: worrying about letter case. Correction:
4Fand4fare identical. Case is convention, not content.
Practice
1. Decode 48 69. Bytes 72 and 105 → “Hi”.
2. Write “OK” in hex. O is 79 and K is 75 → 79 is 4F, 75 is 4B — answer: 4F 4B. Check both in the converter above.
Hex to Text FAQ
How do I convert hex to text?
Hex is bytes written in base 16 — two hex digits per byte. To read it as text, turn each pair into a byte and decode those bytes as UTF-8: 48 69 is bytes 72 and 105, which spell “Hi”. The converter above does it instantly, with or without spaces and 0x prefixes.
Is hex an encoding or an encryption?
Neither. Hex is notation — a way to write byte values. It does not decide what the bytes mean (that is UTF-8 or ASCII), and it hides nothing (anyone can read it). 48, 72 and 01001000 are the same byte spelled three ways.
Why does an odd number of hex digits fail?
Because one byte is exactly two hex digits. An odd digit count means a digit was lost or added in copying, so the last byte is incomplete — the converter flags it instead of guessing.
Can hex contain Chinese text or emoji?
Yes. The text is first encoded as UTF-8 bytes, and those bytes are written in hex — so 你 is three bytes, E4 BD A0. Multi-byte characters work the same way, just with more pairs.
What is the difference between hex and Base64?
Both respell bytes as text. Hex is readable byte by byte but doubles the size (2 characters per byte); Base64 is 33% larger and compact for transport, but unreadable at a glance. Use hex for debugging and Base64 for shipping data.
What does 0x mean in front of hex?
The 0x prefix marks hexadecimal in C-style languages — 0x48 means hex 48, decimal 72. It carries no value itself. This converter accepts 0x-prefixed input and strips it automatically.