Morse Code Audio Decoder
Upload a local WAV, MP3, or browser-supported audio file and decode clean Morse-like tones into raw dots and dashes plus readable text. The tool works best with steady single-tone recordings and keeps uncertain results visible.
Drop audio here
Drag in a Morse audio file, or choose one from your device. WAV is usually safest. MP3, M4A, AAC, or OGG may work when your browser can decode them. Files over 25 MB are rejected before decoding.
Decoded text
TextDecoded text will appear here.
Confidence
0%
Estimated speed
Auto
Estimated dot length
Auto
Audio length
0 s
Tone regions
0
Silence gaps
0
Detection threshold
Auto
What this audio-to-Morse decoder can do
Use it for local files that already contain Morse tone audio. It is honest about uncertainty when the recording is noisy, compressed, or poorly spaced.
Use it for Morse-like tone audio
Upload a local file that already contains keyed Morse beeps. The page returns raw dots and dashes plus decoded text when the signal is clean enough.
Do not use it for speech or music
The decoder is not a speech recognizer or music transcriber. Spoken dots and dashes, songs, radio chatter, or mixed effects are outside the target use.
Expect a best-effort result
Automatic audio decoding can miss letters, word gaps, or noisy tones. Treat the decoded text as a starting point and compare it with the raw Morse.
Keep files short and local
Oversized or very long files are rejected before analysis. The selected audio is decoded in your browser instead of being uploaded to MorseWords.
How the audio decoder works
The tool runs locally in your browser. It does not upload your audio file to MorseWords.
Upload audio
Choose a browser-supported file such as WAV, MP3, M4A, AAC, or OGG. Browser decoding support varies, so WAV is the safest fallback.
Find tone regions
The decoder converts the audio to mono, measures short amplitude windows, and separates Morse-like tone regions from silence.
Estimate timing
Tone lengths and silence gaps are compared with a timing unit so short beeps become dots, longer beeps become dashes, and gaps become letters or words.
Decode text
The raw Morse output is passed through the same MorseWords decoder used for pasted dots and dashes, so unknown groups remain visible.
Best recordings for Morse audio to text
Audio decoding is most reliable when the file contains clear beeps, stable timing, and simple silence gaps.
Try WAV before compressed audio
WAV preserves tone edges and quiet gaps better than many compressed files. MP3 may work, but compression can blur short Morse marks.
Use one steady pitch
A consistent tone frequency is easier to separate from silence. Sweeps, mixed pitches, and drifting audio can make detection unstable.
Keep volume steady
Avoid clipped audio, very quiet audio, and large volume swings. A stable level makes the threshold easier to choose.
Preserve timing gaps
Dot, dash, letter, and word gaps must be audible. If words run together, adjust gap settings or clean the raw Morse manually afterward.
Trim dead air carefully
Long silence before or after the Morse usually gets ignored, but cleaner clips are easier to review and less likely to hit duration limits.
Avoid background noise
Static, speech, music, and room noise can look like extra dots and dashes. Generate a clean test signal first when you need a controlled sample.
What the outputs mean
Use the raw Morse, decoded text, and timing summary together instead of trusting one field blindly.
Raw Morse
The detected dot and dash stream, with spaces between letters and slashes between detected word gaps.
Decoded text
Readable text from the raw Morse. Smart spacing can recover some obvious joined words, while exact Morse gaps remain available in settings.
Timing summary
Estimated dot length, speed, tone count, gap count, and confidence so you can tell whether the result is stable.
Low confidence
A low-confidence result is still shown, but it should be checked against the raw Morse and original audio.
When audio decoding does not look right
The decoder is practical for clean Morse audio, but it is not a professional radio signal processor or a general audio transcription tool.
No tones detected
Raise the recording volume, increase sensitivity, trim unrelated noise, or try a cleaner single-tone WAV file.
Wrong characters
Check whether dots and dashes are clipped, stretched, or mixed with background noise. A manual character speed can help steady recordings.
Missing spaces
Lower word gap strictness, try Farnsworth gap style, or review the raw Morse when the original audio has short word spaces.
File too large or too long
Use a shorter clip before decoding. Long-form text-to-audio work belongs on the book translator, not the audio decoder.
Speech, music, or mixed audio
This page looks for Morse-like beeps. It will not reliably decode spoken words, songs, background music, or crowded mixed audio.
Format issue
Browser audio support varies. If MP3, M4A, AAC, OGG, or another compressed file fails, retry with WAV.
Related Morse audio tools
Move to the right canonical tool when you need to generate clean test audio, create long-form output, or practice listening by ear.
Morse code audio decoder FAQ
Can this decode Morse code from an audio file?>
Yes, when the file contains clear Morse-like tone beeps. Upload a local audio file, run Decode audio, and review the raw Morse plus decoded text.
What audio files work best?>
Short, clean recordings with one steady tone, consistent volume, and clear silence between dots, dashes, letters, and words work best.
Can I upload MP3 files?>
Yes, if your browser can decode the MP3. MP3 can work for clean signals, but compression, noise, and clipped edges can make Morse detection less reliable.
Is WAV better for Morse decoding?>
Usually. WAV keeps the tone and silence edges cleaner, so it is the safest format to try when an MP3, M4A, AAC, OGG, or other compressed file decodes poorly.
Why did the decoder miss letters or spaces?>
The timing gaps may be too short, the tone may be clipped, the recording may be noisy, or the speed estimate may not match the audio. Check the raw Morse before trusting the text.
Can it decode speech or music?>
No. This decoder is for Morse-like beep tones. It does not transcribe spoken dots and dashes, music, mixed sound effects, or general audio into Morse.
Can it decode noisy recordings?>
Sometimes, but noisy recordings are less reliable. Use sensitivity and smoothing for small issues, but a cleaner single-tone recording is usually the real fix.
Can I create a clean test file first?>
Yes. Use the sound generator for a quick clean tone test, or use the MP3 generator when you want a downloadable MP3 or WAV file to upload here.
Can I convert text into Morse audio instead?>
Use the audio hub, sound generator, or MP3 generator for text-to-Morse audio. This page goes the opposite direction: audio file to raw Morse and text.
Is my audio uploaded to a server?>
No. The page decodes the selected file in your browser with the Web Audio API. The tool does not upload your audio file to MorseWords.
What should I change if the decoder output looks wrong?>
Try WAV, trim extra silence, use one steady tone, lower background noise, then adjust sensitivity, gap style, word gap strictness, or character speed in advanced settings.
What is the difference between decoding audio and practicing by ear?>
Audio decoding analyzes a file and returns a best-effort text result. Audio practice and quiz pages train you to recognize Morse by listening without relying on automatic decoding.
