To translate Morse code to English, set the translator to Morse → Text, paste a string where the dots and dashes within a single letter run together, individual letters are separated by a single space, and words are separated by a slash surrounded by spaces (" / ") — the decoder then returns readable English in real time. International Morse code assigns each of the 26 letters A–Z, the digits 0–9, and 18 punctuation characters a unique combination of short and long signals: a dot (.) for the short element and a dash (−) for the long element, with a dash lasting exactly three times as long as a dot. The decode direction uses the single, official ITU-R M.1677-1 standard table, so the result matches what amateur radio operators, aviators, and mariners actually transmit on the air. Because the conversion runs in your browser as you type, there is nothing to install and no waiting for a server round-trip. The same tool also handles the reverse direction — encoding English into Morse — so you can verify your own output by decoding it again and confirming the round-trip.
How Morse Code Is Written
Morse code uses only two signal elements: a short element called a dot (.) and a long element called a dash (−). Every letter, digit, and punctuation mark in International Morse is built from a unique combination of those two signals, and the dash is always exactly three times the length of a dot. That single ratio is the foundation of the entire system: every other gap and pause is measured in dot-lengths, which is why a Morse message can be sent at any comfortable speed without changing the meaning. Slow down the sender and the message still says the same thing; the proportions stay constant.
When Morse is written down on paper or typed into a text box, the dot and dash symbols stand in for the short and long tones. The written form has to preserve the same spacing structure that the audio signal would carry, otherwise a human reader or a decoder cannot tell where one letter ends and the next begins. That is why every Morse → English translator, including the Morse Code Translator, uses strict separator rules. Get the separators wrong and the decode will be ambiguous or flat-out incorrect, regardless of how good the character table is.
Translate Morse Code to English in Three Steps
- Set the direction to Morse → Text. If the tool is currently showing Text → Morse, press the swap button (⇄) to flip it. The same input box is used in both directions, so this step just tells the engine which way to convert the characters you type or paste.
- Type or paste the Morse into the input box. Within each letter, run the dots and dashes together with no space. Put a single space between letters, and use a slash surrounded by spaces (" / ") between words. The conversion updates instantly as you type.
- Copy the decoded English. Once the result panel shows the readable text, click Copy to put it on your clipboard, or press Play to hear the Morse as 600 Hz tones at roughly 15 words per minute for ear training or verification.
That is the entire workflow. Because the conversion happens locally in your browser, you can paste a long message and watch the English render character by character without waiting for a server response, and you can keep editing the input until the output looks right.
Understanding Spacing Rules in the Output
Spacing is the part most beginners get wrong, and it is the only thing that distinguishes one Morse sequence from another of the same length. In the ITU-R M.1677-1 standard, four timing rules govern every message:
- A dash is three times the length of a dot.
- The gap between dots and dashes inside one letter equals one dot-length.
- The gap between two letters equals three dot-lengths.
- The gap between two words equals seven dot-lengths.
When Morse is written down, those timing gaps are collapsed into three written separators: nothing between the dots and dashes inside one letter, a single space between letters, and a slash surrounded by spaces between words. The decoder uses those written separators to recover the timing structure, which is why SOS is written "... --- ..." with a space between the three S dots and the three O dashes, and not ".....---...." with no break. Lose the space and you change which letters the pattern represents.
What the ITU-R M.1677-1 Standard Covers
International Morse code is defined in ITU-R Recommendation M.1677-1, last revised in October 2009. That revision is what added the @ symbol to the official alphabet, so any translator that does not handle @ is working from an older draft. The full character set covers 26 letters (A–Z), 10 digits (0–9), and 18 punctuation and symbol characters: period, comma, question mark, apostrophe, exclamation mark, slash, parentheses, ampersand, colon, semicolon, equals sign, plus, hyphen, underscore, quotation mark, dollar sign, and at sign.
The translator's character table follows that standard exactly. The reverse table (Morse → text) is generated programmatically from the single forward table, which guarantees the two directions can never disagree: any string the encoder produces will always decode back to the original text. The audio player uses the same timing ratios — three-dot dashes, one-dot intra-letter gaps, three-dot inter-letter gaps, and seven-dot inter-word gaps — rendered as a 600 Hz sine tone at roughly 15 words per minute. Press Play on SOS ( ... --- ... ) and you will hear the same short-short-short, long-long-long, short-short-short pattern that ships, aircraft, and amateur radio operators have used since 1906.
Practical Decoding Example
Take the Morse string .... . .-.. .-.. --- / .-- --- .-. .-.. -... Split on the word separator " / " first. You get two groups: .... . .-.. .-.. --- and .-- --- .-. .-.. -... Now split each group on single spaces and look up each pattern in the reverse table.
| Morse pattern | Decoded letter |
|---|---|
| .... | H |
| . | E |
| .-.. | L |
| .-.. | L |
| --- | O |
| .-- | W |
| --- | O |
| .-. | R |
| .-.. | L |
| -.. | D |
Reading the letters back together with the word break restored, the decoded English is HELLO WORLD. This is the same round-trip workflow the tool performs: split on word separators, split each chunk on letter spaces, look up each pattern in the reverse table, and concatenate. The full process takes milliseconds because the lookup is a direct hash match against a table generated from the single forward ITU-R M.1677-1 alphabet.
Common Decoding Pitfalls
Decoding errors almost always come from spacing mistakes, not from the character table itself. A few recurring problems and how to handle them:
- Putting spaces inside a letter. H is "...." (four dots, no gap). Writing it as ". . . ." with spaces between dots will decode as "EEEE", four separate Es. Keep the dots and dashes of a single letter joined together with no separator.
- Forgetting the slash between words. "HELLOWORLD" with no separator at all decodes as a single long run of letters and may not even match any real word. Always use " / " (slash with surrounding spaces) as the word break, exactly as the standard requires.
- Mixing separator styles. Some older sources use a double space, a pipe character, or a slash without spaces. The translator only recognizes the standard " / " form, so reformat the input to that style before pasting.
- Lowercase letters in the Morse string. The Morse symbols themselves are case-insensitive — ".--" is W whether you type it as ".--" or ".--". Case only matters once you copy the decoded English text out.
- Characters outside the standard set. Accented characters like é or non-Latin letters are not part of ITU-R M.1677-1 and will be skipped or rejected. Replace them with their plain ASCII equivalents before decoding.
The Morse Code Translator handles the lookup, the timing, and the audio for you, but it cannot invent separators that are not in the input. If the output looks wrong, check the spacing first before suspecting the character table — the spacing rules are the most common reason a decode comes out garbled.