Skip to content

Choose your path

Built around the job you need to finish

Encode supported text with explicit word and whitespace policies, inspect every Morse character and retain the full result without silently dropping unsupported source.

Morse learner

Understand character symbols and word boundaries.

Encode CQ TEST 73, compare rows and switch slash versus per-word lines.

Can distinguish a character code from the word separator.

Fixture author

Detect unsupported text before publishing a practice fixture.

Try A中😀!B, inspect the source offset, then deliberately replace it with supported punctuation and É.

Invalid source produces no partial notation and no unknown character disappears.

Mobile practice-sheet editor

Import and review a long source without losing edits.

Import BOM/CRLF text, remove the BOM explicitly, review 220 characters over pages and undo a replacement.

The source remains recoverable and full output is not limited to the 200-row preview.

Was this tool helpful?

Reference & details

How it works

Validate the original source

Check Unicode validity and the declared 50-character subset: A–Z, É, 0–9 and listed punctuation. Map ASCII lowercase and é only; never expand ß or strip accents.

Make word boundaries explicit

Normalize trims and collapses ASCII space, tab and CR/LF by choice. Strict mode requires single spaces. Choose slash-separated words or one word per line.

Inspect and preserve the result

Review dots, dashes and character-body units in 20-row pages, up to 200 characters. Copy/download retains all notation; the original editor is not replaced by canonical text.

Updated: August 2026

Example Scenarios

Understand character symbols and word boundaries. Encode CQ TEST 73, compare rows and switch slash versus per-word lines.

Detect unsupported text before publishing a practice fixture. Try A中😀!B, inspect the source offset, then deliberately replace it with supported punctuation and É.

Import and review a long source without losing edits. Import BOM/CRLF text, remove the BOM explicitly, review 220 characters over pages and undo a replacement.

Common Mistakes to Avoid

Assuming SOS text is a procedural signal

This tool separates the letters S O S; it does not implement unseparated procedural or emergency signalling.

Publishing partial output after unsupported text

The converter refuses the whole input. Correct the exact reported source location and run again.

FAQ

Period, comma, colon, question mark, apostrophe, hyphen, slash, parentheses, quotation marks, equals, plus and at sign. The precomposed É is also supported. Unlisted characters and procedural signals are refused.

They are outside this declared alphabet. The tool reports the original UTF-16 offset instead of removing or transliterating them. Make any replacement deliberately in your source.

A separated / token is a word boundary. A literal slash in your text becomes -..-.; these must not be confused.

ASCII lowercase and é are canonicalized. Normalize collapses ASCII whitespace; Strict refuses noncanonical spacing. Neither mode is a lossless archive of the original formatting.

UTF-8 imports retain BOM until you remove it explicitly. Source limit: 50,000 UTF-16 units / 200,000 file bytes; output: 1,000,000 units; worker timeout: 10 seconds. No automatic Project save; requesting a download does not verify a saved file.

About Text to Morse Code

Build readable Morse text fixtures with deliberate boundaries. Unsupported characters stop the whole conversion; this is a notation tool, not a transmitter or emergency signalling service.