Morse Translator Audio Guide: WPM, Tone, WAV Export

By the Learn Morsy Content Team · Reviewed by Enes Vural (Morsy founder) · Published July 21, 2026 · Verified against ITU-R M.1677-1 (2009)

A Morse translator audio tool is the single most useful piece of software for anyone learning Morse code. Not because it teaches you Morse (it does not), but because it lets you hear any word, phrase, or letter at exactly the speed and rhythm you need to drill. Ten seconds after typing “HELLO” you can hear it at 5, 15, or 30 WPM and start matching the shape in your ear.

The catch is that most Morse audio tools online sound wrong. Wrong tone frequency, no Farnsworth spacing, timing drift caused by browser JavaScript scheduling, MP3 compression eating the short dits. We built our own Morse translator after fighting these issues for months in other tools, and this post walks through what a translator has to get right, why each setting matters, and how to use audio playback for actual practice.

What a Morse translator audio tool actually does

A translator has two jobs. First, convert text to audio: take an input string like SOS, map each letter to its dit-dah pattern per ITU-R Recommendation M.1677-1 (2009), and generate a sine-wave tone that turns on and off according to the pattern. Second, convert audio to text: listen to a recording of Morse and decode it back into letters using digital signal processing.

Text to audio is the more common use. You paste HELLO WORLD into our translator, pick 15 WPM, hit Play, and hear the exact rhythm a trained CW operator would send. That audio is what your ear needs to learn. See our Morse decoder guide for the reverse path, decoding audio back to text.

Both paths depend on three settings being correct: tone frequency, character speed, and gap timing (Farnsworth spacing). Every other feature is optional. These three are non-negotiable.

Why audio-first matters for learning Morse

Morse is decoded by ear, not by eye. This is the single most misunderstood fact about the code. Every letter has a specific auditory shape at real WPM speed, and your brain learns to recognize those shapes the same way it recognizes spoken words. Charts and dot-dash notation are lookups, useful for reference and dead as a training method.

The Koch method, which is the current standard for Morse instruction, works by drilling those sound shapes directly. You listen to a letter played at 15-20 WPM character speed until your brain recognizes it as one gestalt, then add another letter, then another. Twenty minutes a day for three weeks and you can copy the full alphabet by ear. A translator audio tool is what plays those letters at the speeds Koch requires.

If you have not started yet, read our complete Morse learning guide for the full roadmap. This post assumes you know why audio matters and focuses on what the translator has to do to be useful for that training.

How CW tone frequency works

The 500-800 Hz band is where CW lives. Our translator defaults to 600 Hz because that is the frequency most ham CW receivers filter to. The human ear separates a single steady tone from broadband noise most easily in that range, which is why maritime and amateur operators standardized around it during the vacuum-tube era and never left.

Our advice: leave the translator at 600 Hz for the first month. Once your ear is trained on standard CW tone, you can experiment with 500 or 700 Hz to match a specific ham radio filter setting. Changing tone frequency does not change what you hear rhythmically. The dit-dah shape is identical.

WPM speed presets and what they mean

WPM (words per minute) is calibrated so that sending the reference word PARIS at 1 WPM takes exactly 60 seconds. The formula for dit-length in seconds is 1.2 / WPM. This ratio was standardized to keep Morse speeds comparable across radios, apps, and training programs.

Here is what each preset speed means in practice:

At 30 WPM a dit lasts 40 ms, which is at the edge of what the ear can time precisely. Any audio system with more than 5 ms of timing drift starts to sound “off” at that speed. This is why we care so much about the Web Audio API scheduling accuracy in our translator, which stays under 1 ms drift on modern browsers.

Farnsworth timing versus standard timing

Farnsworth is a two-speed compromise designed for beginners. Character speed stays fast (15 or 20 WPM) so each letter sounds correct. The gaps between letters and words are stretched so effective speed drops to 5, 7, or 10 WPM. That gives the beginner brain time to process each letter without having to slow down the letter itself.

Standard timing uses one speed for everything. At 15 WPM standard, character speed is 15 WPM and gap speed is 15 WPM. That is what real Morse sounds like on the air.

