You've got a string of dots and dashes — off a bracelet, a tattoo, a game, a note someone left you — and you've pasted it into a decoder. It came back as gibberish, or as nothing at all.
That is almost never because the decoder is broken. Morse is a small, rigid system, and there are only a handful of ways a pattern can fail. Here they are, in the order they actually happen, with how to fix each one.
1. The gaps are gone
By far the most common cause. In Morse the silence carries as much meaning as the marks: one unit between symbols inside a letter, three between letters, seven between words. Strip those out and the string stops being decodable — not because it's wrong, but because it becomes ambiguous.
.... is H. .. .. is I I. . . . . is E E E E. Same four dots, three different messages, and only the spacing separates them.
The fix: if you're copying from something physical, look at the original again and mark where the bigger gaps fall. Engraved and beaded designs often lose them entirely — that's why so much Morse jewelry is unreadable. Try the decoder with different spacings and see which reading makes sense.
2. A group is too long to be a character
This one is quick to check and immediately conclusive. In standard International Morse, no character is longer than seven symbols — and only one, the dollar sign (...-..-), even reaches seven. Almost everything is five or fewer.
So if you're looking at a run of eight, ten, twelve symbols with no break, it is not one character. It's several characters whose gaps were lost, and you're back to problem 1.
The fix: count the symbols in each group. Anything over seven needs splitting. Anything over five is worth a second look.
3. The symbols aren't really dots and dashes
Text picks up substitutions as it travels between apps, fonts and keyboards. What looks like a dash to you may not be a hyphen to a decoder:
| What you may have | What it should be |
|---|---|
| · • ● ∙ (middle dot, bullet) | . |
| – — ‒ (en dash, em dash) | - |
| _ (underscore) | - |
| 1 and 0, or O and I | . and - |
Autocorrect is the usual culprit: type two hyphens in many editors and you get a single em dash. The pattern still looks right and no longer parses.
The fix: our decoder already accepts middle-dot, bullet, en-dash, em-dash and pipe as stand-ins, so paste it as-is first. If it still fails, retype the string using only . and -.
4. There's a stray character in the middle
A colon, comma, bracket or stray letter inside the pattern will stop a decode dead. We see this constantly in real searches — patterns arriving with punctuation baked in, usually because the source was a timestamp, a filename or a line of code rather than clean Morse.
The fix: strip everything that isn't a dot, a dash, a space or a slash. If removing a character makes the rest decode cleanly, it was noise.
5. It's a prosign, not a letter
Some sequences are deliberately sent as one unbroken run and are not single characters. ...---... is the classic: written closed up, it's SOS — a prosign, recognised by convention rather than parsed letter by letter. Feed it to a strict decoder as one group and it will refuse, because no character is nine symbols long.
Others behave the same way. .-.-. is both a plus sign and the prosign AR ("end of message"); -...- is both an equals sign and BT, a paragraph break. Both readings are legitimate — context decides which.
The fix: check the prosign list before assuming a long group is broken.
6. It isn't Morse at all
Worth ruling out. Dots-and-dashes notation gets used for things that have nothing to do with Morse:
- Binary written with dots and dashes for 0 and 1 — see Morse vs binary.
- Braille transcribed as dot patterns.
- A substitution cipher that borrows the look of Morse but not the code.
- Decorative "Morse-style" designs that were never encoded from anything. This is common on mass-produced jewelry.
If a pattern decodes to something like EEETTE — plausible letters, meaningless output — that's usually the tell. Real Morse decodes to real words.
A two-minute checklist
- Paste it into the decoder exactly as you have it.
- No luck? Count the symbols per group — anything over seven is a spacing problem.
- Retype using only . and -, with single spaces between letters and / between words.
- Strip any stray punctuation from inside the pattern.
- Check the prosigns for long unbroken runs.
- Still nothing? It probably isn't Morse.
If you'd rather work it out by eye, the full chart has every letter, number and punctuation mark, and how to read Morse code covers the timing from scratch.