An ASCII code converter turns every character in the standard 7-bit ASCII character set into a fixed decimal integer from 0 to 127, and rebuilds the original text from those decimal integers. The standard itself, defined in IETF RFC 20 and cross-checked against Unicode's C0 Controls and Basic Latin chart, assigns exactly one number to each of the 128 characters, including 33 non-printable control codes, punctuation, the digits 0–9, the uppercase A–Z, the lowercase a–z, the space, and DEL. Because the assignment is fixed and one-to-one, conversion in either direction is a deterministic lookup, not a translation. A practical tool like the ASCII Converter enforces this strict boundary: it accepts input only inside 0–127, rejects anything outside that range with a visible error, and runs the entire encode or decode operation locally in the current browser tab. This makes ASCII code conversion one of the simplest and most predictable mappings between human-readable text and machine-readable numbers.
The Bounded 7-Bit Range of Standard ASCII
Standard 7-bit ASCII uses 7 binary bits, which gives 27 = 128 possible values, numbered 0 through 127. This is the original American Standard Code for Information Interchange published in the 1960s, formalized as IETF RFC 20, and mirrored in Unicode's C0 Controls and Basic Latin chart. The 128-character set divides into well-defined regions:
| Category | Decimal range | Example values |
|---|---|---|
| C0 control codes | 0–31 | 9 (TAB), 10 (LF), 13 (CR) |
| Printable space | 32 | Space |
| Punctuation and symbols | 33–47, 58–64, 91–96, 123–126 | 33 (!), 44 (,), 64 (@) |
| Digits | 48–57 | 48 (0), 57 (9) |
| Uppercase A–Z | 65–90 | 65 (A), 90 (Z) |
| Lowercase a–z | 97–122 | 97 (a), 122 (z) |
| DEL | 127 | Delete |
This tight, well-documented layout is exactly what makes a converter straightforward — every printable character and every control code has a single, named decimal value. The range is also intentionally narrow: 7 bits were plenty for English-language technical text in the 1960s and gave the standard room to travel over 8-bit channels without escaping.
How Text Becomes Decimal and Back
The encode direction treats the input string as a sequence of characters and replaces each character with its fixed decimal ASCII code, joined with spaces. The decode direction accepts a list of decimal integers separated by spaces, commas, or line breaks, validates each one, and rebuilds the corresponding characters.
Consider the two-character string "Hi":
- The character H is at decimal position 72 in the standard ASCII table.
- The character i is at decimal position 105.
- Encoding produces "72 105".
Decoding "72 105" reverses the lookup: 72 maps back to H and 105 maps back to i, yielding "Hi". Because the assignment is one-to-one, no interpretation step is needed — the tool simply reads or writes the assigned number for each character. For a more detailed walkthrough of the integer side of this mapping, see How to Convert ASCII to Integer: Exact Decimal Values.
An ASCII code converter that respects this rule also refuses inputs that do not belong to the 7-bit set. If the input contains an accented letter, an emoji, or any other character with a Unicode code point above 127, the converter rejects the first character outside 7-bit ASCII and reports its position. If a decoded integer is signed (for example "+72"), fractional (for example "72.5"), hexadecimal ("0x48"), or above 127, it is rejected for the same reason — a strict ASCII converter fails closed rather than silently producing a different encoding.
Encoding and Decoding With the ASCII Converter
The ASCII Converter on Lizely performs both directions of this conversion in your browser, with visible validation messages when the input falls outside the 7-bit range. To use it:
- Open the ASCII Converter and choose the direction: text-to-codes to convert characters into decimal integers, or codes-to-text to decode a list of decimal integers into characters.
- Enter your input. For text-to-codes, type or paste the string directly into the input box. For codes-to-text, paste decimal integers from 0 to 127 separated by spaces, commas, or line breaks.
- Click Convert ASCII. The tool encodes each ASCII character as a space-separated decimal integer, or tokenizes the decoded input, validates every token as an unsigned one-to-three-digit decimal number, and reassembles the result.
- Read the result in the output area. Watch for invisible control characters such as TAB, LF, CR, NUL, or DEL, which may render as blank space or act on the surrounding text.
- Copy the decimal output or the decoded text using the provided copy action. When the result includes control characters and you need them to remain visible, prefer the decimal form or paste into a byte-aware editor.
If the tool reports an error, check that every input character is inside the 7-bit ASCII range, or that every decoded token is a plain decimal integer between 0 and 127. The input limit is 100,000 UTF-16 code units for encoding and 50,000 code tokens for decoding, so even a long paste usually fits without trouble.
Why Control Characters Often Disappear
The 33 codes from 0 to 31 plus 127 are control characters. Most of them do not have a printed glyph at all. When you decode them back into a textarea, they may show nothing, move the cursor, insert a tab, or break onto a new line — depending on the host application.
Decimal 9 is a horizontal tab, decimal 10 is a line feed, decimal 13 is a carriage return, decimal 0 is NUL, and decimal 127 is DEL. If you copy a decoded string that contains these codes into a chat window, an email body, or a word processor, you may see strange spacing, missing lines, or no visible output where you expected characters. The simplest fix is to keep the decimal form, which is unambiguous, and only decode back to text in a context where the control characters are useful — for example, when reconstructing a protocol message that needs explicit line breaks or when working in a byte-aware editor that can show every byte.
How ASCII Converter Differs From Other Encoding Tools
It is easy to confuse a strict 7-bit ASCII converter with other "convert text to numbers" tools, but the differences matter.
| Tool | Scope | Output | Best fit |
|---|---|---|---|
| ASCII Converter | Standard 7-bit ASCII (0–127) | Decimal integers | Strict text-to-codes or codes-to-text within the 7-bit range |
| ASCII Table | Single reference chart | Read-only mapping | Looking up one character at a time |
| Text to Hex | UTF-8 bytes | Hexadecimal | Encoding full Unicode, including emoji and accents |
| Text to Binary | UTF-8 bytes | Binary digits | Encoding full Unicode as visible 8-bit bytes |
The ASCII Converter's defining property is its bounded input: anything outside 0 to 127 is rejected. The other tools in this comparison work with UTF-8, which can represent every Unicode character but uses one to four bytes per code point. If the goal is a guaranteed round-trip mapping between ASCII text and decimal numbers, the strict converter is the correct choice. If you need the same characters expressed in hexadecimal or binary, use a UTF-8-aware tool and remember that the result is no longer plain 7-bit ASCII.
Where 7-Bit ASCII Stops Being Enough
ASCII was designed for English-language technical text and was never extended in a single, compatible way. The phrase "extended ASCII" usually refers to one of several incompatible 8-bit code pages such as Windows-1252 or ISO-8859-1, which use values 128 to 255 but assign different characters in each page. A strict ASCII converter deliberately does not pick one of these for you, because doing so would silently change the meaning of your data.
When your input contains accented letters, non-Latin scripts, or emoji, those characters live in Unicode code points above 127. To encode them faithfully, use a converter that names its target encoding — for example, a UTF-8 encoder for the modern web, or a specific legacy code page when you genuinely need Windows-1252 or ISO-8859-1 output. The ASCII Converter's role in that workflow is to confirm which parts of your text really are 7-bit ASCII, and to give you a clean decimal representation of exactly that portion.
If you're weighing options, HTML Escape Explained: From Characters to Entities covers this in detail.