Calculateus

Morse Code Translator

Translate text to Morse code or Morse code back to text.

Result

Morse Code
... --- ...

About the Morse Code Translator

The Morse Code Translator converts plain text into Morse code, or reads Morse code back into text, using the international Morse alphabet for the 26 letters and 10 digits. It's built as a direct two-way lookup rather than a full Morse standard implementation, so it handles the core alphanumeric set cleanly. Anyone learning, teaching, or working with basic Morse code can use it to check or generate messages instantly.

How It Works

You type a line of text or a string of Morse code and pick a direction. In Text to Morse mode, each character is uppercased and swapped for its dot-dash code from a lookup table, with a forward slash marking the space between words. In Morse to Text mode, the input is split on spaces, each dot-dash group is matched back to its letter or digit, and a standalone slash converts back into a space.

Encode: output = join(lookup(uppercase(character)) for each character, using '/' for a space). Decode: output = join(reverse-lookup(code) for each space-separated code, using ' ' wherever a '/' token appears).

Examples

Encoding the distress signal

Entering 'SOS' in Text to Morse mode returns '... --- ...', three dots, three dashes, and three dots separated by spaces, the internationally recognized distress code.

Decoding a two-word message

Entering '.... . .-.. .-.. --- / .-- --- .-. .-.. -..' in Morse to Text mode returns 'HELLO WORLD', with the slash converting into the space between the two words.

Advantages

  • Handles both directions, text to Morse and Morse to text, in a single tool rather than needing two separate lookups.
  • Uses the standard international Morse code table, matching the reference used in ham radio and signaling education.
  • Manages word breaks automatically through the slash convention rather than requiring manual spacing rules.

Common Mistakes

  • Typing Morse code with inconsistent spacing, such as a single space between both letters and words instead of the letter-space, word-slash convention the decoder expects.
  • Including punctuation or symbols in the input and expecting them to encode, when only letters and digits are supported by the lookup table.
  • Running dots and dashes together without spaces between letters, which prevents the decoder from correctly splitting them into individual codes.

Edge Cases to Watch For

  • Only uppercase letters A through Z and digits 0 through 9 exist in the lookup table, so punctuation, accented letters, and other symbols are silently dropped from encoded output rather than causing an error.
  • In decode mode, a Morse group that doesn't match any entry in the table, from a typo or malformed spacing, is likewise dropped silently, which can produce a garbled result with no warning.
  • Word breaks depend entirely on using a single forward slash between Morse groups; a plain double space in place of a slash will not be recognized as a word boundary.
  • Encoding always uppercases the input first, so any case distinctions in the original text are not preserved in the Morse output.

Common Use Cases

  • Amateur radio operators studying or practicing Morse code proficiency.
  • Students or scouts learning Morse code for coursework, badges, or general interest.
  • Puzzle and escape-room designers building Morse-based clues that need quick encoding or decoding.
Written & fact-checked by the Calculateus TeamLast updated August 5, 2026How we verify our formulas

Frequently asked questions

Is Morse code still used for anything today?

Practical use has largely faded with modern digital communication, but Morse code remains part of amateur (ham) radio culture, some aviation navigation beacons, and emergency signaling (SOS is internationally recognized), and it's still taught for its historical significance as one of the earliest forms of long-distance electronic communication.

Conclusion

This translator provides a reliable way to move between text and Morse code for the standard letter and digit set. Messages that require punctuation, accents, or non-English characters will need manual handling, since those fall outside the supported lookup table.