Morse Code Translator: Dots and Dashes, Instantly
Morse code maps every letter and number to a sequence of dots (.) and dashes (-). SOS is ... --- .... HELLO is .... . .-.. .-.. ---. It's been around since the 1830s and it still shows up — in CTF challenges, escape rooms, amateur radio, and the occasional nerdy tattoo.
This tool translates text to Morse code and Morse code back to text. Uses standard ITU International Morse Code. Paste in either direction.
Runs in your browser. Nothing leaves your machine.
What's actually happening
The tool uses a hardcoded lookup table mapping every letter (A-Z), digit (0-9), and common punctuation marks to their ITU Morse code equivalents.
Encoding: each character in your input is looked up in the table. Characters are separated by spaces. Words are separated by /. Unknown characters (like emoji or CJK) are silently dropped.
Decoding: the input is split by / for words and spaces for characters. Each Morse sequence is looked up in a reverse map to find the original character. Invalid Morse sequences throw an error.
The mapping is one-to-one for supported characters. A is always .-. 1 is always .----. No ambiguity.
Using it
Pick Encode or Decode. Type or paste your input. The output updates instantly. Hit Copy. The toggle button swaps your input and output and flips the direction — handy for verifying a round-trip.
When you'd actually reach for this
- You're solving a CTF challenge or puzzle that uses Morse code as an encoding layer
- You're building an escape room or puzzle game and need Morse-encoded clues
- You're learning Morse for amateur radio (ham radio) and want to practice
- You're decoding Morse from a movie, game, or viral video
- You need a simple encoding for a creative project — Morse looks cool in design and typography
Why Morse code still matters
Morse code is arguably the simplest digital encoding ever invented. It predates computers, ASCII, and Unicode by over a century. It's still used in:
Amateur radio — licensed operators still use Morse (called CW — continuous wave) because it cuts through noise better than voice. A Morse signal can be decoded at signal levels where voice would be unintelligible.
Aviation — navigational beacons (VORs and NDBs) identify themselves with Morse code. Pilots learn to recognize station identifiers by ear.
Emergency signaling — the SOS pattern (... --- ...) is universally recognized. Flashing a light in Morse is a viable emergency communication method when nothing else works.
Accessibility — some assistive technology uses Morse-like input methods. Google's Gboard supports Morse code input for users with motor disabilities.
Morse code format conventions
Letters within a word are separated by a space (or a short pause in audio).
Words are separated by / (or a longer pause — typically 7 dot-lengths in audio timing).
Case doesn't matter — Morse has no upper/lowercase distinction. hello and HELLO produce the same output.
Numbers use 5 dots/dashes each: 0 is -----, 1 is .----, and so on. There's a logical pattern — count how many dots vs dashes tells you the digit.
Punctuation is supported but less standardized. Period is .-.-.-, comma is --..--, question mark is ..--... Not all translators support the same punctuation set.
Edge cases
Non-Latin characters — Morse code was designed for the Latin alphabet. There are extensions for Cyrillic, Arabic, Japanese (Wabun code), and others, but they're separate systems with different mappings. This tool supports ITU International Morse only.
Prosigns — in traditional Morse, certain character combinations are sent without spacing as procedural signals (AR for end of message, SK for end of contact). This tool doesn't handle prosigns — it treats each character individually.
Ambiguous spacing — when decoding, the difference between a space within a character (between dots and dashes) and between characters matters. In written Morse, this is handled by convention: single space between characters, / between words.
Troubleshooting
Some characters in my input are missing from the output — the tool drops characters it doesn't have a Morse mapping for. Emoji, Unicode symbols, and non-Latin characters are silently skipped. Stick to A-Z, 0-9, and basic punctuation.
Decoding fails with an error — your Morse input contains an invalid sequence. Check for typos — an extra dot or dash produces a sequence that doesn't map to any character. Also check your word separators — use / not | or multiple spaces.
The decoded text is all uppercase — correct. Morse code has no case distinction. The decoder outputs uppercase by convention. Lowercase it yourself if needed.
I see / in my encoded output — that's the word separator. HELLO WORLD becomes .... . .-.. .-.. --- / .-- --- .-. .-.. -... The / marks where the space was.
Round-trip encoding/decoding changes my input — only if your original input had characters that Morse doesn't support. Those characters are dropped during encoding and can't be recovered during decoding.
What to do with it
For puzzles and CTFs: decode the Morse, get the flag or clue. If it's layered encoding (Morse → Base64 → hex), decode one layer at a time.
For learning: encode common words and practice recognizing the patterns. The most frequent letters in English (E, T, A, O, I, N) have the shortest Morse codes by design — Morse was optimized for efficiency.
For creative projects: Morse code as a visual element works well in design. The dots and dashes have a clean, minimal aesthetic. Use the encoded output as a design element, engraving text, or visual puzzle.