About ASCII to Text
ASCII to Text takes decimal character codes and rebuilds the string — 65 66 67 becomes ABC. It is the reverse of Text to ASCII, and it is how you turn a list of numeric codes back into readable content, whether those codes came from documentation, a test fixture, or a data interchange format that stores characters numerically.
The parsing is deliberately forgiving. Any run of digits is treated as one code, so codes may be separated by spaces, commas or line breaks without changing the result. That matters in practice because code lists arrive in all three forms and none of them is worth rejecting.
One boundary is worth knowing: codes above 65535 are discarded rather than decoded, since they fall outside what a single code unit can represent. If you are working with emoji, whose code points sit above that line, no output will appear for those entries — a signal that the data is not simple decimal code points.
How to use ASCII to Text
- 1 Paste the decimal character codes you want to convert, separated by spaces, commas or newlines.
- 2 The reconstructed text appears immediately.
- 3 If nothing appears, check that the values are within the range a character code can hold.
Frequently asked questions
What separators are accepted?
Any non-digit character works as a separator, so spaces, commas, semicolons and line breaks all behave the same way. The codes are found by scanning for runs of digits, so the exact separator does not matter.
Why did some codes produce no output?
Values above 65535 are ignored, because they cannot be represented as a single character code. Emoji and some rarer scripts fall above that boundary — for those you would need a conversion that handles surrogate pairs.
Can I convert back to codes afterwards?
Yes, with the Text to ASCII tool. The pair round-trips exactly for characters in the ASCII range; outside it the codes are still correct but no longer correspond one-to-one with storage bytes.
Will this work for text in other languages?
It works when the codes are Unicode code points, which is what this tool assumes. If the numbers were produced by a different convention — for example raw UTF-8 bytes for non-ASCII text — the output will not match what you expect.
Free, online, and private
Free to use
ASCII to Text is completely free. There is no account to create, no login, and no hidden charge or usage limit.
Runs online in your browser
It is a free online tool that runs entirely in your browser. Nothing to download or install — open the page and start using it right away.
Your data stays private
All processing happens locally on your device. Your input is never uploaded, stored, or tracked, so it never leaves your browser.
How ASCII to Text behaves in detail
These are the specifics of this implementation — the exact ranges, defaults and fixed settings you are working with.
| Parameter | Value |
|---|---|
| Token pattern | runs of digits (\d+), so any non-digit separates two values |
| Accepted values | 0 up to 65535; anything above 65535 is discarded |
| Character construction | String.fromCharCode — one UTF-16 code unit per number |
| Separator tolerance | spaces, commas, letters and newlines all work equally well |
| Sign handling | a minus sign is just another separator, so -1 is read as the value 1 |
Compiled from the implementation of this tool and checked against it by itoolnet.
What ASCII to Text does not do
Knowing the edges of a tool saves more time than another list of its features. These are the cases where it will not do what you might expect.
- Numeric runs are taken whole, not split into pairs of digits: typing 656667 without separators yields one number well above the 65535 ceiling, which is filtered out, so the field goes empty instead of producing ABC.
- String.fromCharCode builds UTF-16 code units, so only the Basic Multilingual Plane can be produced. An over-range value is dropped by the filter rather than reported, which leaves a silent gap in the middle of an otherwise correct result.
- Nothing validates the token lengths. A value like 4 or 65 is accepted as readily as 4100, so a code string that lost a digit still converts — quietly to the wrong character rather than to an error.
Tested and documented by itoolnet, the team that builds and maintains this site.