Free Morse Code Audio Translator & Decoder
Upload an audio file or use your microphone, and this tool converts Morse code beeps into readable text — letter by letter, in real time. Everything runs in your browser; no audio is ever sent to a server. Want to go the other direction instead? Try the Morse Code Translator to convert text into Morse code, or the Morse Code Image Translator to turn Morse into a shareable graphic.
Morse Code Audio Decoder
Source: none · Status: idle
Detected Morse
Decoded Text
Quick speed presets
⚠ Frequency and WPM here must roughly match the audio's original settings for accurate decoding. Leave "Auto-detect" on if you're unsure what they were.
Session Log
Decoded sessions will show up here automatically.
What Is a Morse Code Audio Translator?
Live Microphone
Decode beeps as they happen
Audio File Upload
WAV or MP3, decoded instantly
A Morse code audio translator — also called a Morse code audio decoder — listens to audio containing Morse code signals and automatically converts those beeps into plain text. Instead of manually timing dots and dashes by ear, the tool analyzes the sound wave, identifies the on/off pattern at the signal's tone frequency, classifies each pulse as a dot or a dash based on its duration, and reconstructs the message letter by letter.
This tool works two ways: point your microphone at a Morse signal for live decoding, or upload a recorded WAV or MP3 file for the tool to analyze all at once. Both methods follow the timing rules defined by the International Morse Code standard (ITU-R M.1677-1) — the same standard used throughout this site.
The #1 Reason Decoding Goes Wrong: Mismatched Settings
Every Morse code audio file is generated at a specific tone frequency (pitch) and a specific speed (WPM). To decode it accurately, the decoder needs to know roughly the same values. If the decoder is listening for a 700 Hz tone but the audio was generated at 550 Hz, it isn't hearing the signal clearly at all — the output will be garbled or empty, not because the tool is broken, but because it's tuned to the wrong pitch.
How to Use the Audio Decoder
- 1
Choose your source
Click Listen (Mic) to decode live through your microphone, or Choose Audio to upload a WAV or MP3 file.
- 2
Check your settings
Make sure Frequency (Hz) and WPM roughly match how the audio was created — or leave Auto-detect on if you're not sure.
- 3
Let it decode
File uploads decode automatically. For microphone input, hold your device near the sound source and keep it running.
- 4
Read the output
Watch the decoded text build character by character in the output panel as each letter completes.
Decoder Settings, Explained Simply
WPM Rate
The speed of the Morse code, in Words Per Minute. Set this to match the speed of your audio source — 13 WPM is a common casual speed, 20 WPM is standard operator pace.
Farnsworth WPM
If Farnsworth timing was used when generating your audio (see below), set this separately. Otherwise, keep it close to your WPM Rate.
Frequency (Hz)
The pitch of the Morse tone. This must roughly match the pitch used when the audio was created — this is the single most important setting to get right.
Volume Threshold
How loud a signal needs to be, relative to the loudest tone detected, before it counts as a dot or dash instead of background silence. Raise it if background noise is being misread as signal.
What is Farnsworth timing?
Farnsworth timing sends each individual character at full speed — say 20 WPM — but stretches out the silence between letters and words. The result sounds slightly slower overall, even though every dot and dash is still transmitted at full speed. It's commonly used in training audio because it gives learners more processing time between characters without distorting how each character actually sounds.
What This Decoder Can Recognize
The full A–Z alphabet, digits 0–9, and common punctuation including period, comma, question mark, slash, plus sign, hyphen, and equals sign.
| Accepted formats | WAV (recommended), MP3 |
| Best quality | Mono (single channel), clean recording with minimal background noise |
| Privacy | All audio is processed in your browser. No files are stored or sent to any server. |
| Browser support | Chrome, Firefox, Safari, Edge — any modern browser |
| Device support | Windows, Mac, Android, iOS |
| Input methods | Audio file upload or live microphone |
Why Use a Decoder Instead of Decoding by Ear?
Skilled operators can absolutely decode Morse code by ear — it's a real, learnable skill. But it takes real practice, and even experienced listeners struggle in specific conditions where a tool doesn't:
Where manual decoding struggles
- • Long messages — fatigue causes missed characters
- • Noisy or weak audio — hard to isolate the tone by ear
- • Unfamiliar or fast speeds — no time to think between letters
- • Requires real training and consistent practice
Where a decoder helps
- • Consistent, tireless timing analysis regardless of message length
- • Can isolate a specific tone frequency even with background noise present
- • Works at any speed once WPM is set correctly
- • Useful immediately, with no Morse training required
That said, a decoder is a tool, not a replacement for learning — many people use one alongside practicing by ear, to check their own accuracy against a reliable reference.
Who Uses a Morse Code Audio Decoder?
Decoding Morse from audio by hand takes real practice and can be slow and error-prone, especially in noisy conditions. Here's who typically reaches for a tool like this instead.
Amateur (Ham) Radio Operators
Decoding real CW transmissions quickly, or double-checking their own copy against the audio.
Students & Learners
Training their ear for Morse code and checking their understanding against real audio.
Teachers
Demonstrating Morse code decoding in class without needing specialist radio equipment.
Archivists & Historians
Reviewing old audio recordings that contain Morse code transmissions.
Puzzle & Escape Room Designers
Verifying their own Morse code audio clues decode correctly before using them.
Privacy-Conscious Users
Anyone who wants Morse decoding done locally, without uploading audio to an unknown server.
Tips for the Best Decoding Results
- •Use clean audio. Mono recordings with minimal background noise decode far more reliably than noisy stereo files.
- •Match your settings when known. Entering the correct frequency and WPM manually is always more reliable than auto-detection.
- •Use Auto-detect when unsure. It scans a range of common CW frequencies (300–1000 Hz) and estimates the clearest signal automatically.
- •For live microphone use: find a quiet room, hold the device close to the speaker, and keep sending at a steady rhythm if you're keying the message yourself.
- •Adjust the volume threshold if background hiss is being read as signal, or if a quiet transmission isn't being picked up at all.
How to Decode Morse Code From Audio Manually
If you'd rather practice decoding by ear instead of relying on the tool above, here's the actual method operators use — the same logic this decoder automates.
- 1
Slow the audio down
Use a media player with speed controls and slow the recording down, especially while you're still learning. This gives you more time to judge each signal's length.
- 2
Mark each beep as a dot or dash
Listen for the duration of each tone. A short beep is a dot; a beep roughly three times as long is a dash. Write down a . or a - for each one as you hear it.
- 3
Track the silences too
A brief pause separates dots and dashes within one letter. A slightly longer pause marks the gap between letters. A noticeably longer pause marks the gap between words — mark that with a space or a slash.
- 4
Match your sequence to the alphabet
Once you have a full string of dots and dashes for a letter, compare it against the Morse code alphabet chart to identify the character.
Need the full reference while you practice? See our Morse code alphabet chart.
Why Morse Code Is Still Heard, Not Just Written
Morse code was designed from the start to be transmitted as sound over telegraph wires and, later, radio. Reading it as a printed chart of dots and dashes is a modern convenience — operators historically learned to recognize entire letters and words by their rhythm alone. That's exactly what this decoder is built to do automatically: listen for the rhythm, not just look for symbols. For the full history of Morse code and how the timing system works, see our main Morse Code Translator page.
Frequently Asked Questions
What is a Morse code audio translator?▼
It's a tool that listens to audio containing Morse code beeps — from a microphone or an uploaded file — and automatically converts the dots and dashes into readable text.
Why is the decoder outputting the wrong letters?▼
This almost always means the Frequency or WPM setting doesn't match how the audio was generated. Try Auto-detect, or enter the correct values manually if you know them.
Is this Morse code audio decoder free?▼
Yes — completely free, with no signup, no account, and no limits.
Does it work on mobile devices?▼
Yes, on modern Android and iOS browsers as well as desktop Chrome, Firefox, Safari, and Edge.
What audio formats are supported?▼
WAV and MP3. WAV tends to give slightly cleaner results since it's uncompressed.
Can it decode Morse code in real time from a microphone?▼
Yes — click Listen and it decodes continuously as the audio plays, character by character.
Is my audio uploaded to a server?▼
No. All processing happens locally in your browser using the Web Audio API. Nothing is transmitted or stored anywhere.
What is Farnsworth timing?▼
A timing style where each character is sent at full speed but the gaps between letters and words are stretched, making the audio feel slower overall while individual signal lengths stay the same.
Can I decode Morse code from a YouTube video or recording?▼
If you can download the audio as a WAV or MP3 file, yes — upload it directly. This tool doesn't fetch audio from external video URLs.
Why does background noise cause bad decoding?▼
The decoder identifies signal based on energy at a specific frequency. Loud background noise near that frequency can be misread as a dot or dash. Cleaner recordings and adjusting the volume threshold both help.
What is the best Morse code tone frequency?▼
There's no single mandated frequency, but most operators find tones between 600–800 Hz easiest to copy comfortably for long periods — high enough to cut through low-frequency noise, low enough to avoid ear fatigue. This decoder defaults to 550–600 Hz as a reasonable middle ground.
Can I decode Morse code faster than I can read it manually?▼
Yes — that's the main advantage of using a decoder. It applies the same timing logic a trained ear would use, but consistently and without fatigue, so it can keep up with long or fast transmissions that would be difficult to copy by hand.