Enter text and choose an action.
Result
Method and example
The mapping follows in-force ITU-R Recommendation M.1677-1. Characters use spaces between signals and a slash between words. Visual dot and dash variants are normalized before decoding.
Worked example
SOS becomes ... --- ... . HELLO WORLD becomes .... . .-.. .-.. --- / .-- --- .-. .-.. -.. .
Behavior and limits
- Supports A–Z, 0–9, and the documented punctuation shown below.
- Decoded letters are uppercase because Morse does not encode letter case separately.
- Unsupported text characters are rejected; invalid Morse tokens appear as � with a warning rather than a fabricated letter.
- Microphone, audio-file, and camera decoding are outside this tool.
Common mistakes
- Running letters together without character spaces
- Using an unsupported nine-dot token
- Expecting uppercase and lowercase to have different signals
- Treating the slash word separator as a letter
International Morse source
The mapping and spacing method were reviewed against ITU-R M.1677-1 (10/2009), International Morse code, reviewed September 1, 2026. Audio playback is deferred; translation accuracy remains the priority.
Supported punctuation: period, comma, question mark, apostrophe, exclamation mark, slash, parentheses, ampersand, colon, semicolon, equals, plus, hyphen, underscore, quotation mark, dollar sign, and at sign.
Large-text handling
Character counting, case conversion, and reversal accept up to 5,000,000 UTF-16 code units and run only after an explicit action. Morse translation uses a lower 100,000-character text limit because encoded output can expand substantially.