Skip to calculator
Veomark

Free · Instant · No signup

Morse Code Translator (Text to Morse & Morse to Text)

Translate A-Z and 0-9 to ITU Morse, or Morse dots and dashes back to text.

Page updated 2026-09-04.

Morse Code Translator (Text to Morse & Morse to Text) visual
Sponsored

Calculator

Letters, digits, or Morse.

Calculated Results

Tokens

--

Sponsored

Letters separated by spaces, words separated by slashes

'SOS HELP' (8 letters across 2 words) translates to '... --- ... / .... . .-.. .--.' -- each letter's Morse pattern separated by a single space, and the boundary between the two words marked with a slash.

SOS's pattern (... --- ...) is arguably the most recognizable Morse sequence in existence, chosen historically as an internationally recognized distress signal specifically because its three-dot, three-dash, three-dot pattern is simple and unmistakable even under poor signal conditions.

The slash as a word separator is a real, standard Morse code convention, not an arbitrary choice by this tool -- without a clear word-boundary marker, a continuous string of dots and dashes for multiple words would be genuinely ambiguous to decode back into the correct original words.

What this translator does with characters outside its known set

Letters are space-separated. Words use a slash. Unknown tokens stay as ?. A character that doesn't have a defined Morse code mapping (certain punctuation or symbols beyond the standard letter and digit set) is represented as a literal ? in the output rather than being silently dropped -- making it visually obvious that something in the input couldn't be translated.

This handles the standard International Morse Code letter and digit mappings -- historical or specialized Morse variants (like different national telegraph codes that predated full standardization) aren't part of this translator's mapping table.

Decoding in the reverse direction (Morse back to text) depends on correctly interpreting the spacing convention -- a single space between letter patterns and a slash (or equivalent longer gap) between words -- so malformed spacing in Morse input can produce an incorrect decode even if the dot/dash patterns themselves are accurate.

Related text-encoding and cipher tools

For a different, unrelated encoding used historically for radio communication clarity rather than telegraph signaling, the NATO Phonetic Translator spells out letters using standard alphabet words instead.

For a simple letter-substitution cipher rather than a signal encoding, the ROT13 Cipher Generator is a different kind of text transformation.

Frequently Asked Questions (FAQ)

Why does SOS translate to exactly '... --- ...'?

Each letter has a standard International Morse Code pattern: S is three dots (...), O is three dashes (---). SOS is simply those three letters' patterns placed in sequence, and its memorable three-three-three pattern is part of why it was adopted as a universal distress signal.

Why is there a slash between the two words instead of just extra spaces?

Letters are space-separated. Words use a slash. The slash is a standard Morse code convention for marking word boundaries clearly. Without an unambiguous word separator, a long, continuous string of letter patterns for multiple words would be genuinely hard to decode correctly back into distinct words.

What happens if I include a character with no defined Morse mapping?

Letters are space-separated. Words use a slash. Unknown tokens stay as ?. It's represented as a literal question mark in the output, making it visually clear that particular character couldn't be translated, rather than being silently dropped or ignored.

Does this support historical or national Morse code variants?

No. This translator uses the standard, internationally recognized Morse Code letter and digit mappings. Older or nationally specific telegraph codes that predated full standardization aren't part of this translator's mapping table.

Can this decode Morse code back into text as well as encode it?

Yes, using the reverse direction option -- though accurate decoding depends on the input using correct spacing conventions (single spaces between letters, slashes between words), since malformed spacing can produce an incorrect decode even with accurate dot/dash patterns.