How to Tap Morse Code: Timing, Knocks & Practice Messages

To tap Morse code, make a quick tap for a dot and press and hold for a dash, about three times as long. Pause for one beat between signals inside a letter, three beats between letters and seven beats between words. Pick a slow, steady beat, such as a quarter of a second, and keep it the same for the whole message.

That works on a touch pad, a phone screen or someone’s hand. On a hard table or a wall there is a catch: a knock is over almost instantly, so it cannot be “held”. Below are four ways around that, plus drills to get your rhythm right.

The method in five steps

1. Choose your beat. One unit of a quarter to a third of a second is comfortable for beginners.
2. Dot: one quick tap, lasting one unit.
3. Dash: one long press, lasting three units. On a hard surface, use one of the long-signal methods below.
4. Pause correctly. One unit between signals in the same letter, three units between letters, seven units between words.
5. Repeat the message after a long pause so the receiver can confirm what they heard or felt.

For example, the letter -.- is tap, press-and-hold, tap. The word --- -.- is three long presses, a three-unit pause, then K.

Tapping Morse code is not the same as tap code

Search for “tap code” and you will find a different system, the one prisoners used to knock messages through cell walls. It is not Morse code, and the two are often mixed up.

Tap code is based on a 5 by 5 letter grid, known as a Polybius square. Each letter is sent as two groups of plain knocks: the row number, a short pause, then the column number. There are only 25 cells, so C and K share one.

To send HI in tap code, you knock 2 then 3 for H, and 2 then 4 for I. To send HI in Morse code, you send .... ..: four dots, a letter gap, then two dots.

According to the National Veterans Memorial and Museum, American prisoners of war in Hanoi were introduced to the tap code in June 1965 by four fellow prisoners, including Captain Carlyle “Smitty” Harris. Tap code suits that setting because every knock is identical: nothing depends on how long a signal lasts.

Taps meant for a Morse translator, or for anyone who reads Morse, must use Morse, which is what the rest of this page covers.

The short signal: a dot

A dot is the easy part. Tap once, lightly and cleanly, and lift your finger straight away. The contact should last one unit and no longer.

Use the same finger every time and let the tap come from the finger, not the whole hand. A relaxed, small movement is faster, quieter and easier to repeat evenly than a big knock.

Letters made only of dots are good for calibrating your dot. . is one dot, .. is two, ... is three and .... is four. Tap each one slowly and listen for evenly spaced taps.

The long signal: four ways to make a dash

The International Telecommunication Union’s Morse code recommendation, ITU-R M.1677-1, defines a dash as equal to three dots. With sound or light that is simple: the tone or beam stays on three times as long. A fingertip needs a way to make that length noticeable.

1. Press and hold

Keep your fingertip in contact for three units, then lift. This is the closest match to real Morse timing, and it is how tap-to-type tools, including our tap pad further down, read your input.

It works best wherever the receiver can feel or detect contact: a touchscreen, a switch, a partner’s palm or forearm. On a hard surface a held press makes no sound, so a listener in another room only hears the start.

2. Drag or scrape

Tap down and slide the fingertip or a fingernail along the surface for three units. The scraping sound lasts as long as the dash, so a listener can hear the difference between a knock and a scrape.

This is the best option for an audible signal on a table or a door. The trade-off is that it is slower and noisier, and a rough surface makes a louder scrape than a smooth one.

3. Click and release

A telegraph sounder, the device operators listened to on landline telegraph circuits, had the same problem. As Wikipedia’s article on the telegraph sounder explains, it gave a “click” when current started and a “clack” when it stopped, and operators read each signal from the time between the two sounds.

You can copy that with two sounds per signal: a firm tap to start, and a lighter tap (or the sound of lifting a pen off the table) to end. A dot is click-clack close together; a dash leaves three units between them. It is accurate but takes practice, because a careless listener hears two dots.

4. Two different sounds or two hands

Instead of using length at all, make dots and dashes different sounds: a fingertip tap for a dot and a knuckle knock or a flat-hand thump for a dash. Or tap dots with one hand and dashes with the other.

This removes the hardest timing problem, and it is the same idea behind two-button Morse input used in accessibility technology. You still need clean pauses between letters and words, and both people must agree on the convention before they start.

Why plain knocks are ambiguous

If you only knock, with every knock the same length, the receiver has one clue left: the time from one knock to the next. That interval is the signal’s own length plus the pause after it. Work it through with the standard ratios and you find a problem.

A dash inside a letter and a dot followed by a letter gap both give 4 units to the next knock. So “knock, 4 units, knock” could be --, -., . - or . .. The last signal of any message also has no following knock, so the receiver cannot tell whether .. or .- was sent.

A receiver who knows what to expect can often guess from context. For anything that matters, use one of the four long-signal methods above rather than bare knocks.

Timing for hand tapping

