Beta · works best with clean audio

Morse Code Audio Decoder

Upload a recording or hold your mic up to the sound — get the text back. Everything is decoded on your device; nothing is uploaded.

MP3, WAV or OGG. Clean tones decode best — noisy radio needs patience.

waiting for audio…

How the Audio Decoder Works

  1. Give it sound. Drag in an MP3, WAV, or OGG file — or click the microphone button and play the Morse near your device. The waveform appears with the detected tones marked.
  2. It finds the timing. The decoder measures the beeps and silences to work out the sender's speed automatically, then maps the dot-dash patterns to letters. You can override the speed manually if auto-detect struggles.
  3. Read the text. Decoded characters appear in real time, tinted by confidence so you can see at a glance which letters the decoder is sure about and which deserve a second look.

Supported Audio Formats

WAV is the best choice because it is uncompressed — every millisecond of tone and silence is preserved exactly. MP3 and OGG work too, but aggressive compression smears the sharp edges of beeps, and that costs accuracy.

What hurts more than the format: background music, talking over the signal, and re-recorded audio (holding your phone up to a speaker adds room echo and distortion). A clean, direct file will always beat a recording-of-a-recording. If you only have a video, extract or record its audio to a file rather than playing it through speakers whenever possible.

Why Audio Decoding Fails (and How to Fix It)

Most decoders fail silently and leave you staring at garbage. Here is what is actually going wrong, and the fix for each:

Background noise. Hiss, hum, music, or voices confuse the tone detector. *Fix:* use a cleaner segment of the recording — even 10 clear seconds beat 2 noisy minutes. Trim silence and music-only parts first.

Inconsistent timing. Hand-sent Morse speeds up, slows down, and stretches gaps. Machine-perfect decoders expect machine-perfect code. *Fix:* switch on the adaptive mode, which follows the sender's drifting timing instead of fighting it.

Speed mismatch. Code sent at 25 WPM decoded as if it were 12 WPM produces nonsense. *Fix:* set the WPM slider manually to roughly match what you hear, then let auto-detect fine-tune from there.

Weak or fading signal. Tones that swell and fade (common in shortwave recordings) get misread as extra gaps. *Fix:* pick the steadiest passage; normalize the volume if your editor allows it.

Tips for a Clean Decode

  • Use the original file, not a re-recording of it through speakers.
  • Trim leading/trailing silence and any sections with music or speech.
  • Work with steady-tone passages; skip parts where the signal fades in and out.
  • If auto-detect gives garbage, set the WPM manually — your ear is a good speed estimator.
  • For hand-sent or sloppy code, use adaptive mode rather than the strict decoder.
  • When only a few characters look wrong, fix them by hand instead of re-running the whole file — the confidence tinting shows you exactly where to look.

Decode Morse Code from YouTube or Streams

Two options. Easiest: play the video near your device's microphone and use live mic mode — fine for short, clear clips. Better: record the video's audio to a file (most systems can do this with built-in tools) and upload it. The file route avoids room echo entirely and decodes noticeably better. Either way, steady clear tones decode well; videos with background music or commentary over the beeps will struggle.

Prefer typing?

Use the main morse code translator to convert text both ways, or decode morse from photos and screenshots.

Frequently asked questions

How do I decode Morse code from an audio recording?

Upload your MP3, WAV, or OGG file to the decoder above, or click the microphone button to decode live sound. The tool detects the tone timing automatically and converts it to text in real time. Everything happens in your browser — nothing is uploaded anywhere.

What audio formats work best for decoding?

WAV gives the best results because it is uncompressed and preserves exact tone timing. MP3 and OGG also work, but heavy compression, background music, or audio re-recorded through speakers will reduce accuracy noticeably. A clean original file always beats a recording of a recording.

Why does my audio decode fail?

The three usual causes are background noise, inconsistent timing in hand-sent Morse, and a speed mismatch between the sender and the decoder. Try a cleaner segment of audio, trim silence and music, or set the WPM slider manually instead of relying on auto-detect. The troubleshooting section above covers each case.

Can I decode Morse code from a YouTube video?

Yes. Play the video near your device's microphone and use live mic mode, or record the video's audio to a file and upload it for better accuracy. Steady, clear tones decode far better than audio with music or talking layered over the beeps.

Is my uploaded audio sent to a server?

No. Decoding happens 100% in your browser with JavaScript — your audio files never leave your device. That also means the decoder works fully offline once the page has loaded, and there is no queue, no account, and no waiting.

Can the text translator decode audio?

No — the text translator only handles typed dots and dashes. Sound recordings need this audio decoder, which is built specifically to turn tones into text. If your code is already written out as dots and dashes, [translate typed Morse → /] instead. [Prefer typing? Use the text translator → /] Still stuck? Learn to decode by ear