Morse Validator
When a translator returns a question mark, it is not telling you what went wrong. This does.
Three kinds of mistake, one symptom
Morse that will not decode nearly always fails for one of three reasons, and all three produce the same result in an ordinary translator: nothing.
- Foreign characters. An underscore instead of a dash, a middle dot instead of a full stop, a non-breaking space. This is what copying from a website does.
- Missing gaps. The single most common one. Everything is written as one run, so ...... could be SS, HI, or six times E - and a translator has no way to choose.
- Impossible sequences. A path that leads nowhere in the code. Here the useful answer is not "invalid" but "close to these characters".
Why every reading is shown
When a sequence can be read several ways, this page shows all of them instead of picking one. That is a deliberate choice: an answer presented with confidence is worse than no answer, because you cannot tell it apart from a correct one.
It also teaches the thing that matters most about Morse: the gaps carry as much information as the signals. Without them, ... is not S - it is S or EI or IE or EEE, and only silence of the right length decides which.
Frequently asked questions
-
What characters are allowed?
Dots, dashes, spaces and slashes. One space between characters, three or a slash between words - anything else is not Morse notation, however similar it looks.
-
It says my valid character is ambiguous. Why?
Because without gaps it could also be read as several shorter characters. The reading given first is the one an operator would take, but it is worth knowing the others exist.
-
Can it check my sending timing too?
Not here - this checks written Morse. For timing there is the sending practice, which measures your dots, dashes and gaps against the standard.