ASCII to Text Converter: Easily Convert ASCII Codes to Text

Decode a List of ASCII Numbers into Readable Text

The ASCII to Text Converter turns a sequence of decimal character codes, such as 72 101 108 108 111, into the text they stand for, in this case Hello. Paste or type the numbers on the left, in the panel titled ASCII Code, and the decoded string appears on the right, in the panel titled Standard Text, as you type. There is no Convert button to press: the output refreshes on every keystroke.

It is a small, focused utility for programmers debugging byte arrays, students working through character-encoding exercises, puzzle and CTF players decoding hidden messages, and anyone who has been handed a row of numbers and told "it's ASCII".

A Short Refresher on ASCII

ASCII, the American Standard Code for Information Interchange, assigns a number from 0 to 127 to each of 128 characters. Codes 0 to 31 and 127 are control characters (tab, line feed, carriage return and others that do not print), 32 is the space, and 33 to 126 are the visible letters, digits and punctuation found on an English keyboard. Because the first 128 Unicode code points are identical to ASCII, ASCII codes remain the common language of text in programming, network protocols and file formats.

A handy pattern: an upper-case letter and its lower-case partner always differ by exactly 32. A is 65 and a is 97.

How to Use the Converter

1. Click in the ASCII Code box. Its placeholder reads "Type space-separated ASCII integers (e.g. 72 101 108 108 111)".
2. Type your numbers separated by spaces, tabs or line breaks, or click Paste under the box to insert whatever is on your clipboard. Your browser may ask permission the first time.
3. Read the result in the Standard Text box. It is read-only, so you cannot accidentally edit the output.
4. Click Copy under the Standard Text box to copy the decoded text, or Copy under the ASCII Code box to copy your input.
5. Click the trash icon under either box to clear both boxes and start again.

Worked Examples

How the Tool Reads Your Input

Knowing the parsing rules saves confusion when an input does not decode as expected. The conversion is done in your browser by a few lines of JavaScript; nothing is sent to a server.

• Separators. The input is trimmed and split on any run of whitespace: spaces, tabs or new lines. Multiple spaces count as one separator.
• Numbers are decimal. Each piece is read as a base-10 integer. Hexadecimal such as 0x41, binary such as 01000001 and octal are not interpreted as such. 0x41 is read as 0, and 01000001 is read as the decimal number one million and one.
• Leading digits win. A piece that starts with digits but has extra characters after them is read up to the first non-digit. 72, becomes 72 and 65.9 becomes 65. This is why "72, 101, 108" with spaces after the commas still decodes correctly.
• Commas without spaces do not split. 72,101,108 is a single piece and is read as just 72, giving "H". Add spaces after the commas, or replace the commas with spaces.
• Invalid pieces. If any piece does not start with a number, for example a word or a stray letter, the ASCII Code card is outlined in red with the label "Invalid sequence", and the Standard Text box keeps showing the last valid result until you fix the input.

Beyond 127: Extended Characters

The tool does not stop at 127. Each number is passed to JavaScript's String.fromCharCode, which treats it as a UTF-16 code unit from 0 to 65535. That means:

• 128 to 255 give the Latin-1 range of Unicode, so 233 is "é" and 169 is "©". This is not the same as Windows-1252, where 128 is the euro sign; here 128 is an invisible control character.
• Larger values give other Unicode characters directly: 8364 is "€", 937 is "Ω".
• Characters outside the Basic Multilingual Plane, including most emoji, need two numbers, a surrogate pair. For example 55357 56832 produces 😀.
• Numbers above 65535 or below 0 wrap around rather than producing an error. 65601, for instance, comes out as "A". Treat such output with suspicion; it usually means the input was not plain character codes.

Where This Comes in Handy

• Debugging. Logs and debuggers often print strings as arrays of byte values. Paste the array, minus brackets, to see the actual text.
• Coursework. Computer science exercises frequently ask students to encode or decode a message by hand; the tool lets you check your answers.
• Puzzles and capture-the-flag challenges. Hidden messages are often given as decimal codes.
• Data cleaning. Exported spreadsheets or sensor data sometimes contain text stored as numeric codes.
• Teaching. Typing codes and watching letters appear is an easy way to demonstrate how computers represent text.

Tips

• When copying an array like [72, 101, 108], remove the brackets, or make sure there is a space after each comma.
• Use 10 to put line breaks into the output, and 32 for spaces between words.
• If your numbers are hexadecimal (often written with pairs like 48 65 6C), convert them to decimal first; this tool reads only decimal.
• Use the Copy button under Standard Text rather than selecting text manually, so invisible characters like tabs are copied too.

What Not to Do

• Do not paste binary strings and expect letters. 01001000 is read as a decimal number, not as the binary for "H".
• Do not join numbers with commas only. Without whitespace they are not separated.
• Do not assume codes 128 to 255 match an old code page like Windows-1252 or CP437; they follow Unicode.
• Do not rely on the output if you see unexpected symbols or blank squares; check for wrapped values or non-decimal input.

Limitations

• Decimal input only; no hex, binary or octal modes.
• One direction: codes to text. There is no text-to-codes panel on this page.
• No validation of the 0 to 127 ASCII range; values outside it are decoded as UTF-16 code units or wrapped.
• Control characters (0 to 31) are inserted as-is and are mostly invisible in the output.
• The Paste button depends on browser clipboard permission; if it is blocked, paste with your keyboard instead.

Frequently Asked Questions