Learn Morse code the way it sticks

How to use it

Press Practice session and put your fingers on the keyboard. A character plays; press its key. Miss one and it shows itself, then plays again until you have it. Twenty five characters later you get a score, and at ninety percent the trainer offers the next character. That is the whole loop: ten or fifteen minutes a day of it beats an hour on Sunday, every time.

Why it works this way

This is the Koch method with Farnsworth spacing, the combination behind most operators who learned code in the last thirty years. Characters play at full speed, twenty words per minute, from the very first session, so your ear learns each one as a single rhythm. The gaps between characters are stretched instead, which is where your thinking time lives; that is the effnumber, and squeezing it toward the char number is how speed grows later.

What you will not find here is a dot-dash chart to study. Learning the printed patterns builds a lookup table in your head, and a lookup table caps out around ten words per minute, because every character costs a translation step. People who learn visually usually have to unlearn it. Here the written pattern only ever appears after you answer, as feedback, never as the thing you memorise.

You also start with two characters, K and M, not one and not twenty six. Telling two rhythms apart is the actual skill; a single character teaches nothing, and the full alphabet at once teaches panic. One new character at a time, each earned at ninety percent, is the fastest path that actually arrives.

The path

Weeks one and two: copy sessions, daily, short. The first few characters feel slow; around six or eight the pace picks up because your ear has learned how to learn them. Everyone plateaus somewhere, often when the numbers arrive; the trainer weights your weak characters heavier automatically, so plateaus grind through on their own.

The middle: mix in groups, which grow from two characters to five as you hold accuracy. This is the bridge from hearing characters to copying, and it is where the skill starts to feel real.

The payoff: the qso mode plays complete on-air exchanges, ragchew and contest style, with fresh callsigns every time. Copy a hundred of those and your first real contact is a rerun of something you have already done. The text mode adds plain-language endurance, and stats shows your streak, your trend, and exactly which characters still masquerade as which.

Honest answers

How long does it take? With daily ten-minute sessions, most people hold a slow QSO in two to three months. It is a skill like swimming: consistency beats intensity, and missing a week costs more than it seems.

What speed should I set? Leave char at twenty. If sessions feel impossible, lower eff, never char: more thinking room between characters, same rhythms. Raising eff back up later is how you get fast.

I already know some code visually. Run the sessions anyway at full character speed; the counting habit fades as the rhythms take over. It is worth the awkward fortnight.

What about sending? Receiving first: your ear calibrates your fist. When a dozen characters are solid, get a paddle, and if you are left-handed set your radio's paddle polarity before the muscle memory forms. Then use the send trainer below.

The half that needs a radio

Inside ShackNerd, this same trainer has a send mode no website can offer: with break-in off nothing transmits, your radio's sidetone reaches the CW decoder, over the monitor on a USB-connected radio or over a practice input on a networked one, and the decoder prints what your paddle actually said, graded against a target. A practice oscillator tells you that you pressed the paddle; your own radio tells you what your keying sounds like to the station on the other end. ShackNerd is free, one small program, and every browser you own becomes the radio.