Morse Code Audio Decoder: Decode Morse Audio to Text

Morse code is a sound before it is anything else. Long before anyone reads dots and dashes on a screen, a radio operator hears them: a short beep, a long beep, a pause, another beep. Decoding Morse by ear means turning that stream of sound into letters in your head, fast enough to keep up with the sender. It feels impossible the first time you try it, and then — usually after a week or two of short daily practice — it starts to click. This guide explains how it works, how the audio decoder on this page listens, and how to train your own ears to do the same job.

What decoding Morse by ear really means

When you decode Morse by ear, you are not counting dots and dashes. Nobody fast ever does. Counting is far too slow: by the time you have counted three dots, the next letter has already gone past. What trained operators hear instead is the shape of each letter — its rhythm. The letter A, dot-dash, sounds like “di-dah”. The letter B, dash-dot-dot-dot, sounds like “dah-di-di-dit”. Each letter has its own little tune, and your brain learns to recognise the tune whole, the way you recognise a word in a song without spelling it out.

That is why the first rule of learning Morse by ear is to never learn it from a chart alone. A chart teaches your eyes. Your ears need sound. Play a letter, hear its rhythm, say the letter out loud, and repeat. Ten minutes a day of that beats an hour of staring at dots and dashes once a week. The decoder above can help here too: play the test beep, listen to SOS, and notice how three short beeps, three long beeps and three short beeps have a rhythm you can feel even before you know the code.

There is also a second skill hiding inside “decoding by ear”, and it is the one beginners skip: hearing the gaps. The silence between beeps is information, not empty space. A short silence means the next beep belongs to the same letter. A longer silence means the letter is finished. A much longer silence means a new word has started. If you only listen to the beeps and ignore the gaps, every letter runs into the next one and the message turns into soup. Good operators listen to the spaces just as carefully as they listen to the sound.

Speed matters as well, and not in the way people expect. Beginners often ask for very slow Morse, thinking slow is easier. Up to a point it is — but Morse played too slowly falls apart, because the rhythm disappears and you are back to counting. Most teachers start learners around 15 to 20 words per minute for the sound of each letter, with long gaps between letters to give thinking time. The letters themselves stay fast and musical; only the spaces stretch out. As your ear improves, the spaces shrink and the words start to flow.

How audio decoding works: tone detection and timing

A morse code audio decoder does mechanically what your ear does naturally, in three steps: find the tone, measure it, and turn the measurements into letters.

Step one is tone detection. The decoder listens to the incoming sound many times per second and asks a simple question each time: is there a beep right now, or is there silence? For a microphone, it reads the live sound level through the browser and compares it with the sensitivity setting. Anything louder than the threshold counts as “tone on”; anything quieter counts as “tone off”. For an uploaded file, it does the same thing to the recording, slicing it into tiny 10-millisecond windows and checking the loudest moment in each window. The result is a list of runs: tone for 62 milliseconds, silence for 58, tone for 190, silence for 200, and so on.

Step two is timing. The decoder needs to know how long a dot is in this particular recording, because Morse has no fixed speed — one sender may send at 12 words per minute and another at 25. So it looks at the tones it found, takes the middle value of the short ones, and calls that one dot. Everything about three times as long is a dash. The same dot length sorts out the gaps: a silence of about one dot means “same letter, keep going”, about three dots means “letter finished”, and about seven dots means “new word”. The formula behind it is simple: one dot lasts 1200 divided by the speed in words per minute, in milliseconds.

Step three is translation. Once the tones and gaps have been sorted into dots, dashes, letter breaks and word breaks, the decoder looks each group up in the Morse alphabet — dot-dash is A, dash-dot-dot-dot is B — and writes out the plain text. Anything it cannot match, because a beep was missed or an extra click slipped in, shows up as a question mark, which is the decoder’s honest way of saying “I heard something here, but it did not form a letter I know.”

