How to Convert Morse Code to Text

Morse decoding runs backward from encoding: you start with dots and dashes and work back to the original text. It is not hard once you know what the spaces are doing, and understanding it by hand is genuinely useful for spotting an error when an automated output looks wrong.

Spaces Carry the Structure

The hard part of reading Morse is never the symbols. It is the spacing. In written Morse, a space is not blank filler, it is information. A single space says one character ends here and the next begins. A slash with spaces around it says one word ends here. Strip those boundaries out and a run of dots and dashes becomes nearly unreadable. .... is H, four dots as one character. Add a space in the middle, .. .., and it becomes I I, two letters of two dots each. Same symbols, different meaning entirely, because of one space.

Rule one, then: trust the spaces before anything else.

Decoding, One Step at a Time

Find the word breaks first

Locate the forward slashes. Each / marks a boundary between words, so split there before anything else. No slashes usually means either a single word or spaces doing double duty.

Split each word segment on single spaces

Inside a word segment, a single space separates letters. Splitting on spaces gives one group of dots and dashes per character. A four-letter word yields four groups.

Look up each group

Match each group against the Morse code alphabet. Every group maps to exactly one letter, digit, or punctuation mark. Write it down, move to the next.

Reassemble

Join the characters within each word segment, then join the words with spaces. That is your decoded text.

Worked Example: HELLO

Start with .... . .-.. .-.. ---. No slash, so it is one word. Split on spaces:

Five groups, five lookups, one word: HELLO.

Worked Example: Two Words

Start with --. --- / -. --- .--. A slash sits in the middle, so there are two words. Split there first: word 1 is --. ---, word 2 is -. --- .--. Word 1 splits into --. (G) and --- (O), giving GO. Word 2 splits into -. (N), --- (O), and .-- (W), giving NOW. Result: GO NOW.

Worked Example: SOS

SOS is ... --- .... In standard written form with letter spacing, splitting on spaces gives three clean groups:

When actually transmitted as a distress call, SOS drops the inter-letter spacing and runs as one continuous sequence, which is what makes it recognizable through poor conditions. Written out with normal spacing, though, it decodes exactly like any other three-letter word.

When a Group Does Not Match Anything

Every so often a group of dots and dashes matches nothing in the standard table. A few things usually explain it. Spacing errors are the most common cause: if the gap between two letters got dropped, they merge into one long sequence that matches nothing, the way H and I running together become ....., which looks like 5 rather than HI. Adding a space somewhere in the middle and checking both halves against the table usually resolves it. Prosigns are another source of confusion, procedural signals like AR (end of message) or SK (end of contact) get sent merged, without the inter-letter gap, so a long unmatched sequence in a radio log may simply be one of those; the common ones are listed in the prosigns section of the Morse code alphabet page. Genuinely invalid sequences do turn up occasionally too, especially from poorly copied audio, in which case marking the character unknown and moving on usually still leaves the rest of the message readable.

Manual Decoding vs. Automatic

An automated decoder, like the quick-try box above or the full translator on the home page, handles splitting, lookup, and reassembly instantly, flagging any group it cannot match. That covers nearly every practical case. Manual decoding is still worth practicing if you want to learn Morse properly or need to decode audio by ear, since the process is identical either way: recognize the pattern, write the letter, move on. With enough practice the patterns become recognizable without consciously counting anything. Experienced operators hear M as "dah-dah" and S as "dit-dit-dit" without running the lookup step at all, though that level of fluency takes months of regular listening.

Decoding From Audio Is a Different Skill

Written and audio Morse are the same code, but the decoding challenge differs. In audio you are listening for tone length (short is a dot, long is a dash) and silence length (short separates elements, medium separates letters, long separates words), and identifying those in real time is harder than reading a printed string at your own pace. Most people learning to copy audio Morse start around 5 words per minute and build up gradually. The Koch method, developed by German psychologist Ludwig Koch in 1935, has learners start with just two characters at full speed, typically 20 WPM, adding one character at a time as accuracy improves, training the ear to recognize whole character sounds rather than counting elements. It works better than starting slow and speeding up later. For the reverse direction of this whole process, see converting text to Morse code.

A Note on Input Format

Format matters when pasting Morse into any decoder, ours or otherwise. The standard uses periods for dots, hyphens for dashes, single spaces between letters, and a slash with spaces between words. Some sources substitute asterisks for dots or pipes for word breaks. If a translator produces nonsense, check whether the input format matches what the tool expects; a quick find-and-replace usually fixes it.