ASCII Code to Text

No — this page only goes one way, from numbers to characters. For the opposite direction look at the Text to Hex and Text to Binary pages, which show the same character table in base 16 and base 2 and are easy to translate into decimal values afterwards.

Spaces and commas in any mix, with any amount of whitespace between values. A line like 72,101, 108 108 111 parses exactly the same as one written with single spaces. Line breaks count as separators too, so a column of numbers copied out of a spreadsheet or a debugger can be pasted in unchanged.

Plain ASCII covers only 128 positions, so anything beyond the Latin alphabet is not in the table. Values above 127 are read as Unicode code points instead, and individual UTF-8 bytes written one per number will assemble into stray symbols because one letter takes two bytes there. For byte-level dumps use the Hex to Text page.

There is no fixed cap, only the memory your tab has. A few thousand values decode instantly; hundreds of thousands will make the interface stutter, since the whole string is assembled in one pass and held in memory. Split very large dumps into chunks and join the pieces in your editor.

A non-numeric fragment does not become a character — it is skipped or leaves a gap in the output. Strip 0x prefixes, quotes, column headers and tab characters from what you pasted so only numbers and separators remain, then run the conversion again.

Yes. The page opens in any mobile browser, the text areas stretch to the screen width, and the copy button writes to the system clipboard. No app is needed, and because the parsing is done by JavaScript on the device itself it keeps working when the connection drops.