Turn a Morse signal back into text. Pick the decoder that matches what you are holding: a live sound, a recording, or a blinking light.
Decoding Morse is not one problem but three, and the difference is the input. A tone coming out of a speaker, a file sitting on your disk, and a torch blinking in a video need different detection, so MorseKit ships a separate tool for each instead of one that half works on all of them. Lights come in two forms as well, a recording or a lamp in front of you, and the two audio inputs also come combined in a single screen, for when you do not yet know which one you will have.
All of them run entirely in the browser, and they differ in what they measure. Live microphone and audio-file input share one tone decoder: it finds the CW tone anywhere in 300-1200 Hz, thresholds that tone against local noise, and ignores bursts that are not the tone. The video and camera decoders work on brightness inside a region you select; the video tool also listens to the soundtrack for Morse beeps. All of them then derive the dot and dash boundary from the run lengths they observe, so they follow the sender's speed rather than assuming a fixed WPM. Nothing is uploaded to a server in any of them.
Input: Live sound
Point your microphone at a speaker, a key, a buzzer or a radio and read the text as the tones arrive. It finds the CW tone anywhere in 300-1200 Hz and re-decodes a rolling buffer with the same engine as the file decoder. Nothing is uploaded: the decoding runs in your browser.
Best for: A signal playing right now in the room.
Input: MP3, WAV, OGG
Drop in a recording and get the message back. The decoder finds the CW tone in 300-1200 Hz and follows its envelope, so pitch can drift and quiet masters still work when the tone is clear. Any format your browser can play is accepted.
Best for: A recording you already have on disk.
Input: Flashing light or beeps
Select the part of the frame where the light blinks and the decoder reads the flashes. If the Morse is beeps in the soundtrack, those are decoded as soon as you pick the file, with no box needed.
Best for: A video of a light, or a clip whose Morse is in the sound.
Input: Live light
Point your phone's camera at a blinking light and read the message as it flashes. Tap the preview to put the target on the light; the decoder recalibrates as more of the signal arrives. Works on lamps, LEDs and lights inside games shown on a screen.
Best for: A light blinking in front of you right now.
Input: Mic or file
The microphone and file decoders in one screen, with a switch between them. Use this if you are not sure which input you will end up with.
Best for: Trying both without changing pages.
Available on iOS and Android. Free to download.
Free · iOS & Android · 27 Languages
See how it worksIt depends on what you are holding. If the signal is audible right now, use the Microphone Decoder. If it is a saved recording, use the Audio File Decoder. If it is a blinking light, use the Camera Decoder when the light is in front of you and the Video Decoder when you have a recording of it, because a flashing light carries no tone for an audio decoder to find. The combined Audio Decoder covers the first two in one screen.
No. Every decoder runs entirely in your browser using the Web Audio API and canvas. The file or camera feed never leaves your device, and the microphone or camera permission is the only thing you are asked for.
It depends which one. The microphone and file decoders look for a CW tone in 300-1200 Hz; heavy noise, music under the tone, or a very quiet file can still defeat them. For the video and camera decoders, keep only the light inside the target and give the tool a few on/off flashes so it can calibrate. If the Morse is beeps in a video, check the soundtrack result rather than the light box.
Usually yes, within limits. The decoders work out the dot and dash boundary from the run lengths they observe, so they adapt to a steady hand. Very uneven manual sending, where the same operator's dashes vary widely in length, is the case that breaks it.
The MorseKit app decodes offline on iOS and Android, which is the case these web tools cannot cover. The web decoders need the page loaded, but once it is open the decoding itself is local.