The whole process happens on your device. Your microphone audio and your uploaded file are analysed in the browser and never sent to a server. That is partly about privacy, but it is also about speed: there is no upload, no waiting, and the text appears as the beeps arrive.

Morse timing: the numbers behind every beep

International Morse is built on one unit of time. Everything else is a multiple of that unit: a dot is one unit, a dash is three, the gap inside a letter is one, the gap between letters is three, and the gap between words is seven. Keep those five numbers in your head and you can work out any speed. The table below shows the exact lengths at the speeds beginners meet most often.

Dot length in milliseconds = 1200 ÷ WPM. So at 20 WPM a dot is 60 ms, a dash is 180 ms, and a word gap is 420 ms — the same numbers the timing table under the tool shows.

Notice how tight the timing gets as speed rises. At 30 WPM a dot lasts just 40 milliseconds — less than the blink of an eye — and the difference between a dot and a dash is only 80 milliseconds. That is why steady timing matters more than raw speed. A sender who holds a rock-steady rhythm at 15 WPM is far easier to copy than one who rushes at 25 WPM with dots that wander between 40 and 90 milliseconds.

The full Morse alphabet: letters and numbers

Every letter and number in International Morse is a pattern of dots and dashes, and the patterns are not random. The most common letters are the shortest: E is a single dot, T is a single dash, I is two dots, M is two dashes. Rare letters get longer patterns. Numbers all use exactly five elements, and they follow a pattern of their own — count the dots from the start for 1 to 5, and count the dashes for 6 to 0. Learn the letters in order of length rather than alphabetically and the chart below gets much smaller, much faster.

All codes are International Morse (ITU). The “sound” column uses the usual spoken rhythm: “di” for a dot inside a letter, “dit” for a dot at the end, “dah” for a dash.

Audio practice routines that actually work

Listening practice works when it is short, daily, and slightly hard — never long, rare, and impossible. Fifteen minutes a day for two weeks will take most people further than a single three-hour weekend session. The routine below uses the decoder as a training partner: it hears exactly what you hear, so when you get a letter wrong you can look at what the machine heard and find out where your ear went off track.

1. Days 1–2: two letters only. Start with E and T — one dot, one dash. Play them mixed up, ten at a time, and write down what you hear. When you score 9 out of 10 twice in a row, add I and M.
2. Days 3–4: build to six letters. Add A and N. Practise in short bursts of five minutes, with a break between bursts. Say each letter out loud the moment you hear it — speaking keeps you from silently counting dots.
3. Days 5–6: first words. With E, T, I, M, A and N you can already hear real words: ME, AT, IN, TEA, MAN, EAT, NAME. Hearing words is the turning point — your brain stops translating and starts recognising.
4. Day 7: check yourself with the decoder. Play a slow Morse recording into the microphone and write down what you hear before looking at the decoded text. Compare the two. Every mismatch is a lesson: it tells you exactly which letters still sound alike to you.
5. Week 2: add two letters a day. Add S, O, R, H, D, L, U and the rest in pairs, always mixing the new letters with the ones you already know. Never practise new letters alone — the confusion between similar letters is the skill.
6. Week 2: copy whole messages. Move from single letters to short sentences at 12 to 15 WPM. Miss a letter? Leave a blank and keep going. Chasing one missed letter is how you lose the next three.
7. Week 3 and beyond: raise the speed a little at a time. When you copy comfortably at one speed, go up by 2 WPM — never more. Your ear adapts in small steps, and jumping ahead just teaches you to guess.

Tips for a clean recording

The decoder can only decode what the microphone or the file actually contains. A few minutes spent on the recording itself will do more for accuracy than any sensitivity setting. These tips apply whether you are recording a practice oscillator, a phone speaker, or a radio.

