The first time Morse code stopped being a curiosity for me was on a small boat with a dying phone and a signal light. I knew "SOS" was three short, three long, three short, and that was the entire extent of my knowledge - enough to feel useful and nowhere near enough to send anything else. Later, curious, I sat down to write my name in dots and dashes and realized I had no idea where one letter ended and the next began, or how you were supposed to mark a space between words. The dots and dashes are the easy part. The gaps are where people get lost.
TL;DR: The Morse Code Translator converts plain text to International Morse code and decodes Morse back to text, using the standard letter and word spacing so your output is unambiguous. It plays the result as audio beeps at an adjustable speed, flags characters it cannot encode, and runs entirely in your browser - no account, no upload.
I built this tool for toolz.dev because the existing translators I found either mangled the spacing, silently dropped characters they did not recognize, or gave you dots and dashes with no way to actually hear them. Morse is a sound-and-light code first and a written one second, so a translator that cannot play the message back is only doing half the job. This guide covers how Morse code is structured, the spacing rules that make or break a message, and how to use the translator to encode, decode, and listen.
What is a Morse code translator?
A Morse code translator converts between ordinary text and Morse code - the system of short and long signals that carried the world's messages by telegraph, radio, and signal lamp for over a century. The timings and the character set are not folklore: ITU-R M.1677-1 defines International Morse code, down to the length of a dash relative to a dot. Each letter, digit, and common punctuation mark maps to a unique sequence of dots (short signals, called "dits") and dashes (long signals, "dahs"). The letter E is a single dot. The letter T is a single dash. SOS is ... --- .... A translator does this mapping in both directions: text in, dots and dashes out, or dots and dashes in, text out.
The tool on toolz.dev uses International Morse Code, the standard defined by the ITU and used worldwide for amateur radio, aviation, and maritime signalling. That matters because there is more than one Morse. The older American Morse, used on 19th-century American railroad and landline telegraphs, had different patterns for several letters and used internal spaces inside some characters. It is effectively extinct outside historical reenactment. When someone says "Morse code" today, they mean International Morse, and that is what this translator encodes and decodes.
Here is the structure the tool follows, which is the same structure every standards-compliant Morse tool uses:
| Element | Length | How it is written here |
|---|---|---|
| Dot (dit) | 1 unit | . |
| Dash (dah) | 3 units | - |
| Gap between dots/dashes in a letter | 1 unit | (no character) |
| Gap between letters | 3 units | a single space |
| Gap between words | 7 units | a slash / |
Why the gaps matter more than the dots
Anyone can look up that A is .-. The reason Morse trips people up is that the timing of the silences carries as much information as the signals. Within a single letter, the parts are separated by one unit of silence. Between letters, the gap stretches to three units. Between words, it is seven. Get those gaps wrong and ... --- ... - three letters, S O S - collapses into an unreadable smear or splits into the wrong letters entirely.
This is exactly where a translator earns its keep. When you encode text, the tool inserts a single space between letters and a slash between words automatically, so the output is always unambiguous. SOS becomes ... --- ... with clear letter gaps, and SOS HELP becomes ... --- ... / .... . .-.. .--. with the word break marked. You never have to count units in your head.
When you decode, the tool accepts either convention for word breaks - a slash, or a run of three or more spaces - because pasted Morse comes formatted both ways. It splits each word into letter tokens on the single spaces, looks up each token, and rebuilds the text. If a token does not match any Morse character, it is flagged rather than silently dropped, so you know exactly where a stray dot crept in. That single design choice - surfacing the error instead of hiding it - is the difference between a tool you can trust and one that quietly lies to you.
How to use the Morse Code Translator
Step 1: Choose your direction
Pick "Text to Morse" to encode, or "Morse to Text" to decode. There is also a Swap button that flips the direction and feeds the current output back as the new input, which is the fastest way to round-trip a message and confirm it survives the trip intact. If you encode "HELLO" and swap, you should get "HELLO" back - if you do not, something in the spacing is off.
Step 2: Enter your message
Type or paste into the input box. When encoding, type normal text; case does not matter, since Morse has no distinction between upper and lower case. When decoding, paste your dots and dashes, separating letters with spaces and words with a slash or extra spaces. The tool normalizes common look-alike characters - the en dash, em dash, and Unicode minus all become a hyphen, and middle dots and bullets become a period - so Morse copied from a document or chat still decodes.
Step 3: Read the live result and the counts
The converted output appears instantly below the input, along with a character and word count. If you are encoding text that contains a character with no Morse equivalent - an em dash, a tilde, a curly quote - the tool lists it in a note rather than pretending it encoded something. Nothing disappears without telling you.
Step 4: Play it as sound
Press Play to hear the message as authentic beeps: short tones for dots, long tones for dashes, with the correct gaps between letters and words. Use the speed slider to set the pace in words per minute (WPM). This is the part most translators skip, and it is the part that makes Morse click. Reading -.-. tells you nothing about the rhythm of the letter C; hearing "dah-di-dah-dit" does. If you are practicing to copy Morse by ear for an amateur radio exam, the audio at a controlled WPM is the whole point.
The speed question: what WPM actually means
Morse speed is measured in words per minute, and the reference "word" is PARIS - chosen because its dot-dash count is close to the average English word. The timing is anchored to a single unit whose duration in seconds is 1.2 / WPM. At 15 WPM, one unit is 80 milliseconds; a dot lasts 80ms, a dash 240ms, a letter gap 240ms, and a word gap 560ms. The translator's audio uses exactly this relationship, so the beeps you hear match the standard timing at whatever speed you set.
Beginners usually start slow, around 5 to 8 WPM, to have time to recognize each character. The catch is that very slow Morse encourages counting individual dots and dashes rather than hearing whole letters as rhythms, a habit that becomes a wall around 10 WPM. Many learners use a compromise where characters are sent fast but the gaps between them are stretched, giving thinking time without teaching bad habits. This tool keeps the standard proportional timing, which is ideal once you are comfortable reading characters as sounds rather than counting their parts.
Common use cases
Learning and amateur radio practice. If you are studying for a ham radio license or just learning the code, encoding text and listening at a set WPM builds the ear you need. Start with common words, listen, then decode a message someone else sent to test yourself. The audio is the teacher here.
Puzzles, games, and escape rooms. Morse is a staple of puzzle hunts, ARGs, and escape rooms. When you find -- . . - scratched into a prop, paste it in, decode it, and move on. The error flagging helps when the puzzle's Morse was hand-made and slightly off.
Geocaching and scouting. Morse appears constantly in geocache clues and scouting activities. Encoding a clue to hide or decoding one you found is a two-second job, and hearing it played back helps when the clue was meant to be flashed or tapped rather than written.
Accessibility and signalling. Morse remains a genuine fallback communication method - it can be sent by sound, light, tap, or a single blinking eye, which is why it still appears in accessibility contexts. Encoding a phrase to signal is a legitimate, practical use, not just a novelty.
Curiosity. Sometimes you just want to see and hear your name, a message, or I LOVE YOU (.. / .-.. --- ...- . / -.-- --- ..-) in dots and dashes. That is a perfectly good reason, and it is how most people start.
Text, binary, and Morse: three ways to encode
Morse is one of several ways to represent text as something other than letters, and it sits alongside the other encoders on toolz.dev. Where the binary translator represents each character as its numeric byte value in base 2, 8, 10, or 16, Morse represents each character as a rhythm of short and long signals designed for transmission by a human over a noisy channel. They solve different problems: binary is about how a computer stores a character, Morse is about how a person sends one by ear or eye. If you are exploring how the same message looks across encodings, the number base converter and base64 converter round out the set, each showing a different lens on the same underlying text. Morse is the oldest of the four and the only one meant to be heard.
What Morse can and cannot represent
Standard International Morse covers the 26 letters, the ten digits, and a defined set of punctuation: period, comma, question mark, apostrophe, exclamation mark, slash, parentheses, ampersand, colon, semicolon, equals, plus, hyphen, underscore, quotation mark, dollar sign, and at sign. The at sign (.--.-.) was the most recent official addition, adopted in 2004 for email addresses - a reminder that the standard still evolves. Characters outside this set have no official Morse form, and the translator will tell you when it skips one rather than inventing a pattern.
Accented letters and non-Latin scripts are the main limitation. Various national variants exist - there are extensions for accented European letters, Greek, Cyrillic, Japanese (Wabun code), and more - but they are not part of the core International standard and are not universally understood. This tool sticks to the International standard set, which is what any operator anywhere will recognize, rather than guessing at a national extension the recipient may not know. When you encode text with accents, the base letters that do have Morse encode normally and the accented ones are flagged, so you can decide how to handle them.
Privacy: it all runs in your browser
There is nothing to upload here, and nothing is uploaded. Encoding, decoding, and audio playback all happen in client-side code running in your browser. That is a deliberate choice, and an easy one to verify: disconnect from the internet and the translator keeps working, dots, dashes, and beeps included. Your messages - whether a practice phrase, a puzzle answer, or something you would rather keep private - never touch a server or a log. This is the same client-side principle behind every tool on toolz.dev, which I make the full case for in the data privacy in online tools article, and which shapes the whole web developer toolkit approach.
FAQ
How do I translate text to Morse code?
Choose "Text to Morse" and type your message into the input box. Each character is converted to its International Morse pattern, with letters separated by a single space and words by a slash. For example, HELLO becomes .... . .-.. .-.. ---. The result updates as you type and can be copied or played as audio beeps with one click.
What is SOS in Morse code?
SOS is ... --- ... - three dots, three dashes, three dots - sent as one continuous signal with no gaps between the three letters. It was chosen as the international distress call because the pattern is simple, symmetrical, and hard to mistake for anything else. Type SOS into the translator and you get exactly that sequence.
How are letters and words separated in Morse code?
Within a letter, the dots and dashes are separated by one unit of silence. Letters are separated by a gap of three units, written here as a single space, and words are separated by a gap of seven units, written as a slash. Getting these gaps right is what keeps a message readable; the translator inserts them automatically when you encode.
Does the translator support numbers and punctuation?
Yes. It covers all ten digits and the standard International punctuation set, including period, comma, question mark, exclamation mark, slash, parentheses, colon, ampersand, and the at sign. Characters with no official Morse form, such as some symbols and accented letters, are skipped and listed so you know they were left out rather than silently dropped.
Can I hear the Morse code as sound?
Yes. After translating text to Morse, press Play to hear it as beeps, with dots as short tones and dashes as long tones, spaced correctly between letters and words. A slider sets the speed in words per minute. Hearing the rhythm is the fastest way to learn the code and is essential if you are practicing to copy Morse by ear.
What is the difference between International and American Morse code?
International Morse Code, also called Continental Morse, is the modern worldwide standard used for radio, aviation, and maritime signalling, and it is what this tool uses. American Morse was an older variant used on 19th-century American telegraph lines, with different patterns for several letters and internal spaces in some characters. It is essentially obsolete today, so for any current use International Morse is the correct choice.
Why won't some characters convert?
Standard International Morse only defines codes for letters, digits, and a specific set of punctuation. If your text contains a character outside that set - an em dash, a tilde, a curly quotation mark, or an accented letter - there is no official Morse for it, so the tool skips it and lists it in a note. This keeps the output honest rather than inventing a pattern the recipient would not recognize.
Is it safe to translate private messages here?
Yes. Every conversion and the audio playback run entirely in your browser with client-side code. Nothing you type is uploaded, stored, or logged, and the tool keeps working with your connection disabled. You can safely translate private notes, names, or messages.