Our translator supports both. For anyone new to Morse we recommend character 20, effective 7-10 for the first two weeks, then close the gap gradually. The ARRL learning-Morse-code resources walk through the same progression using their own trainer, which follows the identical Koch-Farnsworth pattern.

Why this matters: slowing character speed below 15 WPM changes the auditory shape of each letter. A 5 WPM V sounds like four isolated boops. A 15 WPM V sounds like the opening of Beethoven’s Fifth, one recognizable rhythm. Training on the slow version wastes weeks. See our Morse timing rules post for the full breakdown.

WAV export and why compression breaks Morse

Our translator exports audio as WAV: 44.1 kHz sample rate, 16-bit mono, uncompressed. That format preserves timing exactly and matches what CW operators use for archival recordings.

MP3 and other lossy codecs are a problem for Morse audio. Their compression algorithms are tuned for speech and music, both of which use complex harmonic content. Morse is a single sine-wave tone with very short envelope transitions. Compression can smear those envelopes, blur the boundary between a dit and the gap after it, and at high WPM drop dits entirely below the codec’s detection threshold. We have seen 30 WPM HH (eight dits) decode as H5 or H4 after MP3 round-tripping.

Use cases where WAV export matters:

• Offline practice. Download a WAV file of your drill words, load into any audio player, drill on a plane or in a signal-dead area.
• Ham radio study material. Record standard call signs and Q-codes in WAV, share with a local club without decoder-app dependencies.
• Escape rooms and puzzle design. Embed a Morse WAV in a puzzle. Cleanly decodable by any audio-decoder tool.
• Accessibility applications. Morse-based text entry for users with motor disabilities, where audio feedback needs to be timing-accurate.
• Broadcast and video production. Sound designers embedding real Morse in film and TV. WAV preserves the exact rhythm the story requires.

If a translator only offers MP3 or WebM download and no WAV, it is not built for serious use.

Browser Web Audio API versus native app tradeoffs

Modern browsers ship the Web Audio API, which handles precise audio scheduling in a dedicated audio thread separate from JavaScript. Timing accuracy is well under 1 ms on Chrome, Firefox, Safari, and Edge, which is more than enough for Morse at any WPM humans can copy.

Where browsers still lose to native apps:

• Background playback. iOS Safari suspends audio when the tab is not visible. Native iOS apps run in the background.
• Battery efficiency. A running browser tab burns more battery than a well-tuned native audio pipeline. Long sessions favor native.
• Offline access. A browser tool needs the page loaded. Native apps work without any network at all after installation.
• System integration. Native apps can drive the phone flashlight LED, integrate with lock-screen media controls, and use the Apple Watch as a paddle. Browsers cannot.

Our recommendation: use our browser translator for quick lookups and text-to-audio playback. Use a native Morse trainer app (the Morsy iOS and Android apps, LCWO’s mobile client, G4FON on desktop) for daily Koch drills. Both have a place. Neither replaces the other.

Five common Morse audio-quality mistakes

Wrong tone frequency. Tools that default to 1000 Hz or higher cause ear fatigue within 20 minutes. Change to 600 Hz.

No Farnsworth control. Any tool that only offers “effective speed” without a separate “character speed” setting is built for people who want to sound faster than they are, not for beginners learning correctly. Skip it.

MP3-only export. As covered above, MP3 compression smears Morse envelopes at high WPM. If the tool only offers MP3 or WebM, do not use it for archival material.

JavaScript setInterval-based timing. Legacy web tools use setInterval to schedule tone on-off events. That gives 15-50 ms of drift depending on browser load, which sounds “wobbly” at 20+ WPM. Any tool built after 2015 should use the Web Audio API scheduler instead.

No sidetone envelope shaping. Real CW radios shape the tone with a gentle rise and fall (typical 5 ms attack, 5 ms release) to avoid the sharp click that hurts the ear and sprays broadband noise. Tools that switch the tone on and off instantly sound harsh and are not what a real receiver would deliver. Our translator applies a 4 ms envelope so the audio matches ham-radio ear expectations.

A practical translator practice drill

Here is the drill we recommend to Morsy users who want to test their sending against a decoder:

