Morse Code Translator

What Is a Morse Code Translator?

A morse code translator converts between human-readable plain text and Morse code — a telegraph encoding where each letter, digit, or symbol maps to a unique sequence of short signals (dots) and long signals (dashes).

Why it matters: Morse is a pattern language, not a font or binary bytes. You need a translator to turn a phrase like SOS into ... --- ... without memorizing every letter.

Example: The letter E is one dot (.). The letter T is one dash (-). Together in a word, each symbol is space-separated: ET → . -.

Common mistake: Confusing Morse with binary code — binary stores bytes as 0s and 1s; Morse uses timed dots and dashes for telegraph communication.

Dots, dashes, and International Morse

International Morse Code (ITU standard) is what TextTools uses — one mapping for A–Z, 0–9, and common punctuation. Morse has no uppercase or lowercase; hello and HELLO encode the same way.

Edge case: Accented letters and emoji have no standard Morse equivalents — they are skipped during encoding rather than guessed.

Morse code vs binary code

Morse encodes characters as audible or visible dot-dash patterns. Binary encodes characters as numeric bytes (0s and 1s). A puzzle asking for dots and dashes needs Morse; a puzzle asking for eight-bit groups needs a binary translator.

How to Convert Text to Morse Code

Text to morse code conversion replaces each supported character with its ITU dot-dash pattern and inserts separators between letters and words.

1. Type or paste plain text in the text pane — letters, digits, and supported punctuation.
2. Read the Morse output — letters separated by spaces, words separated by / .
3. Copy or export the Morse string for sharing or practice.
4. Play Morse to hear beeps at your chosen WPM speed.

Why it matters: Correct spacing is what makes ... --- ... readable as SOS instead of nine random symbols.

Word and letter separators

TextTools outputs one space between letters within a word and / (space-slash-space) between words. That matches common online Morse conventions and decode input on this page.

Example: Hi there → .... .. / - .... . .-. .

Common mistake: Pasting Morse without spaces between letters — the decoder cannot split combined patterns.

Worked examples

Takeaway: Morse grows longer than the source text — each letter becomes several symbols plus spaces.

How to Convert Morse Code to Text

Morse to text decoding splits dot-dash tokens back into letters using the International Morse lookup table.

1. Enter Morse in the Morse pane — use . for dots and - for dashes (underscore _ also works as a dash).
2. Separate letters with spaces and words with / or |.
3. Read decoded text in the text pane as you type.

Why it matters: Both panes are live inputs — you can decode by typing directly into the Morse field without swapping.

Typing dots and dashes in the Morse pane

Paste or type patterns like ... --- ... and the text pane shows SOS. Unknown tokens are skipped silently during decode.

Dash substitutes: Underscore _ is treated as a dash when decoding — useful when copying from sources that avoid hyphens.

Edge case: Missing word separators merge tokens — .- -... without a slash may read as one garbled word instead of two.

Morse Code Timing Rules

International Morse timing uses a dot as the base time unit. A dash lasts three dot units. Gaps between symbols, letters, and words scale from that unit.

Why it matters: Rhythm distinguishes Morse from random beeps — timing is part of the encoding, not decoration.

How WPM affects playback

WPM (words per minute) sets how fast Play Morse plays beeps. TextTools offers 5–40 WPM on the speed slider; default is 20 WPM — a common amateur-radio practice speed.

Example: At 20 WPM, each dot is roughly 60 ms — the standard PARIS timing reference used in ham radio training.

Edge case: Very fast WPM can blur together for beginners — start near 15–20 WPM when learning.

Play Text vs Play Morse Audio

TextTools offers two different audio actions — they are not interchangeable.

Why it matters: Searching “play morse code audio” expects beeps — use Play Morse, not Play text.

Common mistake: Pressing Play text and expecting dot-dash tones — that control reads the message aloud in English.

International vs American Morse Code

International Morse Code (ITU) is the worldwide standard today — this translator implements it exclusively. American Morse Code (landline/railroad Morse) uses different patterns for several characters and is largely historical.

