About inMorse

inMorse has one goal: make Morse code accessible to anyone with a browser. You might be here for a ham-radio license, a school assignment, a puzzle in a video game, or just plain curiosity. Either way, this site gives you the cleanest, fastest Morse experience on the web.

The translator runs entirely in your browser. There is no backend that stores what you type. The audio engine uses the Web Audio API to generate pure-tone Morse on the fly, with adjustable WPM, frequency, and waveform so you can train your ear at your own pace. The learning hub breaks the alphabet into digestible chunks, and the advanced tools cover everything from a binary converter to an image-based decoder.

inMorse is an independent project, not a venture-backed startup. It is built by people who actually use Morse code on the air and got tired of clunky, ad-heavy tools that look like they were last redesigned in 2007. So we built our own.

Every existing Morse code translator on the web fell into one of two camps. The first was the “textarea on a page” school: a plain HTML form that converted text to dots and dashes and stopped there. No audio. No flash. No learning path. The second camp was the opposite: heavy, ad-stuffed portal sites that buried the actual translator below a wall of SEO copy and pop-ups.

Neither felt right. Morse code is fundamentally an auditory and visual language. Dots and dashes were designed to be heard as tones or seen as flashes, not read as text on a screen. A modern Morse tool should make the sound first-class, make the rhythm adjustable, and make the alphabet chart just a scroll away.

That is what inMorse is: a translator that plays audio, an audio engine that flashes light, a learning hub that gives you the chart and the practice mode side by side, and a tools page for the weird stuff (binary, SOS, image decoding). Everything runs in one browser tab, free, with no server round-trips.

To keep Morse code alive, useful, and welcoming for the next generation of operators, learners, and makers. Morse has been in continuous use since 1844 and still finds new uses, from accessibility input methods to hidden jewellery engravings to emergency signalling. We want the tools around it to feel as timeless as the code itself.

In practice, that means three things: keep the core tool free forever, keep adding genuinely useful features (not bloat), and keep the privacy policy short enough to actually read. If you have an idea for something inMorse should do that it does not do yet, tell us.

Every article on the inMorse blog is written and reviewed by the inMorse Team, a small group of amateur radio operators, CW enthusiasts, and educators. We have spent years working with Morse code on the air, in the classroom, and in assistive technology.

Our editorial process is straightforward. We research primary sources (ITU recommendations, ARRL handbooks, historical archives), verify every Morse code sequence against the International Morse Code standard, and test every tool feature we write about. When we get something wrong, we fix it and note the correction in the article's updated date.

We don't use AI-generated content without human review, we don't accept paid placements in our articles, and we don't recommend tools we haven't tried ourselves. If you spot an error or have a topic suggestion, reach out.