Standard 7-bit ASCII assigns exactly one decimal number from 0 to 127 to every printable letter, digit, punctuation mark, and control code that early computers agreed to share, and an ASCII code converter cheat sheet maps each of those 128 values to its character in both directions. A printable cheat sheet gives you the static reference (the rows "65 = A", "97 = a", "32 = space") so you can look up a single character without any software. A converter cheat sheet goes further: it lets you paste a whole word, sentence, or block of decimal numbers and produces every code in one pass, with strict validation so you never accidentally treat an extended byte as ASCII. The free ASCII Converter tool fits both roles at once, returning exact decimal values 0 through 127 for any input you paste while flagging the first non-ASCII character instead of silently corrupting your data.
A traditional printed ASCII reference card shows 128 cells, often arranged as four rows of thirty-two characters or eight rows of sixteen, with the decimal, hexadecimal, and sometimes octal value printed next to each glyph. Useful columns include the character itself, its decimal code, and a short label such as "NUL", "LF", or "DEL" for the codes that have no printable shape. The IETF RFC 20 specification that defines the original 7-bit assignments is still the authoritative source, and the Unicode Consortium's C0 Controls and Basic Latin chart cross-references the same values for modern software. When you find those references online, you usually see a small fixed table, which is fine for one-off lookups but slow when you need to convert a paragraph, an entire log line, or a long list of decimal codes back into text. For a deeper decimal-first walkthrough, the How to Convert ASCII to Integer guide covers the same tool with extra worked examples.
Use the ASCII Converter as an interactive cheat sheet
Open the ASCII Converter page and pick a direction first: text-to-codes turns each character of a string into a space-separated decimal integer, while codes-to-text reverses the process. Both directions run entirely in the current browser tab, so the text you paste never leaves your machine and there is no upload step, no account, and no server round-trip. The accepted range is exactly decimal 0 through 127, which covers every control code, punctuation mark, digit, uppercase and lowercase Latin letter, and the DEL character. Eight reference fixtures anchor the lower boundary (0), TAB (9), line feed (10), space (32), digit zero (48), uppercase A (65), lowercase a (97), and the upper boundary (127), so a wrong assignment cannot slip through the validation logic.
Unlike the static ASCII Table reference page, the converter enforces strict two-way conversion between standard 7-bit ASCII and decimal code values without offering an extended-code-page fallback. It also differs from a Text to Hex or Text to Binary converter, which encode UTF-8 bytes in hexadecimal or binary rather than treating the input as plain 7-bit ASCII in the first place. Choosing the right tool for the right job matters: if your input contains accents, emoji, or any character above 127, ASCII Converter will refuse the work and you should switch to a UTF-8 converter that names its encoding explicitly.
Convert text to decimal ASCII codes
Follow these steps to turn a string into the matching decimal codes:
- Choose the text-to-codes direction on the ASCII Converter page.
- Paste or type the text you want to encode into the input area. The limit is 100,000 UTF-16 code units.
- Select Convert ASCII and review the result, which appears as space-separated decimal integers such as 72 105 33 for the string "Hi!".
- If a non-ASCII character appears, the tool stops at that character and reports its position rather than guessing how to encode it as UTF-8 or a legacy code page.
- Copy the decimal output to your clipboard for use in code, documentation, or a network protocol.
For a quick worked example, take the three-character string "Hi!". The first character H is decimal 72 by RFC 20, the second character i is decimal 105, and the exclamation point is decimal 33. The tool produces exactly 72 105 33 in one step, with no manual lookup required, so even a short phrase is faster to convert than to read off a static table.
Decode decimal codes back to text
The reverse direction is just as useful when you have a block of codes from a spec, a textbook, or a log file. Follow these steps:
- Switch the ASCII Converter to codes-to-text mode.
- Enter the decimal values as integers in the 0 to 127 range, separated by spaces, commas, or line breaks; the tokenizer accepts any combination of those separators.
- Select Convert ASCII. The decoder requires unsigned, one-to-three-digit decimal tokens and rejects signed numbers, fractions, hexadecimal prefixes such as 0x41, and empty tokens.
- Review the rebuilt text in the output area. The decoding limit is 50,000 codes per paste, which is enough for almost any single document or table.
- Copy the result if it looks correct. If part of the output looks invisible or behaves oddly in the destination application, see the control-character note below.
Because the tool handles a complete text sequence as decimal 7-bit values and fails closed when the input is not ASCII, you always know whether the conversion succeeded. There is no ambiguous "best effort" pass that hides errors, and there is no silent reinterpretation of bytes 128 through 255 as Windows-1252 or ISO-8859-1. That fail-closed property is the main reason a strict converter beats a permissive one for protocol work, forensic analysis, and teaching purposes.
Quick ASCII decimal reference table
The table below shows a handful of the most-asked values, taken directly from the RFC 20 assignments and cross-checked against the Unicode Basic Latin chart. For the full 0-127 range, paste text into the ASCII Converter instead of looking up each code manually.
| Decimal | Hex | Char | Category |
|---|---|---|---|
| 0 | 00 | NUL | Control |
| 9 | 09 | TAB | Control |
| 10 | 0A | LF | Control |
| 13 | 0D | CR | Control |
| 32 | 20 | (space) | Whitespace |
| 48 | 30 | 0 | Digit |
| 65 | 41 | A | Uppercase letter |
| 97 | 61 | a | Lowercase letter |
| 127 | 7F | DEL | Control |
Notice how the digit characters start at 48, the uppercase Latin letters run from 65 through 90, and the lowercase Latin letters run from 97 through 122. That ordering is what lets ASCII sort strings naturally with a simple byte comparison, which is one reason the code survived long after larger character sets became available.
Why values 128 through 255 are deliberately excluded
Standard ASCII is a 7-bit code, which means each value fits in seven binary digits and the maximum is 127 in decimal or 0x7F in hex. Bytes 128 through 255 belong to a different category that people loosely call "extended ASCII", but that phrase hides an important problem: there is no single definition. Windows-1252, ISO-8859-1, and several other code pages each assign 128 to 255 to different characters, and choosing the wrong one turns a text file into mojibake the moment a non-ASCII byte appears. The ASCII Converter rejects any input character above 127 and any decoded integer above 127 rather than silently picking a code page, which is exactly the behavior you want when correctness matters more than convenience. For Unicode code points, UTF-8 byte streams, or legacy single-byte encodings, switch to a converter that explicitly names the required encoding; the UTF-8 Encoder / Decoder is the right next step when the file contains accented letters or emoji.
Control characters: when decimals look invisible
A common surprise when decoding decimal codes is that codes 0 through 31 and code 127 represent control characters rather than printable glyphs, so part of the output may look blank in the textarea. Decimal 9 inserts a tab, decimal 10 inserts a line feed, decimal 13 inserts a carriage return, decimal 0 is NUL, and decimal 127 is DEL. Each of those codes can trigger application-specific behavior when pasted into another program: a tab may move the cursor to the next field in a form, a line feed may split the value into two rows in a spreadsheet, and a NUL byte can truncate the string inside a C program that uses a C-style string library. If you need to see or preserve every byte exactly, copy the decimal output instead of the decoded text, or paste the decoded result into a byte-aware editor that renders controls visibly. The tool does not warn you about every control character by default, because most uses treat tabs and line breaks as helpful rather than dangerous, but the validation always reports the position of any character that falls outside the 7-bit range.
Limits and validation you can rely on
Two practical limits govern how much text you can convert in one paste. Encoding accepts up to 100,000 UTF-16 code units, and decoding accepts up to 50,000 decimal tokens; both numbers are large enough for a novel-length document but small enough to keep the round-trip instant. Validation is strict on both sides: encoding rejects the first character outside the 0 to 127 range and reports its position so you can fix the input, and decoding rejects signed numbers, fractions, hexadecimal prefixes, empty tokens, and out-of-range values without trying to interpret them. There is no fallback to an extended code page, no silent UTF-8 reinterpretation, and no upload of your text to a remote server. Combining those properties is what makes the converter safe to use on log lines, protocol payloads, and classroom exercises alike, because every byte in the output means exactly one thing.