Morse Code Translator

Translate text to Morse code and back with audio playback of the signal.

How to Use Morse Code Translator

1

Enter your text

Type the text you want to convert to Morse code.
2

View the translation

See the dots and dashes for each character in your text.
3

Play the audio

Listen to the Morse code beeps to hear your message.

Tested tool guide Tested browser tools Checked August 16, 2026

What Morse Code Translator does, with a checked example

Unlike a substitution between alphabets, Morse Code Translator turns each supported text character into signal notation made from dots, dashes, and boundaries, or reads that notation back as text. It also plays the encoded sequence so its rhythm can be checked by ear. The easy mistake is treating spaces as decoration. They distinguish coded characters and words; without them, a continuous run of dots and dashes may have several valid segmentations. Morse does not encode letter case, so the signal alone cannot preserve whether the source used uppercase or lowercase letters.

Worked example

A concrete input and expected output from the current implementation.

Input

SOS

Expected output

... --- ...

S is three dots and O is three dashes in International Morse code. Repeating S after O produces these three groups, with spaces marking the character boundaries.

How the result is produced

Encoding text

For text-to-Morse conversion, each supported character is replaced by its International Morse pattern. Dots denote short signal elements and dashes denote long signal elements. Separate character groups preserve the breaks needed to read the message. Audio playback expresses those same patterns as short and long sounds, with silence distinguishing structural gaps rather than speaking the letters aloud.

Decoding symbols

For Morse-to-text conversion, the translator treats each bounded dot-and-dash group as one character, maps it to the corresponding letter, digit, or supported mark, and joins the results in order. A word boundary must remain distinguishable from an ordinary character boundary. If separators disappear, decoding is not generally unique because Morse character patterns have different lengths and are not self-delimiting.

Good uses

Verifying that a short call sign, identifier, or practice word has been converted into the intended Morse character groups before copying it into notes.
Decoding a clearly separated dot-and-dash message from a worksheet, puzzle, label, or radio training exercise into readable characters.
Playing a known word such as SOS to compare its audible short-and-long rhythm with the written groups while learning Morse character patterns.

Limits and checks

Spacing is meaningful. Copying Morse through software that removes or collapses its separators can change the interpretation or make reliable decoding impossible.
Uppercase and lowercase letters share the same Morse patterns. A decoded result therefore cannot establish how the letters were capitalized in the original text.
Not every Unicode character, emoji, accented letter, or punctuation mark has an International Morse representation. Text containing unsupported characters may not encode or round-trip completely.

Common questions

Can it decode Morse if all spaces are missing?

Not reliably. Morse depends on gaps to distinguish elements inside one character, adjacent characters, and separate words. Written Morse uses visible separators to represent that timing. Once every boundary is removed, the remaining dots and dashes can often be divided into valid character patterns in multiple ways. A translation cannot prove which segmentation the sender intended.

Will audio playback read the translated words aloud?

No. Playback represents the Morse signal as short and long sounds separated by meaningful gaps; it is not text-to-speech. Use the decoded result when you need readable wording. Use playback when you want to recognize, compare, or practice the audible signal pattern associated with the encoded characters.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.