Morse Decoder — Decode by Ear, Chart, or Audio Tool

Built by Enes Vural · Published July 19, 2026 · Verified against ITU-R M.1677-1 (2009)

Decoding Morse code sounds like a lost skill. It is not. Ham radio operators, maritime signallers, aviation NAV beacon listeners, and thousands of hobbyists decode Morse every day. Some by ear, some with software, some with both running side by side to catch what the other misses. If you want to decode Morse yourself, you have three real paths. The one you pick depends on what you are decoding and how fast it is coming at you.

Here is how each decoding method actually works, when to use which, and why the “decode Morse by hovering over a chart” approach fails the moment audio starts moving.

The three ways to decode Morse code

Every method of decoding Morse falls into one of three categories. Each has a specific accuracy ceiling and a specific speed cap.

The interesting one is that last row. Audio decoders look extremely capable on clean recordings. You drop in an MP3 of someone sending at 20 WPM with a metronome and the text pops out perfectly. Real over-the-air Morse is not clean. Fists drift, static bursts hit, atmospheric fading swallows syllables. A trained ear at 20 WPM will out-decode any commercial software on a marginal signal. This is why decoders are best used as an assist, not a replacement.

Decoding Morse by ear: how it actually works

The mistake most beginners make is thinking they will decode by hearing “dit dit dah” and then translating that to U. That approach caps you at about 5 WPM forever. Your conscious brain cannot count symbols faster than that.

Trained Morse decoding is auditory pattern recognition. Every letter has a sound shape: a specific rhythmic gestalt your brain recognises whole, the same way you hear “hello” as a word rather than as the sequence h-e-l-l-o. S sounds like “dididit”. V sounds like the opening motif of Beethoven’s Fifth. Q sounds like “dahdahdidah”. You do not decode it. You hear it.

Building this recognition is a specific training process:

1. Learn letters at full speed from day one. Character speed always 15-20 WPM, never slower. Slow-speed Morse sounds like a different code and does not transfer. You have to re-learn every letter when you speed back up. Our timing rules post explains why the 15 WPM floor is non-negotiable.
2. Use Farnsworth spacing to buy time. At 15 WPM character speed with big gaps between letters, you get slow effective speed (5-10 WPM overall) but the sound shape of each letter stays correct. As your ear catches up, you close the gaps to reach real 15+ WPM.
3. Train with the Koch method letter-by-letter. Start with two contrasting letters (K and M), drill until you copy them at 90%+ accuracy, then add a third, and so on. Our Koch method guide walks the full 40-letter progression.
4. Send while you receive. Motor memory reinforces auditory memory. Beginners who only listen take 30-40% longer to reach 15 WPM. Tap along with the audio using our translator’s tap-to-send mode or a real key.

At 15 WPM you can decode plain-language English in real time. At 20-25 WPM you can decode most ham-radio contacts. At 30-40 WPM you are into contest-CW territory. Above 40 WPM is a rarefied skill: maybe a few thousand people worldwide.

Decoding Morse by chart: the beginner’s fallback

A printed Morse chart is a lookup, not a training tool. It is genuinely useful for two tasks.

• Decoding a very slow signal. Someone tapping SOS on a wall, a light blinking at 3 WPM across a bay, a message left as .- .-.. .-.. --- ..- in a note. Grab the Morse code chart, look up each symbol, write down the letter, move on.
• Checking your own sending. After you tap or key a message, read your own timing against the chart to see if you sent what you meant to.

The chart is useless for real-time decoding of anything faster than about 5 WPM. Your eyes cannot flip between the audio (in your ear), the pen (in your hand), and the chart (on the wall) fast enough to keep up. This is the trap that stops most self-taught Morse learners. They can look up the alphabet, they can decode written dit-dah sequences, but they cannot decode a signal that is actually moving.

If you plan to use Morse for radio, emergency signalling, or any application where speed matters, you have to move past the chart. Chart-based decoding is the training-wheels phase. It is necessary for the first few days and harmful if you never leave it.

