Convert Hex to ASCII

Each pair of hex digits represents one byte (0-255), and each byte maps to one ASCII code point. 48 hex = 72 decimal = letter “H”. So 48656C6C6F decodes byte-by-byte to 72, 101, 108, 108, 111 → “Hello”. The tool repeats this for every pair in your input.

Auto-detect strips the common four: 0x prefixes (0x48 0x65), commas (48,65), spaces and tabs (48 65), and plain continuous digits with no separators. Underscores as visual separators (48_65_6C) are also handled. Mix and match – 0x48, 0x65 0x6c works fine.

Bytes outside the printable ASCII range 32 (space) through 126 (~). That includes control characters like x00 (null), x0A (newline), x1B (escape), and x7F (DEL), plus everything from x80 upward (which isn’t valid 7-bit ASCII at all – those are extended/high bytes used in code pages and UTF-8).

Escape is safest for inspecting binary data – you see every byte clearly. Placeholder is cleanest for mostly-text data with occasional control bytes you want to ignore visually. Strict is for validation – if your hex is supposed to be pure printable ASCII, this flags anomalies as errors. Raw emits literal control characters – useful when piping into a shell that interprets them, dangerous in a browser text box.

You get an error: “Hex string must have an even number of digits.” Every byte needs 2 hex digits (one for each nibble), so A alone is ambiguous – is it 0A or A0? Rather than guessing, the tool refuses. Prepend or append a zero if you know which you meant.

When each line of your input is a separate hex sequence (maybe a column of database values, or multiple packets from a capture). Batch mode decodes each line independently and shows which ones failed in a red error list below the output. Without batch mode, all lines are concatenated into one big hex value.

ASCII is strictly 7-bit (bytes 0-127). UTF-8 extends to multi-byte sequences for characters beyond ASCII – a byte like C3 A9 in UTF-8 is the single character “é”, but in pure ASCII it’s two non-printable bytes. If your hex represents UTF-8-encoded text, use the hex-to-UTF-8 tool instead; this one treats each byte as a standalone ASCII code.

No. Everything runs in your browser’s JavaScript engine – no network requests fire during conversion, and no server stores or logs your input. You can verify in the Network tab of DevTools. The tool keeps working even after you disconnect from the internet.

Practically unlimited. The algorithm is O(n) and processes roughly 1 MB of hex (100,000 bytes) in under 50 ms on a modern laptop. Very large pastes may take a moment to render in the output textarea, but the conversion itself stays fast.

Yes. Feed this tool’s output into a “text to hex” converter (or use our companion “convert ASCII to hex” tool), and you’ll recover the original hex exactly – assuming every byte was in the printable ASCII range. Non-printable bytes round-trip correctly in Raw and Strict modes; Escape mode adds explicit backslash sequences that the reverse tool would need to re-interpret.