TL;DR / Summary: Tap code turns each letter into two knock groups—row taps, a pause, then column taps—on a 5×5 Polybius square. Type your message at tap-code.org, read the dot or number output, and practice the rhythm until pairs feel automatic.
What you need before your first encode
Tap code is deliberately low-tech. You do not need radio gear, special fonts, or a printed chart once you understand the grid. What you do need is a message written in plain Latin letters, a quiet minute to look up coordinates, and a way to verify output before you knock on a wall or tap a desk.
The English standard uses twenty-five cells for twenty-six letters by merging I and J into one position and C and K into another. Numbers and punctuation are usually dropped unless your tool explicitly maps them. For your first session, stick to short words like HELLO or WATER so every character lands on the grid without guesswork.
Open the encoder in a focused browser tab. Mobile works, but a laptop screen makes it easier to compare the live grid with your output while you learn.
Locate each letter on the Polybius square
Imagine a five-by-five table numbered by row and column, both starting at one. Row one holds A through E; row two holds F through J (with I/J sharing the fourth cell of that row in most charts); row three continues K through O (often with C/K merged); row four holds P through T; row five holds U through Z.
To encode H, find it in row two, column three. That becomes two knock groups: two taps (row), pause, three taps (column). To encode E, row one, column five: one tap, pause, five taps. Every letter expands to exactly two groups, which is why tap code is easier to recover in noise than variable-length Morse.
Write the coordinate pairs on paper for your first message before you knock. The physical act of lookup builds memory faster than staring at finished output alone.
Turn coordinates into knocks or numbers
On the homepage tool you can switch between dot display (visual knocks) and numeric display (plain row-column digits). Both represent the same signal. Dots help you practice timing; numbers help you log messages in a notebook or share them in chat without formatting issues.
Each letter is separated from the next by a slightly longer pause than the pause inside the pair. Think of it as short-short … long … short-short. If you merge the inner pause with the outer pause, decoders read extra letters or garbage pairs—timing is half the protocol.
When you read output aloud, say “two, three” for H rather than “twenty-three.” The comma or breath between counts matters more than speed.
Walk through HELLO as a complete example
Take the word HELLO letter by letter:
- H → row 2, column 3 → 2 taps, pause, 3 taps
- E → row 1, column 5 → 1 tap, pause, 5 taps
- L → row 3, column 2 → 3 taps, pause, 2 taps
- L → same pair again
- O → row 3, column 5 → 3 taps, pause, 5 taps
Between letters, extend the pause slightly. Between words, extend it again or insert an agreed “word break” signal—some groups use a double pause, others a distinctive triple tap. Match whatever convention your partner expects.
After encoding, decode the same string back to letters without looking at your notes. If you round-trip successfully, your pauses and counts are probably clean enough for a patient human listener.
Common beginner mistakes and quick fixes
Rushing the inner pause causes pairs like 2-3 and 3-2 to blur into five taps with no structure. Slow down until a partner can write digits as you knock.
Off-by-one rows happen when people count from zero or skip the merged cells. Always use the chart on the tool or a chart you trust; do not mix layouts mid-message.
Trying symbols too early wastes time. Encode letters first; add numbers or punctuation only after your group agrees on extensions.
Long first message hides which letter caused a mistake. Start with three to five letters, confirm, then scale up.
Practice habits that stick
Five minutes daily beats a single hour on weekends. Pick one drill: encode a random word from a book title, decode it, then compare to the source. Log errors by type—wrong row, wrong column, bad pause—so you fix patterns instead of repeating them.
Pair up when possible. One person knocks on a desk while the other writes pairs; swap roles. Distance and a closed door simulate real wall conditions without the stress of a live emergency.
Keep a personal cheat sheet until row-three letters (L, M, N, O) feel instant. Most speed gains come from memorizing the third and fourth rows, not the easy top row.
Test it once more: how to Encode Messages With Tap Code Step by Step
Encoding with tap code is lookup, rhythm, and verification. Find the letter on the Polybius square, knock row then column with a clear inner pause, separate letters with a longer gap, and check your work on tap-code.org before you rely on the message in a drill or classroom demo.
