How to Convert Text to Morse Code (and Actually Hear It) in 2026

Morse code isn't dead — it just moved

International Morse Code dates back to the 1840s, and it's still very much alive: amateur radio operators use it as a low-bandwidth, high-reliability mode that cuts through noise better than voice; search-and-rescue and survival courses teach the SOS pattern; escape rooms and puzzle designers love it; and plenty of hobbyists learn it purely for the challenge. If you've ever needed to actually convert text to Morse — or decode a string of dots and dashes someone sent you — accuracy matters, because a single wrong symbol changes the letter entirely.

Getting the table right

The International Morse Code table assigns a unique sequence of dots (short signals) and dashes (long signals) to every letter, digit, and common punctuation mark. A few examples: A is dot-dash (.-), S is three dots (...), O is three dashes (---), which is where the famous SOS distress signal (... --- ...) comes from. Every digit 0-9 has its own five-symbol code, and punctuation like periods, commas, and question marks are standardized too. Getting even one character wrong in a reference table means every message encoded with it will be subtly corrupted — so a trustworthy Morse tool needs to be checked character-by-character against the published ITU standard, not typed from memory.

Why timing is the hard part

Encoding text into a string of dots and dashes is the easy half. The harder, more often-skipped half is timing — because Morse code isn't really "dots and dashes", it's a sequence of tone lengths and silence lengths, and the ratios between them are precisely standardized:

• A dash is exactly 3 times the length of a dot.
• The gap between symbols within a single letter is 1 dot-length.
• The gap between letters is 3 dot-lengths.
• The gap between words is 7 dot-lengths.

A tool that just beeps every dot and dash for the same fixed length, with the same fixed gap everywhere, doesn't produce Morse code — it produces noise that happens to visually look like Morse code on screen. To actually sound like real Morse — the kind a ham radio operator or a trained ear would recognize as legitimate — playback has to respect all four of those ratios simultaneously, scaled by a chosen playback speed.

How speed (WPM) works

Morse speed is measured in words per minute (WPM), typically calibrated against the word "PARIS" as a standard-length reference word. From a target WPM, you can derive the base "dot" duration in milliseconds, and every other timing (dashes, gaps) scales directly off that one number. Slower speeds (5-10 WPM) are common for beginners learning the code; faster speeds (20-35 WPM) are typical for experienced operators.

What good audio playback needs

Generating the actual tone requires synthesizing a sine wave at a standard frequency (600Hz is a common, comfortable choice) and gating it on and off precisely at the calculated tone and gap durations — turning a static list of dots and dashes into something that genuinely sounds like a telegraph operator sending a message, entirely inside a browser tab with no audio files or plugins.

Practical tips

If you're learning Morse code, start slow (10-13 WPM) and listen more than you read — Morse is fundamentally an audio language, and reading dots and dashes visually is a crutch that doesn't transfer well to real radio use. If you're decoding a puzzle or a message someone sent you, double-check letter boundaries carefully; a single misplaced space between symbols can turn one letter into two completely different ones.

Bottom line

A Morse code tool is only as good as two things: an accurate character table, and audio timing that actually respects the 1:3:1:3:7 ratio standard. Get both right and you have something that's genuinely useful for radio operators, students, and puzzle solvers alike — not just a novelty text scrambler.