Morse timing is a set of ratios, not fixed times. The general rules are on our homepage’s timing and spacing section; here they are at speeds a hand can manage.

Start at 300 ms if you are new. Speed comes later; even spacing matters far more to the person receiving.

The demonstration below pulses a short message at 6 words per minute and names each element as it plays, with its length in units and milliseconds. Watch it once, then tap along on the table in front of you. You can lower the speed to 4 wpm.

A useful way to keep time is to count silently in units. For a dash, think “one-two-three” while your finger stays down. For a letter gap, think “one-two-three” with your finger up. For a word gap, count to seven.

Letter gaps and word gaps

Gaps carry as much meaning as the taps. A missing letter gap joins two letters into a different one, and a missing word gap runs words together.

Two examples show how little it takes:

• . - (E, then T) sent without the letter gap becomes .-.
• - . (T, then E) sent without the letter gap becomes -..

The letter gap is three units, which is the same length as a dash. If you are pressing and holding, a good self-check is that your finger stays up for about as long as it stays down on a dash. The word gap is seven units: long enough to feel slightly awkward the first few times.

Beginners tend to make gaps too short, because a pause feels like “doing nothing”. If a receiver keeps misreading your letters, lengthen the gaps before you change anything else.

Where and how to tap

A few practical points apply everywhere:

• Keep pressure consistent. A harder tap is not a longer tap, and the receiver may read loudness as a different signal.
• Agree on the method first. Before you send anything, tap one test letter, such as K, and check the receiver reads it correctly.

Tapping on someone’s hand is a common way to share a short private message, such as a phrase you both know. Our guide to I love you in Morse code walks through that phrase tap by tap.

Practise on the tap pad

The pad below is a hold-to-send practice area. Press and hold it with a mouse, a finger or the Space bar. It measures each press against the speed you choose, shows its length in units, and decodes your rhythm back into letters, so you can see whether your dashes really are three times your dots and whether your gaps are long enough.

Start at 5 or 8 wpm. If letters come out wrong, read the press lengths it reports: dashes under two units are being read as dots, and gaps under three units are joining your letters.

Practice letters

Work through these sets in order. Tap each letter five times with a full letter gap between repeats, then check it on the pad.

Then send the pairs that differ only by the gap: E T and A, T E and N. If the pad reads A when you meant E T, your letter gap is too short.

Practice messages

Short, familiar messages show instantly when the result is wrong. Send each one twice with a word gap between repeats.

SOS appears here only as a rhythm exercise. As a distress signal it is usually sent as one unbroken group with no letter gaps; our prosign section explains the difference.

When the list feels easy, have a partner call out a random short word and tap it immediately, or practise listening instead of sending with our Morse code practice drills.

Common mistakes

• Dashes that are too short. A dash under two units reads as a dot on our tap pad, and a listener hears it the same way. Count “one-two-three” while holding.
• Letter gaps that are too short. E and T turn into A, T and E turn into N. When in doubt, pause longer.
• Speeding up mid-message. Confidence makes people rush the second half. Keep the beat you started with.
• Relying on bare knocks. As the knock table shows, M, N, E T and E E can sound identical. Use a long-signal method.
• Tapping hard instead of long. Force does not make a signal longer. Keep pressure the same and change only the duration.

Tapping, keys and other ways to send

Tapping is manual sending in its simplest form: your finger forms every element, as it does on a straight key. For how operators send faster, see our comparison of the straight key, paddle and bug.

When the receiver can see you but not hear or feel you, light is often clearer than taps. The same 1:3 and 1:3:7 ratios apply; our guide to sending Morse code with a flashlight covers aiming, distance and pacing. If you just want a phone to buzz a message for you, the translator’s Vibrate output does that automatically.

Accessibility: real uses and honest limits

Morse can be a practical input method for some people who cannot use a standard keyboard, because it needs only two signals. In 2018 Google added a Morse code keyboard to Gboard, developed with Tania Finlayson, who communicates in Morse. Google’s announcement describes separate dot and dash inputs and support for external switches, so a person with limited mobility can operate a device.

That example uses two inputs rather than timed presses, which sidesteps the long-signal problem on this page entirely. It also shows where finger tapping has limits:

• Timing takes motor control. Holding a press for three units and pausing for seven is hard for anyone with tremor, fatigue or limited hand movement. Two separate switches, or a device that sets the timing for you, may suit better.
• Both people need to know the code. A tapped message is only useful if the receiver can decode it at the speed you send.
• Tapping is slow. At a comfortable hand pace, even a short sentence takes tens of seconds.
• It is not a medical or emergency system. Tapped Morse is a skill and a backup, not a guaranteed way to be understood. Anyone choosing a communication method for daily or assistive use should do so with a qualified specialist.

For private messages, learning and games, tapping works well: start slow, make dashes truly long, and respect the gaps.