Morse Code Translator & Audio Synthesizer
Translate text to Morse code and back, then hear it played as real dot-dash audio — adjustable WPM speed, Farnsworth spacing, a visual keying lamp, and one-click WAV export.
- Switch between Text → Morse and Morse → Text using the pill bar, or hit Swap to feed the result back in.
- Type your message, or click one of the sample buttons (SOS, Hello World, a CQ call, a pangram) to try it instantly.
- Adjust Character Speed and Effective Speed (WPM) to control keying speed and Farnsworth spacing, plus tone pitch and volume.
- Click Play Morse to hear it beeped out with a synced visual lamp, or Download WAV to save the audio as a file.
All processing happens entirely in your browser. Your data never leaves your device.
Key Features
- Bidirectional translation: text ↔ Morse code using the full ITU-R M.1677-1 alphabet, digits, punctuation, and accented letters
- Tolerant decoder: accepts middots, en/em dashes, and underscores as dot/dash stand-ins, plus "/", "|", or triple spaces as word breaks
- Adjustable Character Speed and Effective Speed (5–40 WPM) with proper Farnsworth spacing when they differ
- Sample-accurate audio playback via the Web Audio API, with adjustable tone pitch (300–1200 Hz) and volume
- Synced visual keying lamp and per-letter highlight so you can follow the message as it plays
- One-click WAV file export rendered offline from the exact same timing engine as live playback
- Swap button to instantly flip direction and reuse the current output as the next input
- Collapsible full reference chart covering letters, numbers, punctuation, accented characters, and common prosigns (SOS, AR, SK, and more)
- 100% client-side — no message you type is ever sent to a server
About Morse Code Translator
Morse code represents letters, numbers, and punctuation as sequences of short and long signals — dots and dashes — and was the backbone of long-distance communication for over a century, from the first telegraph lines to modern amateur radio. Timing is everything in Morse: a dash is exactly three times the length of a dot, the gap between symbols within one letter is one dot-length, the gap between letters is three, and the gap between words is seven. Get the spacing wrong and the message becomes unreadable, even if the dots and dashes themselves are correct.
ForgeKit's Morse Code Translator handles both directions — text to Morse and Morse back to text — using the full ITU-R M.1677-1 international alphabet, including digits, punctuation, and accented letters. The built-in Audio Synthesizer goes beyond a simple beep: it uses the Web Audio API to key a sine-wave tone with sample-accurate timing at any speed from 5 to 40 WPM, with optional Farnsworth spacing (keeping individual characters fast while stretching the gaps between them) — the same technique ham radio operators and Morse instructors use to build real head-copy skill instead of a symbol-counting habit.
A synced lamp and letter highlight let you follow along visually while it plays, and the same timeline can be rendered offline to a downloadable WAV file for practice sessions, ringtones, or embedding in other projects. Everything runs locally in your browser — nothing you type is ever sent anywhere.
Frequently Asked Questions
The International Morse Code as standardized by ITU-R M.1677-1 — the same alphabet used in amateur radio and virtually every modern reference chart, covering A-Z, 0-9, standard punctuation, and common accented letters (À, Ä, È, É, Ñ, Ö, Ü).
Character Speed is how fast each individual dot and dash is keyed. Effective Speed is the overall speed of the message including gaps. When Effective Speed is set lower than Character Speed, the tool applies Farnsworth spacing: letters are keyed at full speed but the gaps between characters and words stretch out — the standard technique for learning Morse by ear without falling back on counting dots and dashes.
Yes. Click Download WAV to render the exact same dot/dash timeline offline to a 16-bit PCM WAV file using the current speed, pitch, and volume settings — no live playback required first.
Text → Morse skips any character with no Morse equivalent (like most emoji or symbols) and lists what was skipped. Morse → Text shows "?" for any dot/dash sequence that doesn't match a known character, and lists the unrecognized sequences below the input.
No. Translation and audio synthesis both happen entirely in your browser using the Web Audio API — nothing you type or play is ever transmitted to a server.
Prosigns like SOS, AR (end of message), and SK (end of contact) are procedural signals sent as one run-together character rather than spelled-out letters. They're included in the reference chart for learning, but kept out of the decoder since several share a pattern with an ordinary punctuation mark and would be ambiguous to auto-decode.