1. Open our Morse translator in one browser tab. Set 15 WPM, 600 Hz, Farnsworth character 20, effective 10.
2. Type a target phrase (start with SOS, then HELLO, then THE QUICK BROWN FOX).
3. Hit Play. Listen twice.
4. Open a second tab with the translator in Morse-to-text mode. Hit Record.
5. Tap the target phrase on any hard surface with your finger, trying to match the audio rhythm you just heard.
6. Stop recording. Read the decoded output.

If the decoder returns your target phrase, your sending timing is correct. If it returns a mangled string, look at where it broke: extra letters usually mean dahs too short. Missing letters usually mean gaps too long. Do the same drill for ten minutes daily for two weeks and your sending rhythm will lock in.

For structured beginner practice, follow our 21-day 10-minutes-a-day plan. For realistic timeline expectations after that, see our Morse learning timeline post.

Comparing three Morse translator audio tools

We are obviously biased, but the honest tradeoff: LCWO has the best structured Koch curriculum for progressive learning across weeks. morsecode.world is the most feature-loaded free web tool if you want everything from decoders to text encoding puzzles. Our translator focuses on getting the audio playback and decoder right with zero signup and no ads. Pick the tool that matches how you learn.

For the underlying theory of CW as a signalling mode, the Wikipedia continuous wave article has a good primer on why CW dominated early radio and why it still outperforms voice modes at low signal-to-noise ratios.

Try the translator right now

Open our Morse translator in a new tab. Type your name. Set 15 WPM. Hit Play. That is your name in Morse, played at the speed a real ham operator would send it. If you can hear the rhythm and start to guess where the letter boundaries fall, you are already 10% of the way to reading Morse by ear.

Then look up the letters on our Morse code chart to see the dit-dah patterns you just heard. That is the correct order: hear first, then look at the notation. Doing it the other way (memorizing dots on paper and then trying to match audio) is what stops most self-taught learners.

FAQ

What does a Morse translator audio tool do?

It converts text into a continuous wave (CW) audio signal by mapping each letter to its dit-dah pattern and playing beeps at a user-set speed. Good tools also work in reverse, decoding audio recordings back into text. Speed, tone frequency, and Farnsworth spacing should all be adjustable, otherwise the tool is not suitable for real practice.

What tone frequency should Morse code audio use?

500-800 Hz is the standard range for CW. 600 Hz is the most common default. Most hams tune their radio filters to this range because the ear separates a single tone from broadband noise most easily at these frequencies. Speech frequencies (2-4 kHz) are the wrong band and fatigue the ear during long practice.

What is the difference between character speed and effective WPM?

Character speed is how fast individual letters are keyed. Effective WPM includes the gaps between letters and words. Farnsworth timing keeps character speed fast (15-20 WPM) while stretching effective speed down to 5-7 WPM. That trains correct auditory patterns without overwhelming beginners.

Can I export Morse audio as a WAV file?

Yes. Our translator supports WAV export at 44.1 kHz, 16-bit mono, uncompressed. WAV preserves timing exactly. MP3 compression can smear tone envelopes and drop very short dits at high WPM, so we recommend WAV for practice files and archival ham-radio training material.

Is a browser-based Morse translator as good as a native app?

For most practice, yes. The Web Audio API gives sub-millisecond timing accuracy, which is well below the roughly 40 ms threshold where the ear can hear timing drift at 30 WPM. Native apps still win on offline access, background playback, and battery efficiency for long sessions.

What is Farnsworth timing and when should I use it?

Farnsworth timing keeps individual letters at fast character speed (15-20 WPM) but stretches the gaps between letters. This lets beginners hear correct sound shapes from day one without struggling to keep up. Every serious CW trainer since the 1990s uses this method by default. See our Koch method guide for the training progression.

Why does my Morse audio sound different at different speeds?

At real WPM the dit-length in seconds drops (1.2 divided by WPM), so a 20 WPM dit is 60 ms and a 5 WPM dit is 240 ms. Your ear perceives short beeps and long beeps as different tonal shapes. This is why slow-character practice does not transfer to fast copy: the sound itself is different.