Morse code translator

Encode text to ITU Morse dots and dashes or decode locally.

{{ t("morseHint") }}

Overview

Before the electric telegraph, news traveled at the speed of a horse — roughly 15 kilometers per hour for a well-mounted messenger. The first large network for rapid information transmission was the optical signaling tower system developed by French priest Claude Chappe in 1792, capable of transmitting a message from Paris to Lille (225 km) in just two minutes. But the real revolution came with the electric telegraph, patented in the United States by Samuel Morse in 1837 and in England by Charles Wheatstone around the same time. On May 24, 1844, Morse sent the first long-distance telegraph message between Washington and Baltimore: `What hath God wrought` — a biblical quotation from the Book of Numbers, chosen by Annie Ellsworth, daughter of the US Patent Commissioner. The world was never the same again: for the first time in human history, a message could travel faster than its messenger.

The Morse code we know today — dots and dashes — was developed in partnership with Alfred Vail, the engineer who built the practical telegraph equipment. The assignment of codes to each letter was not arbitrary: Morse and Vail visited a local print shop and counted the frequency of letter types available to see which letters were most used in English. The result was a variable-length encoding ahead of its time: the letter `E`, the most frequent, gets the shortest possible code — a single dot. `T` gets a single dash. `Q` and `Z`, rarely used, get long codes of four symbols. The ITU (International Telecommunication Union) standardized International Morse in 1865, adding accented European characters and establishing precise timing: one dot equals one unit, a dash equals three, the gap between symbols of the same letter is one unit, between letters is three, and between words is seven.

Morse code survived the 20th century with surprising vitality. The SOS distress signal (... --- ...) was adopted internationally in 1908 because its patterns are impossible to confuse: three dots, three dashes, three dots — unambiguous even in poor signal conditions. Aviation used Morse for radio navigation aid identification for decades — VORs and NDBs transmitted (and some still transmit) their identifier in Morse code. Amateur radio continues to use Morse, and knowledge of the code remains a licensing requirement in several countries. More recently, in 2018, Google added Morse code input to the Gboard keyboard as an accessibility feature, allowing people with limited mobility to operate a smartphone with just two contacts — one for dot, one for dash. Morse, born to transmit commercial dispatches over telegraph wire, ended up as an accessibility interface in the 21st century.

Technical deep dive

Common questions summarized

  • What is this tool for?: It runs fully in your browser: useful to validate, format, or convert data in everyday development.
  • Are my inputs sent to a server?: Processing happens locally with JavaScript. We do not store what you paste into the text areas.
  • Can I use this for real production data?: Use at your own risk. For secrets (passwords, tokens), prefer controlled environments and your company policies. And always review the generated contents. Never trust blindly things you see on the internet.

Sample payload to try

  • See also the larger "Code Snippets" sample; paste this excerpt to try locally: SOS — Texto: SOS Morse: ... --- ...

Tool guide

  • What Morse code is A way to encode letters and digits with dot and dash patterns, historically central to radio. The ITU Latin set is the usual reference.

  • What the tool does Encodes text (A–Z, 0–9 and some punctuation) with spaces between letters and / between words, or decodes Morse-like input back to text.

  • Why use it Learning, puzzles, and quick demos without installing apps.

Code Snippets

Code example
Texto: SOS
Morse: ... --- ...

SOS

Texto: SOS
Morse: ... --- ...

FAQ

What is this tool for?

It runs fully in your browser: useful to validate, format, or convert data in everyday development.

Are my inputs sent to a server?

Processing happens locally with JavaScript. We do not store what you paste into the text areas.

Can I use this for real production data?

Use at your own risk. For secrets (passwords, tokens), prefer controlled environments and your company policies. And always review the generated contents. Never trust blindly things you see on the internet.