Why it matters: Pasting American Morse from an old chart into an International decoder yields wrong letters.

Prosigns (not supported here)

On-air operators use prosigns — combined signals like AR (end of message) or SK (end of contact) — that are not plain A–Z text. This translator encodes standard characters and punctuation only, not ham-radio prosign shorthand.

Example: Typing AR encodes as two letters (.- .-.), not the single prosign sound used on CW radio.

Morse Code Alphabet Reference

International Morse maps each Latin letter and digit to a unique dot-dash pattern. Punctuation such as . , ? @ is also supported by this translator.

Letters A–Z

Numbers 0–9

Common punctuation

Quick lookup: SOS = ... --- .... HELP = .... . .-.. .--.

Common Use Cases

SOS and emergency pattern

SOS (... --- ...) is the international distress signal — not an acronym, but a distinctive pattern chosen for easy recognition over radio.

Example: Load SOS with the preset control, then Play Morse to hear the standard distress rhythm.

Puzzles, games, and novelty messages

Video games, escape rooms, and friends sometimes hide Morse in audio or text — paste the pattern into the Morse pane to decode quickly.

Edge case: Game designers may use non-standard spacing — add spaces manually if decode fails.

Learning and amateur radio practice

Students and amateur radio newcomers use a translator to verify handwritten Morse before sending on air. The PARIS timing reference at 15–20 WPM matches common CW training speeds.

Example: Encode a callsign, listen with Play Morse at low WPM, then decode from memory to check letter accuracy.

Troubleshooting Invalid Output

Missing letters, empty decode, or garbled words usually mean spacing, dash characters, or the wrong Morse standard — not a broken alphabet table.

Missing letters after translation

Unsupported characters — emoji, accented letters, or symbols outside the ITU set — are omitted during encoding with no placeholder and no error message.

Fix: Replace unsupported glyphs with plain ASCII before converting, or spell out the word (e.g. café → cafe).

Decode returns wrong or empty text

Wrong output usually means missing letter spaces, wrong dash character, or American Morse patterns fed into an International decoder.

Common mistake: Using commas between letters — only spaces separate letter tokens.

Continuous dot-dash strings

A long unbroken string like .... . .-.. .-.. --- without spaces cannot be split into letters automatically — the decoder needs one space between each letter pattern.

Fix: Re-insert spaces between letter groups, or re-encode from the text pane to get correctly spaced output.

Tips and Edge Cases

Morse output length vs plain text

Each letter becomes a multi-symbol pattern plus a separator. Short words can produce surprisingly long Morse strings — HELLO is five tokens with four inter-letter spaces.

Pane stats vs Morse length

Word and character counts under each pane reflect that pane’s content — a 5-character word can show 20+ characters in the Morse pane because dots and dashes count as characters.

Edge case: Input shows 3 characters while Morse shows 15+ — measure the pane you plan to copy, not the source phrase alone.

Privacy and Local Processing

TextTools lets you translate Morse without uploading — conversion runs in your browser and messages are not sent to a server for the translate step.

Why it matters: Puzzle answers and practice phrases stay on your device. Use export or share-link only when you choose to copy results out.

Edge case: Share links encode state in the URL — anyone with the link can read that content. Do not share secrets you would not paste in plain text.

Limitations

TextTools Morse Code Translator focuses on International Morse text conversion and beep playback — not full radio stack features.

• International Morse only — not American landline Morse.
• No prosigns (AR, SK, BT) — standard text and punctuation only.
• No microphone decode — type or paste Morse; no audio-to-text from recordings.
• No tap, light, or vibration modes — beep playback only.
• No WAV audio export — use retention-bar .txt export for text/Morse strings.
• Unsupported characters omitted — no # placeholder in output.
• Play text uses speech synthesis — not Morse tones.

References: ITU (International Morse standard body) · Morse code — Wikipedia (external).

Frequently Asked Questions