Morse Code Translator — Text to Morse & Morse to Text

The Morse code translator below converts plain text into International Morse code and decodes Morse code back into readable letters and numbers, instantly and entirely in your browser. Type a sentence, and every letter, digit, and common punctuation mark is mapped to its correct sequence of dots and dashes; paste in Morse code, and the tool reverses the process to hand you back plain text. There is also a built-in audio player that beeps out the actual dot-dash-and-pause timing through the Web Audio API, so you can listen to a message the way an operator on a telegraph key or an amateur radio net would hear it.

Arb Digital built this Morse code translator as one of a growing set of free browser utilities for developers, students, and hobbyists — no installs, no ads blocking the workflow, no data leaving your machine. It supports the full A–Z alphabet, digits 0–9, and the punctuation marks most people actually need, plus configurable separators so the output matches whatever format your project, homework assignment, or ham radio study guide expects.

What This Morse Code Translator Does

At its core, this is a two-way Morse code converter. Choose "Text → Morse code" to encode any sentence you type, or "Morse code → Text" to decode a string of dots and dashes back into words. The translation happens character by character using the standard International Morse code table — the same table maintained by international telecommunication standards bodies — so output here matches what you'd get from a certified operator or a textbook reference. Because everything runs in JavaScript inside your own browser tab, there's no server round-trip, no upload, and no delay: results update as you type.

Beyond plain conversion, the tool includes an audio playback feature. Click "Play Morse Audio" and an oscillator built with the Web Audio API beeps out your translated message using correct relative dot, dash, and pause timing at the words-per-minute speed you choose. This is genuinely useful for practicing Morse code by ear rather than by eye — reading dots and dashes on a screen and recognizing the same pattern as a sound are different skills, and many people preparing for amateur radio licensing or simply learning Morse for fun need both.

How to Use the Morse Code Translator

1. Pick a direction. Select "Text → Morse code" to encode, or "Morse code → Text" to decode. The input label updates to match.
2. Type or paste your content. For text-to-Morse, type any sentence. For Morse-to-text, paste dots and dashes separated by spaces, with a slash or extra space between words.
3. Adjust separators if needed. Some references use a single space between letters and a slash between words; others use pipes or triple spaces. Pick whichever matches your use case — a classroom worksheet, a coding challenge, or a ham radio logbook.
4. Read the result. The translated output appears instantly in the highlighted box and the read-only text area below it, ready to copy.
5. Copy the output. Click "Copy result" to copy the translation to your clipboard for pasting elsewhere.
6. Listen to it. Set a words-per-minute speed and tone pitch, then click "Play Morse Audio" to hear your message beeped out with accurate timing.

Morse Code Timing: The Formula Behind the Sound

Morse code is built entirely from one base unit of time, conventionally called a "dit" length. Every other element is a multiple of that single unit: a dot (dit) lasts one unit, a dash (dah) lasts three units, the gap between dots and dashes within one letter is one unit, the gap between two letters is three units, and the gap between two words is seven units. This elegant ratio system is what makes Morse code decodable purely by ear — a trained listener doesn't need to see dots and dashes, only to perceive short and long sounds separated by short and long silences.

Speed is measured in words per minute (WPM), calibrated against a standard reference word (commonly "PARIS", which has a known, fixed number of dit-units). At higher WPM, the dit unit shrinks proportionally so every element gets faster while keeping the same 1:3:1:3:7 ratio. This tool calculates the dit length in milliseconds directly from your chosen WPM using that same PARIS-standard formula, which is why the audio playback sounds authentic rather than arbitrarily timed. For the full technical specification of these timing ratios and the history of the standard, the ITU-R M.1677 International Morse Code recommendation is the authoritative reference used worldwide.

Why Morse Code Still Matters

Samuel Morse and Alfred Vail developed the code in the 1830s and 1840s for the electric telegraph, and it later became the backbone of early radio communication because a simple on/off tone is far easier to transmit reliably over noisy, low-bandwidth channels than voice. Even today, Morse code (CW, for "continuous wave," in amateur radio jargon) remains popular among ham radio operators because it can punch through weak signals and interference where voice communication fails completely — a skilled CW operator can often maintain contact at power levels or distances where SSB voice would be unreadable.

