Phone keypad multi-tap encoder
HELLO becomes 44 33 555 555 666 on a classic phone keypad: press 4 twice for H, 3 twice for E and 5 three times for each L. Turn text into key presses or read digit runs back as letters. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Text
- HELLO
- Result
- 44 33 555 555 666
- Calculation mode
- Encode
- Quantity
- 5
- Scheme
- itu_e161_multitap
Before touchscreens and predictive T9 dictionaries, every SMS and contact name was typed on a twelve-key pad by multi-tap: press 2 once for A, twice for B, three times for C, wait or switch keys for the next letter, and so on through 9 for W X Y Z. That ITU E.161 layout still appears in feature phones, IVR menus, retro puzzles, museum demos, and programming exercises that ask students to map letters to digit runs. This capability encodes plain text into those classic press sequences and decodes space-separated digit groups back into characters, failing loud on invalid runs instead of guessing.
Encode text to multi-tap key sequences
Each Latin letter A through Z maps to a run of the same digit: A is a single 2, B is 22, C is 222, D is 3, E is 33, and so on through Z as 9999 on key 9, matching the familiar 2=ABC, 3=DEF, 4=GHI, 5=JKL, 6=MNO, 7=PQRS, 8=TUV, 9=WXYZ layout. Spaces encode as a single 0 so word boundaries survive the round trip.
Digits zero through nine encode with the wrap-around convention used on many handsets: after the letter cycle on that key, one more press yields the digit itself, so the character 2 becomes 2222 and the character 7 becomes 77777. Lowercase letters are folded to uppercase in the token list so HELLO and hello produce the same result string. Empty text with no characters also fails validation.
Identical inputs always produce identical outputs because the path is pure table lookup with no network, no random salt, and no wall clock.
Decode key presses and reject invalid sequences
Set mode to decode and put space-separated multi-tap groups in text, where each group is one digit repeated as many times as you would have pressed that key for one character. Matching is strict: 22 decodes to B, 777 to R, 0 to a space, and 9999 to Z. Because every character is its own whitespace-delimited token, consecutive letters on the same key need no pause timer—A followed by B is simply 2 22 rather than an ambiguous 222.
Empty decode input fails the same way. Prefer this capability when search intent is phone keypad multi-tap encoder, old mobile SMS key presses, 2 ABC texting converter, or multi-tap decode for digit runs; predictive T9 word dictionaries and language-aware completion belong to other tools, not this fixed table.
What you can do with it
Classroom multi-tap worksheets
Teachers encode sample phrases into digit runs for homework, then auto-grade student decode answers and fail loud on invalid key sequences instead of accepting silent typos.
Escape rooms and retro puzzles
Designers print multi-tap sequences as clues and decode player submissions server-side so only the correct press groups unlock the next stage.
FAQ
How do I convert text to phone multi-tap key presses?
The result field returns 44 33 555 555 666 with a tokens list for each character.
How do I decode multi-tap sequences back to letters?
Set mode to decode and put space-separated digit runs in text (for example 44 33 555 555 666). The result field returns the recovered uppercase string.
Does this support T9 predictive text?
No. This tool implements classic multi-tap press counts only, not a T9 dictionary. Each character is encoded or decoded independently.
How are spaces and digits typed in multi-tap?
A space is a single 0, so word breaks survive the round trip. A digit takes one press more than the letters on its key: the character 2 becomes 2222 and the character 7 becomes 77777.
How do I type two letters from the same key, such as A and B?
Write each character as its own group separated by a space: A then B is 2 22. Because the groups are already split, no pause is needed, and a run like 222 always means C.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/enc/phone-multitap \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"HELLO"}'const res = await fetch("https://api.kit.forhosting.com/enc/phone-multitap", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "HELLO"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/enc/phone-multitap",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "HELLO"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/enc/phone-multitap", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"HELLO"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"HELLO"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/enc/phone-multitap", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "HELLO"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "enc.phone_multitap",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
The mapping is a fixed deterministic table—no language model, no network call, and no clock—so the same input always returns the same JSON for tests, SDKs, and browser widgets. Use the free on-device tool for one-off conversions; the prepaid API charges $0.002 per successful item when backends need the identical contract.
Encode text to multi-tap key sequences
Send a JSON body with the required string field text set to the message you want to spell on a classic phone keypad, and leave mode at its default encode or set mode to encode explicitly. Characters outside letters, digits, and spaces—punctuation, emoji, or other scripts—raise invalid_input naming the character and index, so a typo does not silently disappear from a puzzle answer or SMS recreation. Aliases input, value, and s are accepted for the text field; direction, op, and action may stand in for mode. The response includes result as space-separated digit runs (for example HELLO becomes 44 33 555 555 666), tokens as an array of char and code pairs, count as the number of mapped characters, mode equal to encode, and scheme equal to itu_e161_multitap.
Decode key presses and reject invalid sequences
Any token that mixes different digits, uses a non-digit character, exceeds the maximum presses for that key, or is empty after splitting raises invalid_input with an explicit invalid key sequence message naming the bad token—exactly the contract quiz graders and puzzle checkers need when a wrong sequence must not invent a letter. On success the response returns result as the recovered uppercase string (with spaces preserved from 0), tokens pairing each character with its press code, count, mode decode, and scheme itu_e161_multitap. Validation failures are not charged on the prepaid API, so operators can probe bad pastes safely.
API usage, pricing, workflows, and practical limits
Call the free in-browser phone keypad multi-tap encoder for classroom demos, museum interactives, retro-game localization checks, and one-off SMS recreations without installing a spreadsheet of key maps. A typical workflow encodes a short plaintext clue for an escape-room prop, prints the digit runs, then decodes player submissions and asserts that result matches the original letters. Authors shipping SDKs can map the tokens array into a table of character and press-code columns for UI copy buttons, while mode and scheme labels make OpenAPI examples self-explanatory for readers comparing multi-tap layouts to NATO spelling or other encoders. Use the prepaid KIT API when a puzzle backend, onboarding bot, content pipeline, or SDK needs the same encode or decode step under balance at $0.002 per successful item; failed validation never consumes balance after the engine rejects the request. Pair this endpoint with uppercase or transliteration tools when identifiers arrive in mixed scripts, but keep the steps separate so each landing page matches a single search intent.
Integration use cases
CI fixtures for keypad UIs
Feature-phone or IVR simulators pin encode and decode goldens—including an invalid-sequence error—so keypad table changes break tests immediately.
Technical questions
What happens on an invalid key sequence?
Decode raises invalid_input naming the bad group—mixed keys, non-digits, or too many presses. Validation failures are not charged on the prepaid API.
Is the phone multi-tap encoder free?
The browser widget runs free on your device. API calls use prepaid KIT balance at $0.002 per successful item.