Morse Code Translator
Translate text to Morse code and back instantly, then hear it as audio at any speed, watch it flash on a light, and download the sound. Runs fully in your browser.
- Free, no account
- No watermark
- No usage limit
About the Morse Code Translator
Most Morse code translators are a lookup table wearing a text box. You type a word, they hand back dots and dashes, and that's it. Morse was never meant to be read off a page though, since it is a sound and a rhythm, and staring at ... --- ... on a screen tells you almost nothing about the code. This tool converts text to Morse and back like any other, live as you type, no Convert button. The difference is you can then hear it at real operator timing and any speed you set, watch it flash on a light panel the way a signal lamp works, and download the beeps as an audio file. Everything runs in your browser, so whatever you type never leaves your machine on its own. Share is the one place it travels, and even there your message sits after the # in the link, the part a browser never sends to a server. Whoever you hand that link to can read it, which the Share row says before you copy anything.
It handles the full International set: A through Z, the digits 0 to 9, and the thirteen punctuation marks ITU-R M.1677-1 actually lists, plus five more that it does not. The exclamation mark, semicolon, underscore, dollar sign and ampersand are amateur and commercial extensions rather than treaty characters, so the chart puts them in their own group instead of passing them off as the standard. Type SOS and you get ... --- ... back, and pasting that in returns SOS. Anything it can't map, an emoji, a curly quote, an accented letter with no Morse of its own, gets flagged rather than quietly dropped, so you always know what made it through.
How to use
- Pick a direction. Text to Morse encodes words into dots and dashes, Morse to Text does the reverse. Text to Morse is the default.
- Type or paste into the box, or tap an example chip (SOS, HELLO WORLD, I LOVE YOU, CQ) to drop in a ready phrase. For decoding, write your Morse with dots and dashes, a space between letters, and a
/between words. - Read the result underneath. It updates on every keystroke, nothing to submit. In encode mode you can switch the display between plain dots and dashes and the spoken di-dah form with the small menu above the output.
- Press Play to hear it, then drag the Speed and Pitch sliders to set the pace and the tone. The light panel flashes in step, and two checkboxes let you run just the sound or just the light.
- Download the audio to save the beeps as a
.wav, or hit Copy for the text result. Share hands you a link that reopens the tool with your message and settings loaded. - To double-check a translation, switch direction. The current output becomes the new input, so you can encode a phrase, flip to Morse to Text, and confirm it decodes back.
Hear it the way it actually sounds
Most free tools that bother with sound at all get the timing wrong. They fire off evenly spaced blips, which is not what Morse sounds like. The whole code lives in its timing. A dot is one beat, a dash is three, the gap inside a letter is one beat, between letters it's three, and between words it's seven. Get that 1 to 3 ratio wrong and the code turns to mush, because a receiver hears two letters with too small a gap as one run-on letter.
Press Play here and the tool keys every dot, dash, and gap to that ratio at whatever pace you pick. The Speed slider runs from a slow 5 words per minute, a beginner crawl, up to a brisk 40 that trained operators copy without blinking. Speed in Morse is measured against one reference word, PARIS, which works out to exactly 50 units with its gaps, so the WPM number genuinely means something. The Pitch slider sets the tone in hertz. The default 600 Hz sits in the range operators find comfortable to listen to, and you can drop it lower or push it higher to taste.
So the audio you hear is a faithful rendering of real Morse, and so is the file you download. And if you're actually trying to learn the code, flip the notation menu to Di-dah, which spells each letter the way operators say it aloud, a dot as "dit" and a dash as "dah," so C reads "dah-di-dah-dit." That matches what lands in your ear far better than the shape of it on a chart. A visual chart has you translate one letter at a time, which is exactly the wrong habit to build. Hearing the rhythm at a real speed is how it eventually clicks.
Signal it with light
Sound is one way to send Morse. Light is the other, and it needs no radio, no wire, nothing but a way to make something bright go on and off. The panel under the Play button lights up for every dot and dash and goes dark for the gaps, in step with the tone. Turn the sound off and leave the light on, and you have a silent signal you can practise reading by eye.
That is not just a gimmick. Blinking Morse with a flashlight, a phone screen, or a signal mirror is a real survival skill, three short flashes then three long then three short is SOS, and a search plane can pick it out from a long way off. It works when your phone has no bars and a shout won't carry. Rehearse the rhythm on the panel a few times and it sticks.
Getting the decoder to read your Morse
Encoding is the easy direction, every character has one pattern, so the tool looks each up and strings them together. Decoding is where it gets interesting, because Morse is genuinely ambiguous without its spacing. Take .... On its own that reads as S. But . then .. is EI, and three separate single dots is EEE. Same marks, different words, and the only thing telling them apart is the gaps.
That is why the spacing does real work here. Get the gaps right and the letters come apart cleanly. To decode, put a single space between letters and a / between words. If slashes are a hassle, three or more spaces between words does the same job, since the decoder reads a wide gap as a word break. It also accepts the Unicode dot · and dash −, so pasted Morse using those needs no cleanup first. A solid wall of dots and dashes with no gaps can't be recovered though, not by this tool and not by a person, because the information that separates the letters is not there.
Frequently asked questions
What speed should I set the slider to for learning?
Slower than you'd guess, but not painfully slow. Serious learners send each character fast, around 15 to 20 words per minute, and just stretch the gaps between characters to keep the overall pace easy. That way you learn a letter's sound-shape from the start instead of counting individual dots. Set the Speed slider low enough to keep up, maybe 8 to 12 WPM, and nudge it up as the rhythm stops feeling like separate beeps.
I put spaces between my words but they still ran together. Why?
A single space is what separates letters, so one or two spaces between words still reads as a letter gap rather than a word break. The decoder only starts a new word at three or more spaces, or at a /. So if you typed two spaces between words and got back one long jumble, add a third space or drop in a slash and it splits where you meant it to.
Can I use the sound as a ringtone or in a video?
Yes. The Download button saves the current message as a .wav file, a plain mono tone at the pitch and speed you set. Drop it into a video, attach it to a message, or use it as a notification. And because it is timed properly, a fellow Morse reader could decode your ringtone by ear.
Why do "hello" and "HELLO" give me the same Morse?
Because Morse has no lowercase. There is one pattern per letter and no separate signal for a small a versus a capital A, so case is thrown away on the way in and everything you decode comes back in capitals. Morse never had that distinction, so the tool has nothing to lose. The code was built in the 1840s for telegraph operators who had no use for upper versus lower case.
Is this International Morse or the old American version?
International, the ITU standard (defined in ITU-R M.1677-1), the same table amateur radio operators use worldwide. The five extension marks noted above sit outside that recommendation and are labeled as such in the chart. There was an older American Morse with different patterns and some awkward internal spaces, but it fell out of use long ago. So standard Morse encoded here reads correctly to anyone who knows the code, and it decodes faithfully in the other direction too.
What are the AR or SK codes I sometimes see at the end of a message?
Those are prosigns, letter pairs run together with no gap, used as control signals rather than spelled-out words. AR (.-.-.) marks the end of a message, SK (...-.-) ends the whole contact, an operator's "goodbye." This translator sticks to plain letters, numbers, and punctuation, so if a prosign won't decode into a word, that is why, it is not an error.