Morse converter
What Is Morse Code? The Original Digital Communication
Morse code is a method of encoding text as sequences of short and long signals — dots and dashes (formally "dits" and "dahs") — developed in the 1830s–1840s by Samuel Morse and Alfred Vail for the electric telegraph. A Morse code converter translates in both directions: type English text to get Morse code, or paste Morse code to decode it back into readable text.
Before Morse, long-distance communication traveled at the speed of a horse. The telegraph collapsed continents to minutes, and Morse code was its language — the first widely-deployed digital encoding, nearly a century before "digital" meant computers. Operators learned to recognize letters by sound, and skilled telegraphists could carry on conversations at 20–40 words per minute, developing distinctive sending "fists" recognizable like voices. Maritime distress signaling made it legendary: SOS (···−−−···) — chosen not as an abbreviation but because the pattern is unmistakable — became the international distress call in 1908, and the final commercial Morse transmission, from a French naval station, didn't go silent until 1997.
The encoding itself is a study in elegant information design. Letters are built from 1–4 symbols, with the shortest codes assigned to the most frequent English letters — E is a single dot (·), T a single dash (−) — an early, intuitive form of data compression that predates Shannon's information theory by a century. Timing carries the structure: a dash is three dot-lengths, gaps between symbols within a letter are one dot-length, gaps between letters are three, and gaps between words are seven. Our converter handles the symbol translation; the timing rules matter when you're learning to send or recognize Morse by ear.
Today Morse survives in amateur (ham) radio — where it remains one of the most efficient weak-signal modes, punching through noise that buries voice transmissions — in aviation (navigational beacons still identify themselves in Morse), in assistive technology (sip-and-puff and single-switch interfaces), and in education and puzzles. Whether you're a radio student, a puzzle enthusiast, or just curious what your name sounds like in dots and dashes, the converter translates instantly in both directions. Input is processed instantly and never stored. For other classic encodings, try our binary converter, ASCII converter, or hex converter.
How to Use the Morse Code Converter
- Choose your direction. Select Text → Morse to encode, or Morse → Text to decode.
- Enter your input. Type or paste English text (letters, numbers, supported punctuation) for encoding; paste dot/dash sequences for decoding. For Morse input, separate letters with spaces and words with slashes or double spaces.
- Convert. The tool translates instantly — each character mapped through the International Morse code table.
- Listen (encoding mode). Use the play button to hear your text as audio tones, with correct dot/dash/letter/word timing — the fastest way to develop recognition.
- Copy or share. Copy the Morse output for puzzles, radio practice sheets, or messages; copy decoded text back into your document.
- Practice recognition. Decode without looking at the text first: play the audio, write down what you hear, then check against the decoded output.
The International Morse Code Table
| Char | Code | Char | Code | Char | Code |
|---|---|---|---|---|---|
| A | ·− | N | −· | 0 | −−−−− |
| B | −··· | O | −−− | 1 | ·−−−− |
| C | −·−· | P | ·−−· | 2 | ··−−− |
| D | −·· | Q | −−·− | 3 | ···−− |
| E | · | R | ·−· | 4 | ····− |
| F | ··−· | S | ··· | 5 | ····· |
| G | −−· | T | − | 6 | −···· |
| H | ···· | U | ··− | 7 | −−··· |
| I | ·· | V | ···− | 8 | −−−·· |
| J | ·−−− | W | ·−− | 9 | −−−−· |
| K | −·− | X | −··− | . | ·−·−·− |
| L | ·−·· | Y | −·−− | , | −−··−− |
| M | −− | Z | −−·· | ? | ··−−·· |
Common prosigns (procedural signals) worth knowing: SOS (···−−−···) for distress, AR (·−·−·) for end of message, SK (···−·−) for end of contact, and BT (−···−) as a separator within a message. Note the numbers' elegant pattern: 1 through 5 are dots-then-dashes counting up, 6 through 0 mirror them — a mnemonic that makes the digits the easiest part of the code to memorize.
Key Features
| Feature | What It Does | Why It Matters |
|---|---|---|
| Bidirectional conversion | Text → Morse and Morse → Text | Encode messages and decode puzzles with one tool |
| Audio playback | Plays the Morse as tones with correct timing | Learn recognition by ear, the way operators do |
| Adjustable speed (WPM) | Words-per-minute control for playback | Start slow (5 WPM), work up to conversational 20+ |
| Flexible Morse input | Accepts ./- and ·−/unicode variants, slash word separators | Paste Morse from any source without reformatting |
| Full character set | Letters, digits, and standard punctuation | Real messages, not just A–Z |
| Prosign support | Recognizes SOS, AR, SK, BT and others | Decode authentic radio-style traffic |
| Copy to clipboard | One-click copy of either direction | Drop results into documents and chats |
Learning Morse: A Practical Path
If the converter sparked an interest in actually learning the code, here's the method that works — and the trap to avoid. The trap is visual memorization: learning "A is dot-dash" as a picture. Visual learners can decode on paper but freeze when hearing it, because the brain stored the wrong representation. The working method is sound-first: learn each letter as a rhythm. A isn't "dot dash" — it's di-DAH. E is dit. Q is DAH-dah-di-DAH. Use the converter's audio playback from day one and associate letters with their sound patterns, never with dot-dash diagrams.
The standard progression: learn at full character speed with long gaps (the Farnsworth method) — characters sent at 15–20 WPM but spaced out. This teaches your ear the true rhythm of each letter instead of the slow, counted rhythm you'd have to unlearn later. Add letters in a sensible order (start with E, T, A, N — the highest-frequency letters — not alphabetical), practice 10–15 minutes daily, and decode real words as early as possible: random character drills build recognition, but words build fluency. Most learners reach functional 10–12 WPM copy in 4–8 weeks of daily practice; conversational 20 WPM takes several months. Ham radio operators consider the journey part of the hobby's charm — and the converter here doubles as your practice partner: encode a phrase, play it back, decode by ear, check your work.
Use Cases
For ham radio students: "The problem:" Morse proficiency for licensing and on-air confidence
The problem: You're studying for an amateur radio license or preparing for your first CW (continuous wave) contacts. You need to build recognition speed, but practice materials are scattered and you can't yet decode live traffic.
How this tool helps: Generate practice text at graduated speeds: encode common words and callsigns, play them back at increasing WPM, and decode by ear before checking. It's an infinite, free practice-text generator tuned to exactly your current speed — more flexible than fixed practice recordings.
For puzzle enthusiasts: "The problem:" a dots-and-dashes puzzle in an escape room or puzzle hunt
The problem: The puzzle gives you ·−· ··· −·−−·−· and expects an answer. You could look up each letter in a table, but that's slow and error-prone under time pressure.
How this tool helps: Paste the sequence into decode mode and get the answer instantly — including handling the slash-vs-space word separators that puzzle setters use inconsistently. For puzzle creators, the encode direction generates clean, correct Morse for clues (and the audio playback lets you make audio-based puzzles too).
For educators: "The problem:" making the history of communication tangible
The problem: You're teaching the telegraph, information theory, or WWII history, and "dots and dashes" as a textbook paragraph doesn't land. Students need to experience the encoding.
How this tool helps: Have students encode their names, play them back, and decode each other's — then discuss why E is one dot (frequency-based design, a century before Huffman coding). It's a ten-minute activity that makes abstract ideas about encoding and compression concrete, and it works from elementary school through university.
For developers: "The problem:" Morse as an easter egg or accessibility experiment
The problem: You're building a novelty feature — a "send as Morse" easter egg, a vibration-pattern encoder for a wearable experiment, or a single-switch assistive interface prototype — and you need a correct reference implementation of the code table.
How this tool helps: Use the converter to generate verified test vectors: encode known strings here and assert your implementation produces identical output. The timing rules (1/3/7 unit gaps) documented above give you the playback spec. For related encodings in your project, our binary converter and ASCII converter provide the same reference role.
For writers: "The problem:" authentic Morse in fiction
The problem: Your story includes a telegraph scene, a wartime radio operator, or a stranded character signaling for help — and readers who know Morse will fact-check you.
How this tool helps: Encode the actual message your character sends and quote the real code. Getting SOS right is table stakes; getting a full authentic exchange right (including prosigns like AR for end-of-message) is what earns the nod from knowledgeable readers. The timing notes above keep your described sending realistic too.
Decoding From Imperfect Sources: A Field Guide
Textbook Morse arrives as clean dot-dash groups. Real-world Morse — the kind in puzzles, films, and historical recordings — rarely cooperates. Here's how to handle the common degradations:
Ambiguous word spacing. The most frequent problem: is that gap a letter space or a word space? When decoding, first try the reading that produces real words — human language is highly redundant, and usually only one segmentation yields sensible text. Puzzle setters know this and rely on it; if two segmentations both produce words, look for which one fits the puzzle's theme.
Missing or extra symbols. A single dropped dot turns one letter into another (H ···· vs S ···). When a decode produces near-words ("HELLO WORLB"), assume transmission error and try minimal corrections — flip one symbol at a time. Authentic historical traffic is full of such errors; operators corrected from context exactly this way.
Non-standard representations. Puzzles render Morse as long/short beeps, flashing lights, taps, raised vs. lowered flags, even long and short noodles in one famous puzzle-hunt case. The translation step is always the same: map the two durations to dot and dash, segment by the timing ratios, then decode normally. Our decoder's flexible input (accepting ./-, ·−, and unicode variants) covers the textual encodings; for audio or visual sources, transcribe to dots and dashes first.
Unknown prosigns. Strings like ·−·−· (AR) or ···−·− (SK) aren't in the letter table — they're procedural signals. A decode that ends in gibberish often just needs its final group recognized as a prosign rather than letters. When in doubt, check the decoded-then-unrecognized groups against the prosign list before assuming corruption.
Morse Code in Popular Culture
Morse has a second career as storytelling shorthand for ingenuity under pressure. Films use it for prisoners tapping on walls (a real technique — the tap code, a grid-based relative of Morse, was used by POWs in Vietnam), for dramatic radio scenes, and as an easter egg layer: several hit songs hide Morse messages in their intros, and video games from Metal Gear to Portal embed Morse puzzles that sent communities scrambling for decoders. The pattern's recognizability is the point — even audiences who can't decode it understand that dots and dashes mean someone clever is communicating against the odds.
Creators planting these easter eggs use exactly this kind of converter to generate them: encode the hidden message, verify it decodes cleanly, then render it as audio, blinking lights, or visual patterns. If you're building one, test the full round trip — encode here, then decode the result without looking at the original — because an easter egg nobody can solve is just noise, while one that's solvable with effort becomes legend.
One last tip for the curious: try encoding your own name and listening to it at 20 WPM — then slow it to 8 WPM and notice how the rhythm changes from a recognizable "word" into countable parts. That perceptual shift, from counting to hearing, is the entire journey of learning Morse in miniature. Everything after that is just vocabulary.
Frequently Asked Questions
What do the dots and dashes officially mean?
A dot ("dit") is one time unit; a dash ("dah") is three units. Within a letter, symbols are separated by one unit of silence; letters by three units; words by seven. These timing ratios are part of the International Morse standard — without them, a stream of dits and dahs can't be segmented into letters.
Is SOS really "save our souls"?
No — that's a backronym. SOS was chosen purely because ···−−−··· is distinctive and hard to mistake, adopted internationally in 1908. The letters don't officially stand for anything, which is also why it's written as a single prosign (···−−−···) rather than three separate letters.
Do I need to learn Morse for a ham radio license?
Not anymore in most countries — the US dropped the Morse requirement in 2007, and most administrations followed. But Morse (CW) remains hugely popular on the air: it's the most power-efficient mode, works through terrible conditions, and has a devoted community. Many hams learn it voluntarily after licensing.
What's a good speed to start learning at?
Learn characters at full speed (15–20 WPM character rate) with stretched spacing between them — the Farnsworth method. Starting at a slow 5 WPM character rate teaches a "counting" habit you'll have to unlearn. Use the playback speed control here to implement exactly this.
Can Morse code handle lowercase or non-English characters?
International Morse is caseless — no distinction between upper and lower. Extended characters exist for some languages (e.g., German umlauts, Spanish ñ have defined codes), but the core standard covers A–Z, 0–9, and punctuation. Our converter maps input case-insensitively to the standard table.
How should I format Morse when typing it?
Common conventions: dots and dashes (or ./-) for symbols, a space between letters, and a slash or double space between words — e.g., "... --- ..." for SOS as one "word," or ".... . .-.. .-.. --- / .-- --- .-. .-.. -.." for "hello world." The decoder here accepts the common variants.
What's the difference between American and International Morse?
American (Railroad) Morse, the original 1840s code, had different timings and intra-character gaps; International Morse (standardized 1865) replaced it almost everywhere. Unless you're reading Civil War-era telegraph tapes, International is the code — it's what this converter implements.
Can I use Morse code for secret messages?
It's an encoding, not encryption — anyone who recognizes it can read it, and decoders like this one are everywhere. For fun puzzles and easter eggs it's perfect; for actual secrecy, use real cryptography. (That said, Morse as audio in a noisy environment is surprisingly inconspicuous.)
Why do aviation beacons still use Morse?
VOR and NDB navigational beacons identify themselves with Morse callsigns because the mode is trivially simple to generate and decode, works over enormous ranges, and needs no digital infrastructure at the receiver — a pilot can identify a beacon by ear with basic training. It's a 19th-century technology still earning its keep.
Is my input stored when I use this tool?
No. Text and Morse input are converted instantly and never stored on the server.