• Record in a quiet room. Close windows, switch off fans and televisions, and keep the microphone away from keyboards. Every click the microphone hears can become a false dot.
• Keep one steady volume. Do not move the speaker or the microphone halfway through. A beep that fades in and out crosses the sensitivity threshold at different moments, which changes its measured length.
• Use a single clear tone. A pure sine-wave beep around 600 to 800 Hz decodes best. Harsh buzzers and tones buried under music are much harder to separate from the background.
• Leave silence at both ends. Start the recording a second before the first beep and let it run a second after the last one. The decoder uses the quiet moments to judge what “silence” means in your recording.
• Prefer WAV over a low-quality MP3. Heavy compression smears the sharp start and end of each beep. If you must use MP3, use the highest quality setting you have.
• Keep the speed steady. Human senders drift, and the decoder estimates one speed for the whole recording. If the first half is slow and the second half is fast, the middle will decode badly whatever you do.
• Record the speaker, not the room. Hold the phone close to the speaker, or plug the audio straight in with a cable when you can. Room echo turns one clean beep into two or three messy ones.

Common decoding mistakes

Most decoding mistakes — human and machine alike — come from the same few confusions. Knowing them in advance means you can catch them instead of trusting a wrong letter.

• Dots heard as dashes. A dot played slightly long, or a dash played slightly short, flips the letter. This is the most common error at higher speeds, and it usually means the sender’s timing is uneven rather than your ear being wrong.
• Missing the letter gap. When the gap between letters is too short, two letters merge into one longer pattern. “ET” can come out as “A”, and “IN” can come out as something else entirely. Listen for the silence, not just the sound.
• Splitting one letter into two. The opposite mistake: a pause inside a letter breaks it in half. “S” becomes “II”, and “H” becomes “II” as well. If your decoded text is full of I’s, the gaps are the problem.
• Counting instead of hearing. Counting dots works at 5 WPM and fails everywhere else. If you catch yourself counting, slow the gaps down — not the letters — and let the rhythm come back.
• Guessing from context too early. Guessing the word from its first letters feels clever, but one wrong guess poisons the rest of the sentence. Copy what you hear, letter by letter, and let the word reveal itself.
• Practising only with your eyes. Reading Morse from a chart and hearing it are different skills. If you only ever read it, your ears never get trained at all. Every study session should include sound.
• Chasing a missed letter. When you miss one letter, the worst thing you can do is stop and think about it while the message carries on without you. Leave a gap, keep listening, and fill it in from context afterwards.

Morse audio decoder vs Morse translator: which one do you need?

A Morse translator and a Morse audio decoder look similar, because both turn one form of Morse into another. The difference is the starting point. A translator starts with text you type: you write HELLO, and it shows you the dots and dashes. An audio decoder starts with sound: you play beeps into a microphone or upload a recording, and it writes out the words. If your Morse is already written down, use a translator. If your Morse only exists as sound — a recording, a radio signal, a practice oscillator — you need a decoder.

The two tools also teach different skills. A translator teaches you what each letter looks like. A decoder teaches you what each letter sounds like, and that is the skill that matters on the air. Radio operators never see the dots and dashes; they hear them. That is why the decoder on this page shows you both the Morse it heard and the timing table underneath it: the timing is the part your ear has to learn, and watching the numbers while you listen trains your ear faster than either one alone.

Use both together: write a message with a translator, play it through a speaker, and decode it back with this page. When the decoded text matches what you wrote, your timing is right.

Five signs you need the audio decoder rather than a translator:

• You have a recording and no transcript. A voicemail, a radio capture, or a practice file with beeps in it and no written version can only be read by listening — by you, or by this decoder.
• You are learning to copy by ear. Translators let your eyes do the work. The decoder makes your ears do it, and the history list shows you exactly which letters you keep missing.
• You want to check your own sending. Send into the microphone, decode it back, and compare. If the decoder reads something different from what you meant to send, your timing drifted.
• You are listening to a real station. On the air there is no text to paste into a translator. There is only sound, and the decoder is the tool built for sound.
• You want to measure speed. The timing table under the tool reads the speed from the beeps themselves, which no translator can do because a translator never hears anything.

