Morse Code Translator

International Morse written characters: A–Z, É, digits and the punctuation shown in the chart. The character and timing reference is ITU-R M.1677-1. Operational prosigns are not interpreted as commands, and extended regional alphabets are not included.

Use whitespace between letter tokens and / between words. Line breaks remain line breaks in the translation and act as word gaps in audio. Consecutive, leading or trailing word separators are invalid in decode mode. A literal slash in the text has its own Morse character code.

Many scripts, emoji and punctuation do not have entries in this chart. Text is normalized to NFC and uppercased; optional Latin accent folding expands supported forms where possible, while É retains its own code. By default unsupported input blocks output; explicit omission reports what was skipped.

No. Letter case is lost, whitespace is normalized into word separators, optional accent folding changes characters and omission drops unsupported input. Decode produces uppercase text. Unknown tokens must be corrected rather than guessed.

Decode accepts ASCII dots and hyphens, middle-dot/bullet dots and Unicode minus/en/em dash variants. All output Morse uses ASCII dots, hyphens, spaces, slash separators and line breaks.

Character speed uses a 1.2 divided by WPM second dot, with dash and standard gaps based on dot units. The optional multiplier enlarges letter and word gaps only, so effective overall reading speed is lower than character speed. WPM uses the conventional PARIS reference.

Mono 44.1 kHz 16-bit PCM WAV, up to 120 seconds, with adjustable 300–1000 Hz tone and 10–80% volume. A brief lead-in and tail are included and tone edges are softened. Longer translations can still be copied as text; increase speed or shorten the message for audio.

It sends S, O and S as three written letters with letter gaps. A continuous operational prosign has different spacing; this tool does not interpret those signals as separate commands or decode recorded audio.

No processing upload or stored message history is used. Translation and tone generation run in your browser; audio uses our existing local WAV encoder. Website ads and analytics follow the privacy information.