Morse code decoding runs in the opposite direction from encoding: you start with a string of dots and dashes and work backward to the original text. The morse code translator on this site does it instantly, but understanding the manual process tells you a lot about why Morse code is structured the way it is, and it helps you spot errors when an output looks wrong.
The key insight: spaces are structure
The hardest thing about reading Morse code is not the symbols themselves. It is the spacing. In written Morse, a space is not just whitespace. It is information. A single space says "this character ends here, the next one starts here." A slash (with spaces around it) says "this word ends here." Without those boundaries, a string of dots and dashes is essentially unreadable. The sequence .... is H (four dots as one character). But if you add a space in the middle, .. .., it becomes I I (two letters, each two dots). Same symbols, completely different meaning.
So the first rule of decoding is: trust the spaces.
The decoding process, step by step
Step 1: Split on the word separator
Find the forward slashes. Each / (slash with a space on each side) marks a boundary between words. Split the input there first. If the input has no slashes, it is either a single word or the spaces are serving double duty. Work with what you have.
Step 2: Split each word segment on single spaces
Within each word segment, a single space separates letters. Split on spaces and each piece is one character's worth of dots and dashes. A four-letter word will give you four groups.
Step 3: Look up each group
Take each dot-and-dash group and find it in the Morse code table. The full table is on the Morse code alphabet page. Each group maps to exactly one letter, digit, or punctuation mark. Write down the character. Move to the next group.
Step 4: Reassemble
Join the characters from each word segment back into a word. Join the words with spaces. You have your decoded text.
Worked example: decoding HELLO
Start with: .... . .-.. .-.. ---
No slash, so this is one word. Split on spaces:
| Group | Letter |
|---|---|
| .... | H |
| . | E |
| .-.. | L |
| .-.. | L |
| --- | O |
Result: HELLO. Five groups, five lookups, one word.
Worked example: decoding a two-word message
Start with: --. --- / -. --- .--
There is a slash in the middle, so there are two words. Split on the slash first:
- Word 1: --. ---
- Word 2: -. --- .--
Split word 1 on spaces: --. is G, --- is O. Word 1 is GO.
Split word 2 on spaces: -. is N, --- is O, .-- is W. Word 2 is NOW.
Result: GO NOW.
Worked example: SOS
SOS is ... --- .... In standard written form with letter spacing, split on spaces:
| Group | Letter |
|---|---|
| ... | S |
| --- | O |
| ... | S |
Result: SOS. When transmitted as a distress signal, SOS is sent without the inter-letter spacing (as one continuous sequence), which makes it recognizable even in poor conditions. But written out with standard spacing, the decoding process is the same as any other three-letter word.
What to do with sequences you cannot find
Every now and then a group of dots and dashes does not match any character in the standard table. A few things cause this.
Spacing errors are the most common. If two letters got merged because the space between them was dropped, you will get one long sequence that matches nothing. Example: H and I run together as ..... looks like 5, not HI. If you suspect a merge, try adding a space somewhere in the middle and check both halves against the table.
Prosigns are another source of confusion. Procedural signals like AR (end of message) or SK (end of contact) are sent as merged sequences without the inter-letter gap. If you see a long sequence in a radio log that does not decode as a letter or digit, it may be a prosign. The most common ones are listed in the prosigns section on the Morse code alphabet page.
Genuinely invalid sequences do appear occasionally, especially if the input came from audio that was poorly copied or from an automated transcription. If nothing works, mark the character as unknown and continue with the rest of the message. Most messages remain readable even with one or two corrupt characters.
Using the translator versus decoding by hand
The morse code translator on this site handles the splitting, lookup, and reassembly automatically. Paste in your Morse string, click decode, and the text comes back. It handles the standard letter and word separators and flags any groups it cannot match. That covers the vast majority of use cases.
Manual decoding is worth practicing if you want to learn Morse code properly, or if you need to decode audio Morse by ear. The process is the same either way: recognize the pattern for each character, write down the letter, move to the next. With practice, the patterns become recognizable without having to consciously count dots and dashes. Experienced operators hear M as "dah-dah" and S as "dit-dit-dit" without thinking through the lookup step at all. That level of fluency takes months of regular practice, but it starts with knowing the table.
Decoding from audio
Written Morse and audio Morse are the same code, but the decoding challenge is different. In audio, you are listening for the length of tones (short is a dot, long is a dash) and the length of silences (short silence separates elements, medium separates letters, long separates words). You have to identify those lengths in real time, which is harder than reading a printed string of dots and dashes at your own pace.
Most people learning to copy Morse audio start around 5 words per minute and work up gradually. There is a well-known method called the Koch method, developed by German psychologist Ludwig Koch in 1935, in which learners start with just two characters at full speed (typically 20 WPM) and add characters one at a time as their accuracy improves. The idea is to train the ear to recognize whole character sounds rather than counting individual elements. It works better than starting slow and speeding up.
For the other direction of translation, see the article on converting text to Morse code.
A note on input format
If you are pasting Morse code into a decoder (ours or any other), the format matters. The standard written format uses periods for dots (.), hyphens for dashes (-), single spaces between letters, and a forward slash with spaces ( / ) between words. Some sources use asterisks for dots or pipes for word breaks. If the translator is not producing sensible output, check whether the input format matches what the tool expects. A quick find-and-replace usually fixes it.