Neither tool replaces the other. Translators are faster when you already have the words. Decoders are the only option when you only have the sound. Most learners end up using both every day: the translator to prepare practice material, and the decoder to check what their ears actually heard. The two together close the loop — write it, hear it, decode it, and compare — and that loop is the fastest way to learn Morse that has ever existed.

Famous Morse messages you can decode by ear

Some Morse messages are so famous that operators recognise them before they finish hearing them. They make perfect practice material, because you already know what they should say, so a wrong decode tells you instantly that your ear slipped. Try each one with the test beep or a recording, and see if the decoder agrees with you.

SOS is the one everyone knows: three dots, three dashes, three dots. It was chosen as the distress call precisely because it is so easy to recognise, even through static and even by someone who knows no other Morse at all. CQ is the general call, the Morse equivalent of shouting “is anybody there?” before a conversation starts. The number 73 means “best regards” and is how operators say goodbye at the end of a contact. DE means “from” and introduces a call sign, so “CQ DE” is the start of many real conversations on the air.

All codes are International Morse (ITU). Practise these eight first: they appear in almost every real Morse conversation.

Once you can copy those eight without thinking, try these practice messages in the tool. Each one uses common words, and each one teaches a different rhythm:

1. HELLO WORLD — the classic first message, with long and short letters mixed together.
2. MEET ME AT NOON — double letters and word gaps, the two things beginners miss most.
3. THE QUICK BROWN FOX — every letter of the alphabet in one sentence, the full test of your ear.
4. SOS SOS SOS — three distress calls in a row, exactly how a real emergency sounds.
5. CQ CQ DE TEST — the start of a real amateur radio call, with the rhythm of a conversation.

Do not rush these. Play each message slowly, write down what you hear, then check with the decoder. When you score five out of five without a mistake, raise the speed by 2 WPM and do them all again. That small, steady climb is how an ear is trained — not by jumping to a speed you cannot follow, but by owning each speed before you leave it behind.

Why the decoder sometimes gets it wrong

Even a good decoder has limits, and they are worth understanding so you can tell a bad recording from a real bug. First, the decoder measures loudness, not pitch, so a second sound at the same time — a voice, a door closing, another station — looks exactly like a beep to it. Second, it assumes one steady speed, so a recording that speeds up and slows down will be right at the start and wrong by the end. Third, very short clicks, like the pop of a key being pressed, can register as a dot and insert a letter that was never sent.

Used with those limits in mind, the decoder is a genuinely useful tool. It checks your own copying, it reads recordings you cannot sit through in real time, and it shows you — in the timing table — exactly how steady a sender is. Pair it with ten minutes of daily listening practice, and the day will come when you hear a beep and the letter is simply there, without any decoding at all. That is the moment Morse stops being a code you translate and becomes a language you hear.

Punctuation and Prosigns You Will Meet on the Air

Letters and numbers will carry you through most messages, but real radio conversations are full of punctuation and short signals that are not letters at all. A question mark ends a question, a full stop ends a sentence, and a prosign tells the other operator that the message is finished or that you are signing off. Without them, you can read the words but you cannot follow the conversation.

Punctuation codes are longer than letter codes, usually five or six elements, which makes them easy to spot once you know them. Prosigns are different: they are sent as one continuous group, with no gap between the letters, so they sound like a single flowing pattern. Learn the six punctuation marks below first, then the five prosigns.

The fastest way to learn these is to listen for them in real traffic. The question mark appears at the end of almost every question, AR closes almost every message, and SK closes almost every contact. Once you have heard AR and SK a dozen times, you will never mistake them for letters again.

Q-Codes Every Listener Should Know

Radio operators use a shorthand called Q-codes, three-letter groups that all begin with Q. They were invented for commercial telegraph, where a short code saved time and money, and amateur operators kept them because they work across languages. A German operator and a Japanese operator may share no words at all, but they both understand QTH.

Q-codes are always sent as three letters, and the question mark turns a statement into a question. QTH means my location is, while QTH with a question mark means what is your location? Learn the twelve below, and you will follow most of what you hear on the air.

