An ASCII chart cheat sheet is a compact reference of all 128 standard 7-bit ASCII codes, each shown in decimal, hexadecimal, octal, and seven-bit binary alongside its character or control abbreviation. Standard ASCII, defined in the 1960s and still embedded inside every modern Unicode text file, spans decimal positions 0 through 127 and never more. A useful cheat sheet preserves that boundary, displays the same code in four radixes side by side, and labels non-printing positions with their RFC 20 abbreviations (NUL, HT, LF, CR, DEL, and so on) instead of leaving cells empty. The four notations matter because source code, network traces, command-line tools, and documentation each lean on a different convention: C-style 0x41 for hexadecimal, Python's 0o101 for octal, and 0b1000001 for binary are all the same capital letter A. Without a side-by-side view, switching between notations slows every debugging, parsing, or encoding task.
What belongs in a usable ASCII chart cheat sheet
A cheat sheet earns its name by being fast to skim and complete enough to answer any 7-bit lookup question. Six elements separate a serious reference from a decorative table:
- All 128 positions. Every entry from decimal 0 through decimal 127, in numerical order. Anything shorter is a sampler, not a cheat sheet.
- Four radixes on the same row. Decimal, two-digit hexadecimal, three-digit octal, and seven-digit binary. Fixed-width prefixes (0x, 0o, 0b) make the notation explicit.
- Visible glyph or control abbreviation. Printable characters show the actual symbol; control positions 0 through 31 use RFC 20 abbreviations such as NUL, HT, LF, and CR; decimal 127 shows DEL.
- A descriptive name. Names follow the Unicode Basic Latin chart for graphic characters and the RFC 20 control table for the rest, so the same row reads consistently across references.
- A category tag. Controls, Space, Punctuation, Digits, Uppercase, Lowercase, or Delete. A category column lets you isolate one slice without scrolling the full table.
- A copy mechanism. Every row should be exportable as a complete record (display value, name, and all four numbers) for pasting into code comments, bug reports, or teaching notes.
If any of those elements is missing, the reference forces readers to convert between notations by hand or guess the radix of a printed number.
The four notations side by side
The cheat sheet's core job is to make the four notations equivalent at a glance. The table below shows how representative rows should appear, with capital A used as a worked conversion example.
| Glyph | Name | Dec | Hex | Oct | Binary | Category |
|---|---|---|---|---|---|---|
| (none) | NUL | 0 | 0x00 | 0o000 | 0b0000000 | Control |
| (none) | HT | 9 | 0x09 | 0o011 | 0b0001001 | Control |
| (none) | LF | 10 | 0x0A | 0o012 | 0b0001010 | Control |
| SP | Space | 32 | 0x20 | 0o040 | 0b0100000 | Space |
| ! | Exclamation Mark | 33 | 0x21 | 0o041 | 0b0100001 | Punctuation |
| 0 | Digit Zero | 48 | 0x30 | 0o060 | 0b0110000 | Digits |
| A | Latin Capital Letter A | 65 | 0x41 | 0o101 | 0b1000001 | Uppercase |
| a | Latin Small Letter A | 97 | 0x61 | 0o141 | 0b1100001 | Lowercase |
| (none) | DEL | 127 | 0x7F | 0o177 | 0b1111111 | Delete |
Worked conversion for capital A (decimal 65):
- Divide 65 by 16: quotient 4, remainder 1, so hexadecimal is 0x41.
- Divide 65 by 8 three times: 65 ÷ 8 = 8 remainder 1; 8 ÷ 8 = 1 remainder 0; 1 ÷ 8 = 0 remainder 1, reading remainders bottom-to-top gives octal 0o101.
- Express 65 as a sum of powers of two: 64 + 1 = 2⁶ + 2⁰, giving seven-digit binary 0b1000001.
Three notations, one character. That equivalence is what a cheat sheet makes visible without further arithmetic.
Using the ASCII Table tool as a printable cheat sheet
The ASCII Table is built around the same six elements: 128 rows, four radixes per row, control abbreviations, names, category tags, and a per-row Copy button that writes the complete record to the clipboard. Here is the shortest path from search to pasted row.
- Open the ASCII Table in your browser and review the full grid of 128 entries, sorted from decimal 0 to decimal 127.
- Type in the search box when you know what you are looking for. Plain digits are read as decimal (so 65 returns capital A), while 0x41, 0o101, and 0b1000001 find the same row in hexadecimal, octal, and binary. You can also search by control abbreviation (LF), name (Line Feed), category (Digits), or character literal (char:space, char:0).
- Pick a category from the filter when you want to isolate a slice: Controls, Space, Punctuation, Digits, Uppercase, Lowercase, or Delete. Every match stays visible; the tool never silently truncates a long result set.
- Read the four radixes on the matched row, confirm the displayed character or abbreviation, then choose Copy on that row to place the full record (display value, name, decimal, hex, octal, binary) on your clipboard for use in code comments, protocol notes, or teaching material.
If the browser denies clipboard access, the page reports the failure instead of pretending the copy succeeded, and changing the search or filter clears that earlier status. Every step runs locally, so search terms and copied rows are not sent to any external service.
ASCII cheat sheet vs extended ASCII tables
A frequent source of confusion is the byte range above decimal 127. Standard ASCII stops at 127 on purpose, and any cheat sheet that mixes in "extended ASCII" is hiding an important ambiguity. The table below summarises where each code range actually comes from.
| Range | Defined by | Glyphs covered | Safe to call ASCII? |
|---|---|---|---|
| 0–127 | ASCII (RFC 20, ECMA-6) | English punctuation, digits 0–9, Latin letters A–Z and a–z, Space, 32 control abbreviations, plus DEL (decimal 127) in its own Delete category | Yes — this is standard ASCII |
| 128–159 | Various single-byte extensions | Punctuation, accented letters, half-width katakana | No — interpretation depends on the encoding |
| 160–255 | ISO-8859-1, Windows-1252, CP437, others | Accented Latin, currency signs, box-drawing characters | No — different code pages disagree |
The byte alone does not identify the character; the encoding does. A cheat sheet that pretends every byte from 0 to 255 is "extended ASCII" masks this. A correct ASCII cheat sheet stops at 127, names the underlying standards, and tells you to confirm the encoding before decoding any byte above that boundary.
Standards behind every line of the table
Every row of a trustworthy ASCII cheat sheet is anchored in a published standard. Three sources matter in practice:
- IETF RFC 20 ("ASCII format for Network Interchange") defines the 128-code table, the control abbreviations (NUL, HT, LF, CR, DEL, and so on), and the strict sense in which DEL is not a control character. RFC 20 is the reason non-printing positions use abbreviations rather than glyphs.
- ECMA-6 confirms the 7-bit, 128-character scope of the standard, which is the technical justification for stopping the table at decimal 127.
- The Unicode Basic Latin code chart assigns the canonical names used for graphic characters (for example, "Latin Capital Letter A" for decimal 65). The Unicode names agree with the RFC 20 code positions, so the same row reads identically in either source.
These three standards are what make a cheat sheet reproducible: decimal 65 is capital A because RFC 20 says so, the name is "Latin Capital Letter A" because Unicode says so, and the binary form 0b1000001 is fixed because ASCII is exactly seven bits wide. For practical lookup, pair the cheat sheet with the ASCII Table so you can search by anything you happen to remember — name, abbreviation, decimal, prefixed radix, or char:value — and copy the matched row without leaving the browser. For developers who apply these codes inside a specific language, the How to Use ASCII Code for Programming and Data Tasks guide walks through real-world conversions in C, JavaScript, Python, and shell contexts, where the same character often needs to be moved between a string, an integer, and a raw byte.