Decoding Morse from audio: using a decoder tool

Software Morse decoders listen to a recording (or live audio from a microphone), measure the length of every tone and every gap, and output the corresponding text. Under good conditions they are astonishingly accurate.

Our Morse code translator includes a decoder mode. Paste a recording or record live audio from your microphone, and the decoder reads back the text. Under clean conditions with a steady sender, good signal-to-noise ratio, and standard Farnsworth timing, accuracy is 95-99%. This is the mode you use for:

• Checking your own sending. Record yourself tapping or keying, run it through the decoder, verify what you sent. Fastest way to fix rhythm drift.
• Decoding a recording someone gave you. A puzzle, an escape room clue, an audio message.
• Learning what different speeds sound like. Feed the decoder your own audio at 5, 10, 15, 20, and 25 WPM and see which speeds it still gets right.

Where audio decoders fail:

• Noisy signals. Static bursts, atmospheric fading, side-tone bleed. The decoder loses timing and outputs garbage.
• Bad fists. Human senders with inconsistent ratios (dahs only 2x longer than dits, letter gaps run together) confuse the DSP. Poor senders sound “readable” to a trained human ear because the ear tolerates rhythm drift, but a decoder cannot forgive it.
• Non-standard timing. Farnsworth spacing throws off many decoders. QRQ (high-speed) sending above 30 WPM often exceeds the decoder’s sample resolution.

This is why serious operators use decoders as an assist. The decoder catches details a tired ear misses. The ear catches signals a decoder cannot lock onto. Together they cover more than either alone.

The math behind audio Morse decoding

If you are curious how a decoder actually reads tones, here is the short version.

Morse timing is defined by ITU-R Recommendation M.1677-1 (2009). Every Morse element is measured in dit-lengths. A dit is 1 unit on, a dah is 3 units on, gap inside a letter is 1 unit off, between letters 3 units off, between words 7 units off. The dit length in seconds is 1.2 / WPM. This same timing appears in the ARRL amateur radio Morse learning resources and Wikipedia’s Morse code article if you want secondary references.

A decoder does the following, roughly:

1. Bandpass filter the audio around the expected tone frequency (usually 500-800 Hz for CW).
2. Envelope detect to measure when tone is present versus silent.
3. Cluster tone-on durations into two buckets: short (dits) and long (dahs), using the 3:1 ratio as a threshold hint.
4. Cluster tone-off durations into three buckets: 1-unit (intra-letter), 3-unit (inter-letter), 7-unit (word) gaps.
5. Assemble the resulting dit-dah sequences into letters using a standard Morse lookup table.

Steps 3 and 4 are where accuracy lives or dies. A steady sender gives clean bimodal distributions and the decoder nails it. An inconsistent sender produces overlapping distributions. Some dits as long as short dahs, some letter gaps as long as intra-letter gaps. The decoder starts guessing.

Which decoder should you use

If you want the free, browser-based option: our Morse decoder handles clean audio at 5-30 WPM with high accuracy and requires no download. Type or paste text and it plays audio. Record or upload audio and it decodes text.

If you want a phone app that works offline: the Morsy iOS app includes an offline decoder that runs on-device. Useful when you have no signal or want to decode audio without uploading it anywhere.

If you want a specialist ham-radio decoder for use on the air: FLDIGI (free, cross-platform) and CW Skimmer (Windows, paid) are the standard tools. Both are heavier than a browser translator but handle real-world noisy signals far better than any general-purpose web decoder.

If you want to decode a written dit-dah sequence (someone wrote ... --- ... in a note and you just want to know what it says), you do not need a decoder tool at all. Type it into any Morse-to-text converter, including our translator, and the answer comes back in a second. Written Morse is trivial to decode compared to audio Morse.

Practicing until you are your own decoder

The endgame is decoding Morse in your head at conversational speed without pausing to think. Reaching it takes 4-8 weeks of daily practice for most people, following a structured plan.

