Article — Letters to Numbers Converter
Letters to Numbers Converter: A1Z26, ASCII, and Phone Keypad
- What the letters to numbers converter does
- A1Z26: the classic letter to number cipher
- ASCII letter to number mapping
- Phone keypad letter to number code
- Decoding numbers back to letters
- Real-world uses of letter number codes
- Common letter to number conversion mistakes
- Why letter number ciphers are not secure
A letters to numbers converter maps each character of text to a numeric code. The three standard schemes are A1Z26 (A=1 through Z=26), ASCII decimal (A=65, a=97, space=32, defined by RFC 20), and the phone keypad mapping in ITU-T Recommendation E.161 (2=ABC, 3=DEF, on through 9=WXYZ). All three are public, deterministic, and zero-security; they are used in puzzles, escape rooms, vanity phone numbers, and as teaching ciphers.
The converter above accepts free text on the left and shows the numeric output plus a cell-by-cell mapping below. Toggle the direction to decode numbers back into letters when you encounter a coded puzzle. Switch between separators (dash, space, comma, none) to control output formatting.
What the letters to numbers converter does
This letters to numbers converter implements three substitution schemes side by side. A1Z26 ignores anything outside A-Z and folds case. ASCII passes every character through, preserving case (uppercase A is 65, lowercase a is 97). Phone keypad covers letters only, mapping them to digits 2-9 with key 0 reserved for spaces. The mapping grid below the headline shows each character with its numeric value so you can verify the conversion step by step.
The A1Z26 cipher first appeared in nineteenth-century recreational math books, but the underlying idea, that letters can be numbered for cryptographic operations, traces to Polybius (c. 200 BCE) and his 5x5 letter grid. The Polybius square gave each letter two-digit row-column coordinates, the direct ancestor of every position-based letter cipher.
A1Z26: the classic letter to number cipher
A1Z26 is the simplest letter to number cipher. Each letter is replaced by its position in the English alphabet. A becomes 1, B becomes 2, M becomes 13, Z becomes 26. The mapping is one-to-one across the 26 uppercase letters, so encoding and decoding are mirror operations. Implementations typically fold case and strip everything else, producing a sequence of integers between 1 and 26.
The arithmetic is easy in your head once you learn three milestones: E=5, J=10, O=15, T=20, Y=25. From any anchor you can step forward or backward to find the rest. HELLO encodes as 8-5-12-12-15. Without a separator the same string would collapse to 851212-15, which a decoder cannot disambiguate. Always use separators when sharing A1Z26 output.
ASCII letter to number mapping
ASCII (American Standard Code for Information Interchange) was published as ANSI X3.4 in 1963 and codified in RFC 20 in 1969. It assigns a 7-bit number from 0 to 127 to every character a teletype could print. Uppercase letters occupy 65 through 90; lowercase letters 97 through 122; digits 48 through 57; common punctuation fills the gaps. The space character is 32. NIST publishes the canonical table.
ASCII covers 128 characters. Modern systems use UTF-8, which extends ASCII (the first 128 code points match exactly) but represents characters beyond ASCII as multi-byte sequences. Accented characters like é or ñ encode to two bytes in UTF-8, not a single ASCII number. If a puzzle expects a single number per character and the source text contains accents, the cipher is probably A1Z26 with accents stripped, not raw ASCII.
Phone keypad letter to number code
The phone keypad letter to number mapping is defined in ITU-T Recommendation E.161, last revised in 2001. Key 2 carries ABC, 3 has DEF, 4 holds GHI, 5 is JKL, 6 is MNO, 7 takes PQRS (four letters), 8 carries TUV, and 9 holds WXYZ (four letters). Keys 0 and 1 do not carry letters in the standard, although some carriers add space to 0.
The mapping powers vanity phone numbers like 1-800-FLOWERS (1-800-356-9377) and the old T9 predictive-text input used on feature phones before touchscreens. T9 disambiguated letter sequences from key presses by checking a dictionary; without context, the digit string 4357 could be GELS, HELP, IDLP, or any combination of letters from those keys.
Decoding numbers back to letters
The converter handles A1Z26 decoding when you flip the direction toggle. Input numbers separated by dashes or single spaces are treated as letters; words are separated by slashes or double spaces. 8-5-12-12-15/23-15-18-12-4 decodes to HELLO WORLD. Decoding ASCII works the same way by table lookup; phone keypad decoding is ambiguous (key 2 could be A, B, or C) and needs a dictionary or human inference.
If a puzzle gives you numbers above 26, A1Z26 is not the right cipher. Numbers from 65 to 90 hint at uppercase ASCII; 97 to 122 hint at lowercase. Numbers in the 0 to 99 range with frequent values like 32 (space) and 46 (period) are almost certainly ASCII.
Real-world uses of letter number codes
Letter to number conversion shows up in more places than you might expect. Escape room designers use A1Z26 because solvers can decode it without a key in under a minute. Geocaching puzzles hide coordinates as numeric ciphers that route players to a final waypoint. The Bible code and gematria traditions in Jewish and Greek scripture treat letter sums as meaningful. Vanity phone numbers and the toll-free SMS shortcodes used by US carriers translate words to digits using E.161.
- 1-800-FLOWERS = 1-800-356-9377 (E.161 mapping)
- HELLO = 8-5-12-12-15 (A1Z26)
- A1Z26 range = 1 to 26, plus optional 0 for space
- ASCII range = 0 to 127, with printable characters in 32-126
- RFC 20 codified ASCII for network use in October 1969
- Polybius square (c. 200 BCE) is the ancestor of position-based ciphers
- T9 dictionary shipped on Nokia 3210 (1999), enabling rapid SMS
- Lowercase offset = uppercase + 32 in ASCII
Common letter to number conversion mistakes
The most frequent mistake is omitting separators in A1Z26 output. Without them, 11-1 (KA) is identical to 1-11 (AK) and 111 (AAA). Always use dashes, commas, or spaces between numbers. The second common mistake is mixing schemes mid-message, where some characters encode as A1Z26 and others as ASCII. The third is treating phone keypad as reversible; without a dictionary, the digit sequence cannot be unambiguously decoded.
A subtle issue is the handling of non-English letters. Polish, German, and Czech texts use diacritics like ą, ö, č that do not appear in A1Z26 or the phone keypad mapping. For ASCII, those characters encode as multi-byte UTF-8 sequences, not single numbers. Most puzzle conventions either strip the diacritic before encoding (ą becomes a, č becomes c) or fall back to Unicode code points.
Why letter number ciphers are not secure
A1Z26 has no key, so anyone who recognises the cipher decodes it in seconds. ASCII is a transmission code, not a cipher at all. The phone keypad mapping is published in an ITU standard. All three are visible to frequency analysis: the letter E shows up about 12% of the time in English, so the number 5 dominates A1Z26 ciphertext just as E dominates the plaintext. None of these schemes should be used for privacy.
For actual cryptographic protection, use AES-256 in GCM mode, ChaCha20-Poly1305, or a vetted signal-protocol messaging app. The letter to number conversion taught here is a starting point for understanding how substitution ciphers work, not a hiding tool. Britannica notes that the move from letter substitution to mathematical cipher operations was the defining shift between classical and modern cryptography.