Account

What new tool do you want?

Text & Writing

Morse Code Translator

Translate text to Morse code and Morse back to text using the international standard, with letters, numbers and punctuation.

How to use

  1. 1Type text to encode, or paste dots and dashes to decode.
  2. 2Letters are separated by spaces and words by a slash ( / ).

Frequently asked questions

How is Morse code written?

Each letter is a pattern of dots (.) and dashes (-). Letters are separated by a space and words by a slash or three spaces.

What is SOS in Morse code?

SOS is ... --- ... — three dots, three dashes, three dots — sent without letter gaps as a single distress signal.

Which Morse standard is used?

International Morse code as defined by the ITU (Recommendation M.1677-1), the version used worldwide today.

How auto-detect decides which way to translate

With 'Auto-detect' selected, the tool checks whether your input consists only of dots, dashes, slashes and whitespace (allowing both '.'/'-' and the visually similar '·'/'−' characters some fonts and keyboards produce) — if so, it decodes; otherwise it encodes. That works well for typical input, but a short text message made entirely of dashes and periods (rare, but possible) could be misread as Morse. Picking 'Text → Morse' or 'Morse → Text' explicitly removes any ambiguity.

Letters are separated by spaces, words by a slash

The international standard separates letters within a word by a single space (in timing, three dot-lengths of silence) and separates whole words by a slash or an equivalent longer pause (seven dot-lengths). This tool follows that convention in its output and accepts either a slash or three-plus spaces as a word boundary when decoding, which matters because mixing up letter-gaps and word-gaps is the single most common mistake beginners make when copying Morse by hand.

Worked example: Morse Code Translator

Encoding 'SOS Help' produces '... --- ... / .... . .-.. .--.' — note SOS has no internal letter spacing ambiguity here since S (...) and O (---) are distinct patterns, but the famous distress signal is actually sent as one continuous string (...---...) without even the usual letter gaps, which is what makes it recognizable as a single emergency signal rather than three separate letters. Decoding that same string back — '... --- ... / .... ..' — returns 'SOS HI'. Any character with no mapping (a symbol outside the ITU table) decodes to a � placeholder rather than failing silently.

Letters the table does not know simply disappear

When I encode cafe with an accent on the e, the accented letter vanishes and I only get the Morse for c, a, and f. Encoding keeps letters, digits, and the punctuation that has an international pattern, including the comma, the question mark, and the @ sign, and it skips everything else instead of inserting a stand-in. Decoding is the opposite: a dot-dash group that is not in the table comes back as a replacement mark, so I can see the failure. The whole message is uppercased before encoding, which is why sos and SOS produce the same dots and dashes. A box that is only spaces comes back empty.

Underscores, vertical bars, and line breaks

If I paste Morse that uses a middle dot, a bullet, an underscore, or a long minus, those are read as ordinary dots and dashes before decoding starts. A vertical bar splits words the same way a slash does, and so does a run of three or more spaces or a line break. When I encode, any whitespace between words, including a line break, becomes a single slash, and extra spaces inside a word collapse. An exclamation mark is in the table, so hello! keeps a pattern at the end rather than dropping the punctuation. I still pick Text to Morse or Morse to Text when a short note is nothing but dots and dashes, because Auto-detect would try to read it as code.

Related tools

More: Text & Writing