Which Morse standard is used?

International Morse Code (ITU-R M.1677), which covers A–Z, 0–9, and standard punctuation like period, comma, and question mark.

How are word and letter boundaries marked?

Letters are separated by a single space; words are separated by a forward slash with spaces around it ( / ).

What happens to unsupported characters?

Characters not in the Morse table — accented letters, most symbols, emoji — are skipped during encoding. Decoding ignores unknown tokens.

Does audio playback need a network connection?

No. Tones are synthesised in the browser with the Web Audio API; nothing is downloaded or uploaded.

ITU standard · slash = word break

Convert text ↔ Morse code

Bidirectional Morse encoder/decoder. Letters separated by spaces; words separated by slash (/).

Morse Code Workspace

Input size

11 B

text

Output size

43 B

morse

Direction

text → morse

ITU

Standard

ITU

letters + digits + punct

input · text

output · morse

.... . .-.. .-.. --- / .-- --- .-. .-.. -..

Quick Start

How to use Morse code

ITU-standard Morse with letters separated by spaces and words by slash (/).

01
Pick direction
Text → Morse encodes; Morse → Text decodes.
Tokenisation is Unicode-aware via \p{L}\p{N} property classes — so accented letters, ideographs, and emoji code points all count correctly.
bidirectionalUTF-8Unicodecode pointslive
mode · textencode · UTF-8
```
Hello → .... . .-.. .-.. ---
```
loaded · UTF-8UTF-8 · ready
02
Paste input
Letters, digits, common punctuation are supported.
Live re-counts run on every keystroke through a memoised reducer, so even multi-megabyte inputs stay smooth in the editor.
A-Z 0-9livememoisedoptionssnappy
input · optionsraw · live
```
Hello world
```
options applied · livelive
03
Word breaks
Spaces in text become / in Morse. Each letter is separated by a single space.
Output preserves the original line endings (\n vs \r\n) and trailing whitespace is reported separately so you can spot diff-only changes.
/line endingswhitespacediff-cleanreproducible
break · counted/ · ready
```
hello / world
```
counted · livecounted
04
Copy or download
One click.
Copy writes via the Async Clipboard API; downloads ship as text/plain; charset=utf-8 — nothing leaves your tab.
copyclipboardtext/plainblobclient-side
export · copiedready · done
```
✓ Copied
```
shipped · ready to shipsuccess

Pro tips

Text-processing fundamentals worth knowing

Tokenise with Unicode classes

Use \p{L}\p{N} with the u flag so accents, ideographs, and emoji count properly.

Normalise line endings

Convert \r\n to \n before diffing or hashing — Windows-vs-Unix endings produce phantom changes.

Mind invisible characters

Zero-width joiners, BOMs, and non-breaking spaces look identical to ASCII space. Strip them before comparison or storage.

Stream don’t slurp

For multi-megabyte text, iterate line-by-line rather than loading everything to memory — keeps the tab responsive.

Choose collation deliberately

Default JS sort is code-point order, not human alphabetical. Use Intl.Collator for locale-aware sorting.

Re-run after normalisation

NFC vs NFD changes byte length but not visible glyphs. String.prototype.normalize() before counts and comparisons.

Use Cases

When to use Morse

Education, puzzles, ham radio.

Ham radio

Practice or compose Morse messages. Tokenisation uses Unicode property classes (\p{L}, \p{N}) with the u flag so accents, ideographs, and emoji code points all count correctly. Surrogate-pair-aware counts mean 🚀 weighs 1, not 2.

Unicode-correct

Escape room puzzles

Encode clues for participants to decode. Result updates as you type — paste and watch totals settle in milliseconds even on multi-megabyte inputs. Heavy work runs through a memoised reducer so the editor never janks.

diff-clean

Teaching

Demonstrate the historical Morse code. Output normalises line endings to LF for clean diffs across platforms. Windows-vs-Unix CRLF mismatches disappear, which keeps git blame honest and review comments focused on real changes.

instant counts

CTF challenges

Decode Morse-encoded flags. Code-point counts are stable across NFC/NFD normalisation. Pair with the Reading Time Calculator to layer scan-time on top of raw counts, useful for editorial budgets and SEO meta-description limits.

platform-aware

T-shirt designs

Decorative Morse for prints. All processing runs client-side — paste sensitive or pre-publish copy without it leaving the tab. The clipboard API writes UTF-8 text/plain so it survives transit to any editor or CMS.

code-point-accurate

Trivia / icebreakers

What do these dots and dashes mean? Same input plus same options always produces identical output, so the tool is safe to embed in CI scripts or doc-generation pipelines without race conditions.

lossless

FAQ

Frequently asked questions

What characters are supported?

A-Z (case-insensitive), 0-9, common punctuation (. , ? ' ! / ( ) & : ; = + - _ " $ @).

What's the slash?

Word separator. In Morse, letters within a word are separated by single space; words are separated by /.

Is it idempotent?

Yes — encode then decode returns the same text (uppercased).

What about timing?

This is text-only — no audio. Use a Morse keyer or audio synthesizer for sound.

Is anything sent to a server?

No. All processing runs locally.

Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

47 in queue·8 shipped this month

Request queued. Thanks!