T9 Multi-Tap Encoder
Encode text as old-school multi-tap phone keypad digits.
Overview
Encode text into the digit sequences you'd press on an old-school phone keypad to type each letter using multi-tap input. Pressing 2 once gives A, twice gives B, three times gives C; pause to advance to the next letter on the same key. The output captures every keypress, separated by spaces or pauses.
Retro tech nostalgists, ARG puzzle designers using number-stream clues, mobile UX historians demonstrating pre-smartphone input, and anyone setting up a phone-themed escape room all reach for it. It's a fun stop on coding challenges that ask you to map between letters and digits.
How it works
The classic mobile keypad layout: 2 (ABC), 3 (DEF), 4 (GHI), 5 (JKL), 6 (MNO), 7 (PQRS), 8 (TUV), 9 (WXYZ). The number 0 is space; 1 is punctuation. To type a letter, press its key the number of times equal to its position on the key: A is one press of 2 ("2"), B is two presses ("22"), C is three ("222").
When two letters in a row share the same key (like "C" then "A"), you have to pause between them — usually marked with a space or a hyphen — so the encoder doesn't read "2222" as a single ambiguous sequence.
Worked example: "CAB" encodes to "222 2 22" — C is 222, pause, A is 2, pause, B is 22.
Examples
Input: HELLO
Output: 44 33 555 555 666
Input: CAT
Output: 222 2 8
Input: HI MOM
Output: 44 444 0 6 666 6
FAQ
What about predictive T9?
True T9 (Text on 9 keys) used a dictionary to disambiguate. Press 4-3-5-5-6 once each and the phone guessed "HELLO". This tool encodes the literal multi-tap sequence, not the predictive shorthand.
Why are the separators important?
Without pauses between same-key letters, "AB" and "C" both look like "22..." sequences. The pause tells the keypad you're done with one letter and starting another.
Does it support lowercase?
Multi-tap traditionally cycled through lowercase letters before uppercase. The tool defaults to the simpler uppercase-only encoding; a toggle adds extra presses for lowercase if needed.