Three of these appear in almost every contact. QTH tells you where the other station is, QSL confirms that a message was received, and 73, which is not a Q-code at all, says goodbye. Learn QTH, QSL and QRZ first, and the rest will follow naturally as you listen.

How Radio Operators Learned to Copy by Ear

Long before apps and websites, radio operators learned to copy Morse by ear in schools, in the military, and in radio clubs, and their methods still work today. The core idea never changed: learn by sound, not by sight, practise a little every day, and never let your eyes do the work your ears should do.

The most famous training programme was run by the American Radio Relay League, whose station W1AW has broadcast Morse practice sessions every weeknight since the 1930s. Beginners copied the slow sessions, and as they improved they moved to the faster ones, until they could copy at 20 words per minute and qualify for a licence. The military used the same idea in wartime, with daily drills and constant testing, and turned complete beginners into operators in a matter of weeks.

• Code groups. Random five-letter groups with no meaning, so the student cannot guess from context and must copy exactly what is heard.
• Plain language practice. Real words and sentences, so the student learns the rhythm of ordinary speech in Morse.
• The W1AW practice broadcasts. Slow sessions for beginners and fast sessions for advanced students, every weeknight.
• Sending practice in pairs. Two students send to each other, because sending teaches the timing that listening alone never does.
• Copying behind. Writing down the message a few words after hearing it, so the student learns to hold the code in memory.
• Speed drills. Short bursts at a speed slightly above comfort, then back to normal speed, which makes the normal speed feel easy.

Every one of these methods works with the decoder on this page. Use the test beep to hear a message, write down what you hear before looking at the decoded text, and compare the two. The gap between what you heard and what the machine heard is your lesson for the day.

Decoding Through Noise and Interference

A clean recording in a quiet room is easy to decode, but real radio is never clean. Static crackles, other stations bleed across the frequency, signals fade in and out, and a nearby appliance hums through the speaker. Learning to decode through noise is what separates a beginner from an operator who can actually hold a conversation on the air.

The first rule is to improve the signal before you blame your ears. A narrow filter, a good pair of headphones, and a quiet room will do more for your copy than any amount of practice. The second rule is to accept that you will miss letters, and to keep listening anyway. A missed letter is a small hole in a sentence, and the sentence usually fills it in for you.

Six techniques that help in noise:

• Use headphones. They cut room noise and make the gaps between beeps much easier to hear.
• Narrow the receiver filter. Only your station gets through, and the neighbours are cut out.
• Turn the volume down. A loud signal is harder to copy than a comfortable one.
• Slow the gaps, not the letters, when a message is hard to follow.
• Write down what you hear, even with blanks, and fill the blanks in afterwards.
• Ask for a repeat. Every operator expects it, and a repeat is better than a guess.

Noise is part of radio, not a failure of it. The operators who copy best in noise are not the ones with the best ears, they are the ones who stay calm, keep listening, and never stop to chase a letter they missed.

Audio File Formats for Morse Recordings Compared

When you record Morse code to decode later, the file format you choose changes what the decoder hears. Some formats keep every detail of the sound, and some throw detail away to save space. For Morse code, detail matters, because the decoder measures the exact start and end of every beep, and a format that blurs those edges will cost you letters.

The rule is simple: record in a lossless format when you can, and use a compressed format only when you must. A one-minute Morse recording is small in any format, so the space you save by compressing is rarely worth the accuracy you lose.

Five tips for choosing a format:

• Record in WAV when you are practising. It is the most accurate format there is.
• Use FLAC when you want to keep recordings. It saves space without losing any sound.
• If you must use MP3, choose the highest quality setting your recorder offers.
• Never re-save a compressed file as another compressed file. Each save loses more detail.
• Keep the original recording, and make a copy to share, so you always have the clean version.

A clean WAV file of a slow, steady signal will decode perfectly almost every time. A low quality MP3 of a fast, noisy signal will not, and no sensitivity setting can fix a recording that has already lost its edges.