Language: English

tools / morse

morse/

Convert text to Morse code and back. One space between letters, / between words. Letters, digits and common punctuation are supported; Chinese characters are not.

Text

Morse code

FAQ

How is Morse code written, and what do the dots, dashes and spaces mean?

A dot is written . and a dash -. The dots and dashes of one letter are written together, letters are separated by a space, and words by / with a space on each side. Line breaks are kept as they are. For example, SOS is “... --- ...” and HELLO WORLD is “.... . .-.. .-.. --- / .-- --- .-. .-.. -..”.

Can it translate Chinese into Morse code?

Not directly. International Morse code only has Latin letters, digits and a few punctuation marks, and no Chinese characters. Chinese telegraph code is a separate table: each character is first turned into a four-digit number, which is then sent in Morse. That needs the telegraph code book, which this tool doesn't include. Characters it doesn't support, such as Chinese characters, é or ñ, are skipped and the rest is translated as usual; the skipped characters are listed in the message under the output. To translate Chinese, you can write it out in pinyin letters first.

Which characters are supported, and which ones are not in the international standard?

A to Z, 0 to 9, and the punctuation listed in ITU-R M.1677-1: . , : ? ' - / ( ) " = + @. There are also five common extensions that are not in the standard: ! & ; _ $. The code used here for & is the same as the standard's “wait” signal. The standard has no multiplication sign; it says to send the code for the letter X, so there is no × here. Case doesn't matter, and curly quotes ‘ ’ “ ” are treated as straight quotes.

When decoding Morse code, how should dots, dashes and spaces be written?

A dot can be . · or •, and a dash can be - − – — or _. Separate letters with any whitespace, and words with / or | or three or more spaces. Line breaks are kept as line breaks. Groups it can't recognize come out as ? and are listed in the message. Typical causes are missing spaces between letters (for example SOS written as “...---...”), the wrong number of dots or dashes, or a combination that isn't in the table at all.

How are case, spaces and line breaks handled when converting text to Morse code?

Case doesn't matter. Several spaces or tabs count as a single word break. Each line is translated on its own and line breaks are kept; decoding also works line by line. A word made up entirely of unsupported characters is dropped, so it leaves no stray /.

Why do the left and right parentheses have different Morse codes?

In ITU-R M.1677-1 the left parenthesis is “-.--.” and the right one is “-.--.-”, so they differ, while opening and closing quotation marks share one code, “.-..-.”. If your reference writes both parentheses with the same code, one of them won't match what you get here. When decoding, “-.--.-” gives the right parenthesis.

Can it translate run-together signals such as SOS or AR?

Not as a single unit. The distress signal SOS is three letters sent with no gaps, “...---...”; here that counts as one unrecognized group and comes out as ?. To get SOS, write “... --- ...” or type the text SOS. The codes for AR (.-.-.) and KN (-.--.) happen to be the same as + and the left parenthesis, so decoding .-.-. gives + and -.--. gives (.

Is my input uploaded?

No. The translation happens in your browser and nothing is sent to a server.