ASCII / Text Converter

About the ASCII / text converter

Each character is converted to its Unicode code point and then rendered in the chosen base. Decimal, hex, binary, and octal values are space-separated tokens — paste any of those formats back in as input and select the matching mode to convert back to text. Hex values are accepted with or without a 0x prefix.

When to use it

This is the go-to tool when a character is not what it looks like. Debug encoding bugs by checking exactly which code point a string really contains, translate a byte sequence from a protocol dump, a serial log, or a hardware datasheet back into readable text, or inspect the bytes your program will send on the wire. It is equally handy for learning: convertingA to 65 and back builds intuition for how computers store text.

How this tool works

In text mode each character maps to its code point viacodePointAt; in the numeric modes, whitespace-separated tokens are parsed in the selected base — decimal, hex (with optional0x), binary (0b), and octal (0o). Output for hex is zero-padded to two digits so byte values read cleanly, and binary is padded to eight bits.

Edge cases and limitations

Strict ASCII covers code points 0–127, but this tool works on the full Unicode range, so accented letters, emoji, and CJK characters convert correctly rather than erroring. Emoji made of multiple code points (like 👨‍👩‍👧) produce one token per code point. A token that does not parse in the selected base — for exampleFF in decimal mode — is reported asInvalid token with the offending value named, so you can fix the input rather than guessing at the output.

Example

Hello in decimal is72 101 108 108 111 and in hex48 65 6C 6C 6F. Paste either token list back in and select the matching input mode to recover the word.

Related tools

For a higher-level view of the same bytes as text, the Base64 encodershows the compact string form, and the URL encodershows the percent-escaped representation used inside URLs.