Awaiting input
Every interpretation derived from the same input.
Enter a hex value above to see every conversion.
ASCII output uses one decimal number per byte, separated by spaces. Bytes outside the printable range still produce their codepoint so you can spot control characters quickly.
Bytes are read left-to-right. Each byte is rendered as its decimal codepoint (0–255). For text-friendly output, switch to the Hex to Text variant.
Decode hex into the decimal ASCII / Unicode codepoint of every byte. Useful when documentation describes payloads in decimal and you need a quick translation from a hex dump.
1A3F.ASCII output uses one decimal number per byte, separated by spaces. Bytes outside the printable range still produce their codepoint so you can spot control characters quickly.
Bytes are read left-to-right. Each byte is rendered as its decimal codepoint (0–255). For text-friendly output, switch to the Hex to Text variant.
Need other directions? Try the Decimal to Hex, Binary to Hex, or Text to Binary tools.
Why list ASCII codes instead of characters?
Decimal codes survive transport that mangles unprintable characters, and they match many spec tables verbatim.
Who relies on this format?
Protocol authors documenting wire formats, CTF teams parsing decimal-encoded flags, and educators showing how text becomes bytes.
When should I use this over Hex to Text?
When the bytes include non-printable control characters or when your downstream tool expects decimal codes.
Where does the separator come from?
The encoder uses spaces. Replace them with comma or newline in your editor if your destination expects a different delimiter.
What if a byte is above 127?
It still renders as the decimal value. UTF-8 multibyte sequences appear as separate codes; combine them via Hex to Text for the rendered character.
How can I round-trip back to hex?
Feed the decimal codes into the ASCII to Base64 or Decimal to Binary tools, then back to hex via Binary to Hex.