Why a dedicated text-to-morse page?
The direction of a translator matters. A tool that decodes morse has different sensible defaults (stop on unknown sequence, assume space = letter gap) than a tool that encodes English (strip unknown characters, normalize case, preserve word boundaries with /).
This page is tuned for encoding. Paste a sentence exactly as you'd write it — uppercase, mixed case, with commas and full stops — and the output comes out with proper word separators (/) between words and single spaces between letters.
What you get in the output
- Uppercase-normalized text — morse is case-insensitive, so typing “Hello” or “HELLO” returns the same pattern.
- Word separators (
/) between words to preserve phrasing. - Punctuation handled — periods, commas, question marks, etc. use the full ITU punctuation set.
- Unknown characters silently skipped, not replaced with
?. Emoji, CJK, and accented characters don't have morse equivalents — the encoder quietly drops them.
Good input vs. output examples
Input: Hello, world!
Output: .... . .-.. .-.. --- --..-- / .-- --- .-. .-.. -.. -.-.--
Each letter separated by a single space, the comma and exclamation mark handled, the one word break marked with /.