TontonTools

HEX to Text

Decode hexadecimal back into text — hex byte codes become characters.

100% Free No signup Privacy-friendly Binary & Number Tools
Updated Sep 2026

Share X / Twitter Facebook LinkedIn WhatsApp

How to use HEX to Text

  1. Paste the hex codes separated by spaces — e.g. 48 65 6C 6C 6F. Strip any \x or % prefixes first.
  2. Read the decoded text instantly in the output: Hello.
  3. Check the flagged token if an error shows — a G or other non-hex character is named exactly.
  4. Click “Copy result” to use the recovered string.

What is HEX to Text?

A hex to text converter decodes space-separated hex character codes back into a readable string: 48 65 6C 6C 6F becomes Hello. Each code is read as a number in base 16 and looked up as its Unicode character — the inverse of a hex dump's text column.

This is the decoding direction for anything that arrives as raw hex: strings spotted in packet captures and hex editors, \x escape sequences in code, percent-encoded URL fragments (strip the % signs first), CTF puzzle strings, and configuration blobs that store text as hex.

About the HEX to Text

Paste hex codes separated by spaces and the decoded text appears instantly. Case doesn't matter — 48 65 and 48 65 decode identically whether typed as 4A or 4a.

Real uses: reading the string hiding in a hex dump or binary file (spot 25 50 44 46 → %PDF and you know the file type), decoding a suspicious hex-encoded payload safely to see what it says, translating \x48\x69 escapes from source code, and solving CTF and geocache puzzles that layer hex over messages. Invalid tokens are named exactly, so one mistyped code doesn't silently garble the rest.

Decoding is instant and local to your browser. Text to Hex encodes the reverse direction; if your codes are decimal or binary instead, the ASCII to Text and Binary to Text tools handle those notations.

Frequently Asked Questions

Remove the \x prefixes and add spaces: 48 69 → Hi. The \x is just C/Python escape notation around the same two-digit hex codes.
Some code falls outside printable ASCII — often a transcription error, or the data was never text (compressed/encrypted bytes decode to noise). Check for a missing digit shifting the pairs.
Split it into two-digit pairs first (48 65 6C 6C 6F) — the tool reads space-separated tokens. ASCII text is always byte-aligned, so pairing from the left works.
Each token is read as a Unicode code point: 20AC decodes to €, 1F600 to 😀. Note that's code points, not UTF-8 bytes — a UTF-8 byte sequence like C3 A9 is é's bytes, not two characters.
Yes — decoding just turns numbers into characters in your browser; nothing executes and nothing is uploaded. It is a standard first step when inspecting suspicious strings.

We use cookies for analytics and to keep the tools free via ads. See our Privacy Policy.