This tool runs locally in your browser.
Results are estimates based on your input only; entered values and result contents are not stored by BoringToolsKit.
Your inputs and results stay in this browser. This page may send privacy-bounded aggregate interaction events described in Privacy; it does not send your entered values or result contents.
Use this result
Share the current inputs or ask ChatGPT to explain the calculation in context.
More options
What does this tool show?
Morse code converter: translate text into international Morse code, or decode dots and dashes back into text instantly. Free, private, in-browser, no signup.
- Morse encodes case-insensitively and has no accents — diacritics map to their base letter.
- Timing matters in audio: dot = 1 unit, dash = 3 units, gaps of 1/3/7 units between elements/letters/words.
When this tool earns its keep
Use it when you need encoding text to Morse for radio practice, teaching, and novelty use — encoding text to Morse repeatedly or once, with the result ready to copy. Pair it with its related tools below when the output feeds the next step.
How this calculator works
Formula
Each character is replaced by its ITU Morse pattern; words are separated by "/" and letters by a single space. For example SOS = ... --- ...
Site methodology
This page does not cite an external source yet. The link above documents how we build and check calculators; it is our own process, not third-party validation. Treat the inputs and results as editable estimates.
Assumptions to verify
- Input format is assumed clean; malformed input is reported rather than guessed at.
- Output is computed client-side and stays in your browser.
Frequently asked questions
Is anything sent to a server?
No. The transform runs in your browser; nothing you paste leaves the page.
What is the honest limitation?
It is mechanical, not judgmental: the tool guarantees format correctness, not fitness for your context — skim the output before shipping it.
Cite this tool
BoringToolsKit. “Morse Code Converter.” boringtoolskit.com/morse-code-converter/ (reviewed 2026-09-20). Free to reference in articles, syllabi, and answer posts with a link.
Privacy: Inputs and results stay in this browser. Results are estimates based on your input only; nothing you enter is stored by BoringToolsKit.
A worked example: converting HI, with the exact audio schedule
Type HI and the converter outputs .... .. : H is four dots, I is two dots. The input is uppercased, each character is looked up, and the space between words would become a slash, so HI THERE becomes .... .. / - .... . .-. .
The numbers matter if you press Play. The audio player uses a fixed unit of 0.09 seconds: a dot lasts 0.09s, a dash three units (0.27s), the gap inside a letter 0.09s, the gap between letters 0.27s, and the gap between words 0.63s. For HI, playback starts at 0.1s. H contributes four dots, each advancing the clock by dot-plus-gap = 0.18s, so 0.72s. The inter-letter gap adds a further 0.18s (0.27s gap minus the 0.09s already counted). I adds two dots = 0.36s. The clock ends at 1.36s, and playback is cleaned up about 0.2s later, so the whole word takes under 1.6 seconds.
That 0.09s unit also fixes the speed: the standard word PARIS spans 50 units, so 1.2 / 0.09 gives roughly 13 words per minute. This is on the slow, learnable side; real hams often copy 20 to 30 wpm, where a dot drops below 60 milliseconds. The tone itself is a 620 Hz sine with 12 ms fade ramps on both ends of every element, which removes the clicks a hard on-off switch would produce.
What the converter will not do: boundary cases worth knowing
The character map holds 54 entries: 26 letters, 10 digits, and 18 punctuation marks (. , ? ' ! / ( ) & : ; = + - _ " $ @). Anything outside that set is dropped silently rather than flagged: an accented e, a curly quote, or an emoji simply produces no output element. Lowercase is fine because everything is uppercased first, but Unicode text such as cafe will come out as -.. .- ..-. . with the accent lost and no warning.
Spacing is normalized, not preserved. Runs of whitespace collapse: three spaces between words still render as a single slash, and leading or trailing spaces vanish entirely. The filter also trims empty elements at the string edges, so pasting text with stray newlines will not leave dangling gaps in the output.
The audio path has its own fixed settings. There is no speed control (the 0.09s unit is hard-coded, about 13 wpm), no pitch control (620 Hz only, near the 600 Hz convention most operators prefer), and no way to pause mid-playback; the Stop button closes the whole audio context and restarts from zero on the next Play. Long text also produces long audio at a fixed ratio of roughly 1 second per three characters, so a 300-character paragraph takes about 100 seconds to play, and some browsers cap or throttle long-running audio contexts in background tabs. For decoding morse back into text, this tool is one-directional: it encodes only.