Morse Code Audio Decoder
Decode Morse code from a recording or live microphone input. The tool detects the tone and timing, shows the Morse sequence it finds, and converts recognizable groups into readable text.
Start with a clear Morse signal and the default settings. If noise, volume changes, or an unusual pitch interfere with the result, use the tuning controls to help isolate the signal.
If the Morse is visible in a photo or screenshot instead of an audio signal, use the Morse Code Image Translator.
How to Use the Audio Morse Decoder
Start with the default settings and let the signal itself guide any adjustments. A clean recording often needs less tuning than a noisy or irregular one.
Choose your audio source
Select Audio File to work with a recording, or Live Microphone to listen through your device's microphone.
Provide a clear Morse signal
Use audio where the Morse tone stands out from background sound. For microphone input, place the sound source close enough to be heard clearly without overloading the microphone.
Check the detected Morse
Review the Detected Morse output first. It shows the dot-and-dash sequence the decoder reconstructed from the audio before that sequence is mapped into text.
Tune only when needed
If the output misses signals or creates extra marks, open Advanced Settings and adjust the controls that are available for sensitivity, frequency, threshold, or timing. Make one change at a time so you can see what improves the result.
What Audio Works Best
Automatic audio decoding works best when the decoder can clearly separate the Morse tone from silence and background sound. The cleaner the timing and signal, the easier it is to reconstruct reliable dots, dashes, letters, and word gaps.
One clear tone
A steady Morse tone is easier to detect than audio with music, speech, several competing pitches, or overlapping signals.
Consistent timing
Clear differences between short and long tones, plus recognizable gaps between characters and words, give the decoder more useful timing information.
Moderate recording level
Very quiet audio can disappear into background noise, while clipped or distorted audio can blur the start and end of each tone. Aim for a clear signal without obvious distortion.
Low background noise
Hiss, hum, voices, room echo, and other tones can create false detections. Use the cleanest source available before relying on advanced tuning.
Some recordings will still need manual adjustment, and heavily mixed or irregular audio may not decode reliably.
How Audio Becomes Morse and Text
The decoder does not need to understand the meaning of the recording. It first measures the signal as sound, then reconstructs Morse timing before converting the Morse groups into characters.
Read the audio signal
The decoder analyses the selected recording or microphone input and looks for the tone energy used by the Morse signal.
Separate tone from gaps
Periods where the signal is present are separated from quieter intervals so the decoder can estimate where each keyed tone begins and ends.
Estimate dots, dashes, and spacing
The lengths of tones and silences are compared to infer short marks, long marks, character gaps, and word gaps.
Map Morse groups to text
The reconstructed dot-and-dash groups appear as Detected Morse, then recognized groups are converted into readable characters in Decoded Text.
Audio File or Live Microphone?
Use an audio file
Choose a recording when you already have Morse audio saved on your device. File input makes it easier to retry the same signal while adjusting decoder settings.
Use the microphone
Choose Live Microphone when the Morse tone is playing from another device or sound source nearby. Browser microphone permission is required, and a quieter environment usually makes the signal easier to isolate.
For either method, compare the Detected Morse with the Decoded Text before assuming the text result is correct.
Troubleshooting a Poor Decode
If the result looks wrong, check the signal before changing several settings at once. The problem is often caused by noise, tone detection, or unclear timing rather than the Morse alphabet itself.
No Morse is detected
Check that the recording actually contains an audible keyed tone and that its level is high enough to stand out from silence. For microphone input, move the sound source closer and confirm that microphone permission is active.
Extra dots or dashes appear
Background noise or a detection threshold that is too sensitive can make unrelated sound look like Morse. Reduce interference first, then adjust the available detection controls if needed.
Parts of the signal disappear
The tone may be too quiet, the threshold may be too strict, or the selected frequency may not match the recording. Review the Signal View and change one relevant setting at a time.
Letters run together or split incorrectly
Uneven spacing can make character and word boundaries difficult to classify. Clean timing produces a more reliable decode than a recording with irregular gaps.
The Morse looks right but the text does not
Compare the Detected Morse output with the text result. If the raw Morse groups are correct, the issue is different from a tone-detection problem and is easier to isolate.
The file will not open
Confirm that the file type is accepted by the upload control and can be decoded by the current browser. Browser audio support can vary by format and platform.
Audio Decoder vs Morse Code Translator
Both tools decode Morse, but they start with different kinds of input.
Use the Audio Decoder for sound
Choose this page when you have a recording, microphone input, Morse beeps, or a CW-style tone that needs to be reconstructed into dots, dashes, and text.
Use the Morse Code Translator for text
Use the main translator when you already have typed text or written dots and dashes. It converts directly between text and Morse notation without analysing audio.
Open the Morse Code Translator →Related Morse Resources
Continue with the tool or guide that matches what you want to do next.
Morse Code Translator
Convert typed text to Morse code or decode written dots and dashes without using audio.
Open the Morse Code Translator →Morse Code Trainer
Practice recognizing generated Morse characters by ear with replay, WPM controls, and session feedback.
Practice with the Morse Code Trainer →Morse Code Alphabet
Look up standard letter, number, punctuation, and Morse reference patterns.
View the Morse Code Alphabet →How Morse Code Works
Learn how dots, dashes, timing, and spacing combine to form Morse characters and messages.
Read How Morse Code Works →Frequently Asked Questions
A Morse code audio decoder analyses a recording or microphone signal, identifies Morse-like tone and silence patterns, reconstructs dots and dashes, and then maps recognizable Morse groups into text.
Yes. Use Live Microphone, allow browser microphone access, and play the Morse tone close enough for your device to capture it clearly. Background noise, echo, and competing sounds can reduce the quality of the decode.
A clear recording with one steady Morse tone, consistent timing, visible silence between signal groups, and little background noise gives the decoder the best chance of separating dots, dashes, characters, and words.
Check the Detected Morse first. Noise, an incorrect tone setting, weak signal levels, clipping, or irregular spacing can change the Morse sequence before it reaches the text-decoding stage. Use Advanced Settings only after checking the source audio.
It is designed for keyed Morse-like tones, not general speech recognition or music transcription. Spoken words, songs, and audio with several overlapping sounds may not produce a useful Morse decode.
Check that the file matches the types accepted by the upload control and that your browser can decode that audio format. Browser support can vary, so using another supported format or browser may help.