Type text to get standard ITU Morse, or paste dots and dashes to decode them back, with 600 Hz playback and a synced indicator.
The translation tables and the oscillator playback are built into this page; nothing you type is sent, saved, or fetched from a network.
Morse input accepts . and - (also ·, −, —). A single space separates characters; three spaces or / separate words — / stands for the BT break prosign. Supported punctuation: . , ? / =.
Both directions run live on every keystroke. Text-to-Morse upper-cases your input and maps each letter, digit and supported punctuation mark through the standard ITU table; spaces become word breaks written as " / " (the written stand-in for the BT break prosign). Morse-to-text normalizes the dot and dash variants you are likely to type (·, −, — all fold into . and -), treats a single space as a character gap and a triple space or slash as a word gap, then looks each dot-dash sequence up in the reverse table. Playback builds the tone event list from the text, times it with a 600 Hz Web Audio oscillator at your chosen speed, and flashes the dot indicator in sync so you can also read it visually.
Yes, in three places. Amateur radio operators keep CW (Morse) alive as a popular mode — a weak Morse signal can be copied where a voice signal cannot. Aviation ground navaids (VOR and NDB) still identify themselves by broadcasting two- or three-letter Morse codes, which is why cockpit charts show them. Maritime GMDSS retired mandatory Morse in 1999 in favor of digital systems, so at sea it survives mostly as a hobby and a backup taught with light and sound.
The fastest documented route is learning by sound in groups rather than alphabetically — the Koch method starts with a few letters (typically K, M, R, S, A, P) at full operating speed, about 18–20 WPM, and adds a new group only when the previous ones are recognized without counting dots. Counting elements is the habit to avoid: it caps your decoding speed at half your thinking speed. Most people need a few weeks of 15-minute daily sessions for a usable 5–10 WPM.
It matters a lot. Slow, evenly-spaced practice tones teach you to count dots, while real operators send rhythmically and at 15–25 WPM; the recognizer that matters is pattern-by-ear, not arithmetic. Use the WPM slider: start the playback around 15 WPM with character lengths short enough that counting becomes impossible, and raise it until mistakes appear, then stay just under that edge.
In the Morse-to-text box, a single space separates characters and three spaces (or a slash) separate words — the slash stands in for the BT break prosign, the traditional way operators marked a word boundary on the key. Both directions follow this convention: text-to-Morse prints letters space-separated and words separated by " / ". The input also accepts the typographic variants · and − in place of . and -.
No. The translation tables are embedded in this page and the playback is a local 600 Hz oscillator from the Web Audio API — no audio files are fetched. Nothing you type is stored or transmitted anywhere.
If you just finished with Morse Code Translator, the natural next steps are Word Frequency Counter, Readability Calculator, Mock JSON Data Generator, or browse every tool in Daily Tools.