Decodificador de audio Morse - Decodificar Morse de gravacoes
O que e o decodificador de audio Morse?
The Audio Morse Code Decoder on Morse Code World converts Morse beeps in audio files (WAV, MP3, OGG, M4A) into dots, dashes, and readable text. Upload a recording, analyze tone and timing, and edit the result in your browser. Free, no account required. Uses International Morse Code.
O que e um decodificador de audio Morse?
An audio Morse code decoder converts recordings of Morse beeps into readable text by analyzing timing patterns between tone and silence. Unlike typing dots and dashes by hand, you can start from a WAV or MP3 captured from a practice session, an on-air recording, or exported video audio.
This tool is built for ham radio operators checking a short CW clip, students verifying homework, and anyone who already has Morse as sound rather than as written symbols. It follows International Morse Code (ITU) timing rules and runs entirely in your browser for the audio analysis step.
After decoding, you can cross-check results in the main translator or use the picture translator when your source is a photo or screenshot instead of audio. translator, picture translator.
Supported audio formats
You can upload WAV, MP3, OGG, M4A, and most common audio formats. Use clean recordings with a single tone and minimal background noise.
How it works, step by step
- Upload your audio recording.
- Click decode to analyze tone and silence.
- Review and edit the Morse output.
- Use AI organize for longer messages.
- Read the decoded plain text.
How the decoder works technically
When you upload a file, the decoder uses the browser Web Audio API to decode the file into a PCM waveform — no audio is uploaded to our servers for this step. The waveform is scanned in short frames (about 10 ms each). For every frame, the tool calculates RMS energy (a measure of loudness) to build an envelope of how strong the tone is over time.
That envelope is lightly smoothed, then compared to an adaptive threshold (roughly 30% of the peak level). Frames above the threshold count as “tone on”; frames below count as silence. The decoder merges consecutive frames into segments and measures how long each tone and each gap lasts in milliseconds.
Next, it estimates the dot length by looking at the shortest common tone durations in the recording. Durations near one dot unit become dots (.); durations near three dot units become dashes (-). Gaps are classified using standard ITU ratios: a short gap keeps building the same letter, a medium gap starts a new letter, and a long gap inserts a word break.
Before showing results, the tool checks whether the timing pattern actually looks like Morse (rather than speech or random noise). If timing is too irregular, it asks for a cleaner recording. The Morse string is then mapped to letters using the same International Morse table as the main translator. An optional AI organize step sends the decoded text to Google Gemini on the server to fix spacing and casing — only the text and Morse string are sent, not the original audio file.
Example use cases
- Verify a short CW practice recording before a ham radio exam or club exercise.
- Decode Morse exported from a YouTube demo, podcast clip, or archived training audio.
- Check whether an old answering-machine-style tone sequence spells a callsign or phrase.
- Study timing: compare the detected dot length and threshold against what you hear.
- Turn a rough decode into readable sentences with AI organize, then edit manually.
Tips for best results
- Use consistent tone frequency (500–1000 Hz is often ideal).
- Avoid background noise, speech, and music.
- Shorter clips under two minutes decode more accurately.
- Manually fix dots and dashes if output looks wrong.
- If letter spacing fails, try a cleaner recording with longer pauses between characters.
Limitations you should know
- Works best on single-tone Morse (one steady pitch). Music, speech, or multiple overlapping tones usually fail.
- Heavy noise, clipping, or very fast/high-speed CW reduces accuracy; you may need to edit the Morse output by hand.
- The decoder does not perform on-air signal processing — it analyzes files you already recorded.
- AI organize requires a configured server API key and sends decoded text (not audio) to Google Gemini.
- Extremely long files or dense symbol streams may be rejected to avoid nonsense output.
Frequently asked questions
What audio formats are supported?
WAV, MP3, OGG, M4A, and most common browser-playable formats. If the file plays in your browser, it can usually be analyzed.
Is my audio uploaded to your servers?
No. Decoding runs locally in your browser with the Web Audio API. Only if you use AI organize is decoded text (not the audio file) sent to Google Gemini.
Is this decoder free?
Yes, completely free with no account required for decoding. AI organize depends on server configuration.
Can I decode audio from a YouTube video?
Export or download the audio as WAV or MP3, then upload it here. Avoid background music and commentary for best results.
Why did decoding fail or look like gibberish?
Common causes are background noise, non-Morse audio, irregular timing, or missing pauses between letters. Try a shorter clip with a clear sidetone.
What does AI organize do?
It sends the decoded Morse text to Google Gemini to add sensible word breaks, capitalization, and punctuation. You should still verify the result.
Which Morse standard is used?
International Morse Code (ITU), the same standard as the main Morse Code World translator — not historical American railroad Morse.
Can I edit the Morse before converting to plain text?
Yes. The Morse output field is fully editable so you can fix dots, dashes, and spaces before reading the decoded message.