What hex formats are accepted?

Any mix works — continuous (48656c6c6f), space-separated (48 65 6c 6c 6f), colon-separated (48:65:6c) or 0x-prefixed. Non-hex characters are ignored, so you can paste dumps directly.

Why do I get an 'odd number of digits' error?

Each byte needs exactly two hex digits, so a valid hex string always has an even length. An odd count means a digit was lost — usually a truncated copy-paste or a stray character at the start.

Is hex the same as Base16?

Yes. RFC 4648 defines Base16, which is standard hexadecimal with uppercase letters. This decoder accepts both upper and lower case.

Can I convert text back to hex?

Use the Hexdump & Byte Stream Parser — it renders any input as an offset / hex / ASCII dump, which is the reverse view of what this tool does.

Hex to Text Decoder

Convert hexadecimal (Base16) back to readable text or a raw byte view.

live · client-sideData, Radix & Stringfree · no sign-up

RAW INPUT

DECODED

Output appears here as you type — decoded on your device.

Input is processed on your device. Nothing you paste is sent anywhere.

What is the Hex to Text Decoder?

A hex decoder converts hexadecimal notation back into bytes, reading each pair of hex digits (00–FF) as one byte and then interpreting the resulting byte sequence as text.

Hexadecimal encodes each byte as two characters drawn from 0–9 and a–f. One hex digit maps to exactly four bits, so a byte is always two digits — which makes hex the default way to print binary in debuggers, packet captures, hash digests and memory dumps. It is compact enough to read and precise enough to be unambiguous.

This decoder pairs the digits, converts them to bytes and interprets the result as UTF-8. It is deliberately forgiving: 0x prefixes, spaces, commas, colons and newlines are all stripped, so you can paste a line straight out of Wireshark, gdb or a log file without cleaning it up first.

Alongside the text you get the byte count and a hex preview, which is usually enough to tell immediately whether you are looking at a printable string, a UTF-8 sequence, or an opaque binary structure that needs a different decoder.

Hex to Text Decoder at a glance

Also called: Base16 (RFC 4648), hexadecimal
Digits per byte: 2 (one nibble each)
Accepted input: 0x prefixes, spaces, colons, newlines
Output: UTF-8 text, byte count and hex view

How to use the Hex to Text Decoder

1Paste your hex string in any common format — 48656c6c6f, 48 65 6c 6c 6f or 0x48 0x65.
2The decoded text appears instantly; check the byte count to confirm nothing was truncated.
3Copy the text, or switch to the Hexdump Parser for an offset-aligned view of the same bytes.

When you would reach for it

Turning a hex blob from a packet capture or log line back into readable text.
Checking what a hex-encoded database column or config value actually contains.
Reading hex output from a debugger, disassembler or embedded serial console.

Hex to Text Decoder — frequently asked questions

Last reviewed 25 July 2026 · questions or corrections: contact@decoder.tools