Morse Code Audio Translator

The Morse Code Audio Translator listens for a repeated tone and measures the lengths of its sound and silence. It decodes the signal itself, rather than guessing an answer from a file name. Start with a short recording containing one sender.

A single steady tone is the clearest input. The Morse Code Audio Translator works best when the sender uses consistent dots, dashes and pauses. Speech, music, several simultaneous stations and drifting tones can compete with the signal you want. Try cropping a longer recording to the useful passage before loading it.

Make the signal audible without clipping. A recording that is too quiet can disappear into its background; one that is too loud may flatten the waveform and introduce extra frequencies. When using a speaker and microphone, reduce room noise and avoid placing the microphone directly against the speaker. Headphone output recorded directly usually has less room interference than a recording made across a room.

Speed is inferred from the lengths of the detected marks. A dot should last one unit and a dash three. Letter gaps and word gaps then separate the recognized patterns. Hand-keyed code may vary enough to confuse this distinction, even when a practiced listener can read it. Longer Farnsworth gaps can also look like word breaks because the audio decoder expects ordinary spacing.

This Morse Code Audio Translator handles one dominant tone at a time. It does not separate overlapping senders or promise to restore severely damaged audio. Start with a clean passage whose content you can check. Once the settings make sense, use the decoded result as a draft to compare with what you hear, especially for call signs, digits and important messages.

Automatic tone detection looks for a prominent frequency in the supported range. A louder background whistle can occasionally win that search. If you know the intended pitch, enter it in hertz to focus the decoder on that tone. Pitch describes the frequency of the beep; it is independent of the rate at which characters are sent.

Manual speed changes the dot-versus-dash boundary and how pauses are classified. Use the character speed, not a slower overall rate produced by extra practice spacing. Select Decode again to apply your corrections to the loaded audio. Clearing both fields restores automatic detection. The Morse Code Audio Translator keeps your recording in memory while you compare these settings, without uploading it.

Very short clips can be ambiguous. One long tone alone might be a slow dot or a faster dash, so the decoder needs a sequence containing varied marks to estimate speed confidently. Supply more of the original message or use a known manual rate. Check the complete Morse result as well as the text, since a plausible word is not proof of a correct decode.

The Morse Code Audio Translator reads files locally and processes microphone samples in memory. It does not send audio to a transcription service or save recordings to a server. Microphone capture begins only after you request it and your browser grants permission. Stopping capture, leaving the page or reaching the three-minute limit releases the microphone.

Choose a new file to replace the current input. Reloading clears the recording and results. You can copy the recognized text and Morse sequence yourself; copying is a separate action and does not publish anything. Browser permission controls still apply, and a microphone indicator from the browser is the most direct way to check whether the input is active.