About Morse Code Decoder
Morse decoding reads a written signal and rebuilds the text — dots and dashes grouped into letters, with a slash marking the break between words. It is the counterpart to the encoder, and it accepts the input with whatever spacing a human or another tool has left in it.
The main practical complication is spacing, because Morse carries no marking for where one letter ends and the next begins beyond the gap itself. Written with single spaces between letters and a slash between words, the boundaries are unambiguous. Copied with uneven spacing, a decoder has to fall back on the gaps it is given, which is why some received messages decode cleanly and others do not.
Beyond decoding, this is a useful way to check a signal you have generated. Encoding a phrase and decoding it back confirms the round trip, and an unexpected result usually points at a character in the original text that had no representation and was dropped.
Recovery of a dropped or corrupted signal is not attempted. Codes that have no entry in the table are discarded silently rather than being approximated, marked with a placeholder or reported in a list, and the tool offers no error correction, no guessing at a likely intended letter, and no tolerance for the common real-world case where one dash was lost. Either the input is fully valid or the output is quietly short. Because a group that is not recognised leaves no trace, a decoded message that reads oddly should be compared against the original signal rather than assumed to be correct.
How to use Morse Code Decoder
- 1 Paste the Morse code, using dots and dashes with single spaces between letters.
- 2 Use a forward slash or extra spacing to mark the break between words.
- 3 Read the decoded phrase, which is produced as soon as the codes are recognised.
Frequently asked questions
How should words be separated in the input?
With a forward slash. A single space marks the break between letters, so if words were also separated by a single space the decoder would read straight through them as though they were one continuous word. The slash is the conventional stand-in for the longer silence that separates words in transmission.
My decoded text is missing letters. Why?
Either the input had no representation for those letters when it was encoded — punctuation and accented characters fall into that category — or spacing was lost somewhere, causing adjacent code groups to be merged and misread.
Does the tool care whether I use dots or the word "dot"?
It expects the written symbols, a dot and a dash, rather than their names. Convert any spelling-out to symbols before decoding, since the decoder matches on the characters themselves.
Can numbers be decoded?
Yes. The digits 0 to 9 each have a five-symbol representation, and they are handled the same way as letters, so a decoded message can contain numbers without any special treatment.
Free, online, and private
Free to use
Morse Code Decoder is completely free. There is no account to create, no login, and no hidden charge or usage limit.
Runs online in your browser
It is a free online tool that runs entirely in your browser. Nothing to download or install — open the page and start using it right away.
Your data stays private
All processing happens locally on your device. Your input is never uploaded, stored, or tracked, so it never leaves your browser.
How Morse Code Decoder behaves in detail
These are the specifics of this implementation — the exact ranges, defaults and fixed settings you are working with.
| Parameter | Value |
|---|---|
| Code table | 36 codes — A-Z and 0-9 only, no punctuation |
| Word separator | a single slash character; whitespace around it is trimmed |
| Letter separator | any run of whitespace between two codes |
| Unknown code | dropped from the output, with no placeholder or error |
| Output case | uppercase letters and bare digits only |
Compiled from the implementation of this tool and checked against it by itoolnet.
What Morse Code Decoder does not do
Knowing the edges of a tool saves more time than another list of its features. These are the cases where it will not do what you might expect.
- Punctuation has no codes in the table, so the standard exclamation sequence ...-.-.-- loses that character completely — a decoded sentence silently loses its marks and no trace of them remains.
- Codes that are not in the table are swallowed rather than reported, so a corrupted or re-wrapped message shrinks into a shorter but still readable string instead of raising an error. The output always looks like a success.
- The word break is defined only by a slash. A message written with three spaces or a double slash between words is treated as one word, or as an empty one, because the split on the slash happens before the whitespace is looked at.
Tested and documented by itoolnet, the team that builds and maintains this site.