Morse code also survives in aviation (VOR and NDB navigation beacons still identify themselves in Morse), maritime distress signaling (SOS — three dots, three dashes, three dots — remains globally recognized even outside radio contexts), and as an accessibility tool: some assistive technology lets users with severe motor impairments communicate by tapping Morse code through a single switch. Learning to encode and decode it, even casually, connects you to over 180 years of communication history.

Reading and Writing Morse by Hand

If you're learning Morse code rather than just converting a one-off message, a few practical habits help. Start with the highest-frequency letters in English — E (a single dot) and T (a single dash) — before moving to less common letters. Practice recognizing whole letter-sounds rather than counting individual dots and dashes; experienced operators hear "dit-dah" as the single sound "A," not as two separate beeps to be counted. Use this translator to check your own hand-decoded attempts: type what you think a sequence says, translate it to Morse, and compare against the original to catch mistakes.

Common characters and their codes, for quick reference:

• E = ·    T = −    A = ·−    N = −·
• S = ···    O = −−− (together, the SOS distress call: ···−−−···)
• Numbers 1–9 follow a clean pattern: 1 = ·−−−−, 5 = ·····, 9 = −−−−·, 0 = −−−−−
• Period = ·−·−·−    Comma = −−··−−    Question mark = ··−−··

Common Mistakes to Avoid

• Forgetting word gaps. When typing Morse manually to decode, using the same spacing between letters and words merges everything into one long unreadable string. Use a slash or extra space to mark word boundaries clearly.
• Mixing separator styles mid-string. Pick one letter separator and one word separator and stay consistent, or the decoder can misread boundaries.
• Assuming Morse covers every character. Standard International Morse code covers the Latin alphabet, digits, and common punctuation — it doesn't have native codes for arbitrary symbols like currency signs or non-Latin scripts. Unsupported characters are skipped and flagged rather than silently guessed.
• Confusing dit/dah ratio with real-world spacing. If you're timing Morse by hand (e.g., tapping a switch), remember the 1:3 dot-to-dash ratio — inconsistent timing is the most common reason hand-sent Morse becomes unreadable.

Prosigns and Special Morse Procedures

Beyond individual letters and digits, Morse code operators traditionally use "prosigns" — procedural signals sent as if they were single characters, formed by running two letters together without the usual inter-letter gap. The most famous is SOS itself, which despite popular belief is not an acronym for anything; it was chosen in 1906 specifically because ···−−−··· is simple, unmistakable, and hard to confuse with any other letter combination, even under poor signal conditions. Other common prosigns include AR (end of message), SK (end of contact, "silent key"), and BT (break, used like a paragraph break in a longer transmission). This translator focuses on straightforward character-by-character conversion rather than prosign handling, since prosigns are a layer of operating convention on top of the base alphabet rather than part of the character set itself — but recognizing them helps when reading real historical or amateur radio Morse traffic, where a prosign appears as a run-together group with no internal letter spacing.

Another practical nuance: amateur radio operators often insert a slight variation in timing called "Farnsworth spacing," where individual dots and dashes are sent at a faster character speed while the gaps between letters and words are stretched out longer than the standard ratio. This technique, named after its creator, helps beginners learn to recognize whole-letter sound patterns at a natural pace without the frustration of trying to count individual slow dots and dashes. This tool's playback uses standard proportional timing rather than Farnsworth spacing, which is the more common reference point for text-to-Morse conversion tools and matches what you'll see in most Morse code reference tables and telegraphy textbooks.

Related Free Tools From Arb Digital

Working with text encoding often means jumping between formats. Try our Base64 Encoder & Decoder for binary-safe text encoding, the Text to Binary Converter for another classic encoding scheme, the Unicode Character Converter to inspect code points in any string, the ROT13 Encoder & Decoder for simple letter-shift obfuscation, and the Hash Generator for SHA-256 and other cryptographic hashes. Browse everything in our free online tools hub.

Frequently Asked Questions

This tool runs entirely in your browser — nothing you type or convert is uploaded or stored anywhere.