Week 1-2: Koch method. Introduce two letters at 15 WPM character speed with Farnsworth gaps giving 5 WPM effective. Drill 10 minutes daily. Add letters one at a time as accuracy climbs above 90%.

Week 3-4: Full alphabet at 15/7 WPM (15 character, 7 effective). Real words. Common English text. Two 10-minute sessions daily.

Week 5-6: Close the Farnsworth gap to 15/12. You are now hearing real Morse at practical speed. Start listening to on-air CW at 15 WPM.

Week 7-8: 20 WPM, full standard timing. You can copy plain English text in real time and understand it as it comes.

Our 21-day beginner plan walks through the daily drill structure. Our realistic Morse learning timeline covers what to expect week by week.

Common decoding mistakes

Counting dits instead of hearing shapes. If you catch yourself thinking “that was three dots so it’s an S,” you are decoding wrong. Speed comes from hearing “dididit” as one sound. Go back to lower Farnsworth speed and let your brain repattern.

Looking at the chart during audio drills. Every glance at a chart is a rep your ear does not get. Cover the chart. Miss letters. Check the chart after the drill, not during.

Practising below 15 WPM character speed. Slow-speed Morse builds bad neural patterns that you will have to unlearn. Widen the gaps instead of slowing the characters.

Sending faster than you can receive. Some students spend 80% of their practice time sending because it feels productive. Reverse it: 20% send, 80% receive. Sending without matching receive skill produces someone who transmits messages no one can decode.

Relying on the decoder as a crutch. Using an audio decoder to check your work is smart. Using it to skip auditory training is a dead end. You will never be able to decode a signal your software cannot handle.

Try the decoder right now

If you want to test a decoder without setting anything up, drop into our translator, switch to Morse → Text mode, and either type dits and dahs manually or record yourself tapping on a table into your phone microphone. Play the recording into the translator and read the output.

Then flip it around. Type a phrase, hit Play at 15 WPM, and see if your ear can catch even one letter. If not, welcome to why the Koch method exists.

FAQ

What is a Morse decoder?

A Morse decoder is anything that converts Morse code dits and dahs into readable text. That includes a person listening by ear, someone reading a written sequence off a chart, or software analysing audio and outputting characters. In practice, “Morse decoder” usually refers to audio decoder tools like our translator, FLDIGI, or CW Skimmer.

How accurate is a Morse code decoder?

On clean audio with a steady sender at 5-30 WPM, a good decoder is 95-99% accurate. Accuracy drops fast with noise, atmospheric fading, or inconsistent sender timing. Trained human decoders remain more accurate than software on marginal signals, which is why serious operators use both together.

Can I decode Morse from a phone recording?

Yes. Record the audio on your phone, upload the file to our Morse decoder, and it outputs the text. Works best on clear recordings with a single steady tone. Phone microphones handle the standard 500-800 Hz CW tone range without issue.

How fast can a decoder read Morse code?

Software decoders comfortably handle 5 to 60 WPM. Above 60 WPM, most consumer decoders lose accuracy because the sample resolution cannot cleanly separate individual dits. Trained humans reach 40-50 WPM by ear, and the world record is above 75 WPM.

Do I need a decoder to learn Morse code?

No. You need it to check your work and to decode audio you cannot copy by ear yet. Learning Morse itself requires audio drills using the Koch method. A decoder does not train your ear, it substitutes for it. Rely on the decoder during learning and you never actually learn.

What is the difference between a Morse decoder and a Morse translator?

A decoder converts Morse (dits and dahs, or audio tones) into text. A translator does that plus the reverse, converting text back into Morse audio, dit-dah notation, or flashing light. Our tool is bidirectional so it works as both.

Can I decode Morse code by hand without any tools?

Yes, using the Morse code chart as a lookup. This works for slow signals: SOS blinked with a flashlight, or a note written in dits and dahs. For live audio faster than 5 WPM you need trained-ear decoding, since no chart can keep up.