Hex to Text

What this Hex to Text tool does

This tool follows a byte-oriented pipeline: hexadecimal pairs become bytes, and those bytes are decoded as strict UTF-8 text. The input 48 65 6C 6C 6F becomes bytes 48, 65, 6C, 6C, 6F, then the UTF-8 decoder produces Hello. Processing runs locally in your browser.

The tool is intentionally one-way. It does not encode text into hex on this route. Use Text to Hex for the reverse workflow.

This distinction matters when you are debugging data copied from logs, packet captures, database dumps or API traces. A hex dump is normally a representation of bytes, not a list of characters. The page therefore validates the byte syntax first, then validates UTF-8 separately, so you can tell whether the problem is malformed hex or a valid byte stream that is not UTF-8 text.

Hex bytes vs Unicode code points

Hex bytes and Unicode code points are different notations. UTF-8 bytes for é are C3 A9, while the Unicode code point is U+00E9. The byte E9 alone is not valid standalone UTF-8 for é; it may be meaningful in another legacy encoding, but this page validates strict UTF-8.

For emoji the difference is even more visible. 😀 is Unicode code point U+1F600, but its UTF-8 byte sequence is F0 9F 98 80. Entering 1F600 as continuous hex means the bytes 1F, 60 and an incomplete final nibble; it is not the same thing as entering a Unicode code point.

Supported hex input formats

48 65 6C 6C 6F
48656C6C6F
0x48 0x65 0x6C
\x48\x65\x6C

Auto-detect accepts clear formats and rejects mixed input such as 0x48 65 \x6C. Byte-pair mode can allow ASCII whitespace, commas or colons according to the separator setting. Continuous mode requires only hexadecimal digits and an even digit count.

Separators are deliberately limited. Ordinary spaces, tabs and line breaks are safe to ignore when that option is selected, but non-breaking spaces, zero-width spaces and punctuation outside the selected format are reported. That prevents invisible copied characters from changing how the byte stream is read.

UTF-8 examples

Invalid UTF-8 sequences

Hex syntax can be valid while the bytes are not valid UTF-8. Common failures include truncated sequences such as C3, unexpected continuation bytes such as A0 A1, overlong encodings such as C0 AF, surrogate encodings such as ED A0 80, and four-byte sequences above U+10FFFF such as F4 90 80 80. Diagnostics use one-based byte offsets.

The output area does not silently replace malformed byte sequences with U+FFFD. If UTF-8 text mode fails, switch to Hex byte inspection to confirm the exact bytes. This is useful for binary headers such as FF D8 FF E0, where the hex is well-formed but the data is not text.

Binary data vs text

Hexadecimal may represent images, PDFs, ZIP files, protocol packets or arbitrary bytes. Valid hex does not guarantee valid UTF-8. If the input is binary, choose Hex byte inspection to normalize and review the parsed bytes without forcing a text decoding step.

If you know the bytes use another character encoding, use a tool designed for that encoding instead of forcing UTF-8. A byte value such as E9 may decode to é in Windows-1252 or ISO-8859-1, but it is not legal UTF-8 by itself. Keeping that boundary clear avoids mojibake and makes error reports easier to reproduce.

How to use the tool

1. Paste hex bytes into Hex byte input.
2. Choose the input format or keep Auto-detect.
3. Choose the separator handling for byte-pair input.
4. Select UTF-8 text or Hex byte inspection output.
5. Use normalization only after successful UTF-8 decoding when you intentionally want to change the Unicode sequence.
6. Review diagnostics, statistics and warnings before copying or downloading the output.

Privacy and processing

This tool runs in your browser. Your input is not submitted to UnicodeNow. Output is written to a textarea as text, and downloads use Blob URLs that are revoked after use.

Common uses

• Debugging API payload bytes.
• Inspecting UTF-8 sequences.
• Converting copied hex dumps.
• Diagnosing mojibake.
• Verifying emoji byte sequences.
• Checking malformed UTF-8.
• Reviewing binary headers.

For source-code escape syntax such as \x48, this tool accepts the byte form only when the \x-prefixed input format is selected. It still treats the result as bytes, not as JavaScript, Python or C source code, and it never executes the input.

Frequently asked questions