Text to Morse & Binary Converter
Translate text to Morse code or binary, both ways
Text to Morse & Binary Converter tool
Letters are separated by a single space and words by a forward slash (/). Decoding is case-insensitive.
Text to Morse & Binary Converter: key facts
- What it does
- Translate text to Morse code or binary, both ways
- Category
- Text Tools
- Cost
- Free, with no account, sign-up, or install.
- Your data
- Runs entirely in your browser — the files and text you enter are never uploaded to a server.
- Last reviewed
- . Report an incorrect result.
Understanding the Text to Morse & Binary Converter
Whether you are decoding a puzzle, teaching a class about how computers store letters, or just having fun with secret messages, translating between plain text and Morse code or binary is oddly satisfying. This converter does both, in both directions, updating the moment you type.
Switch between two modes — Text ↔ Morse and Text ↔ Binary — and edit either side: type a sentence and watch the dots-and-dashes or the 1s-and-0s appear, or paste a coded string and read the decoded text back. Morse uses the international standard, with letters separated by spaces and words by a forward slash; binary encodes each character as its eight-bit code. Hobbyists, students, escape-room designers, and curious tinkerers all use it to encode and decode without memorizing a chart.
If you paste something the mode cannot parse — a stray character in a Morse string or a digit other than 0 or 1 in binary — the field turns red and explains the rule, so you can spot the problem instead of getting silent garbage.
Getting a result
- Choose a mode: "Text ↔ Morse" or "Text ↔ Binary".
- Type or paste plain text in the left box to encode it.
- Or type or paste Morse/binary in the right box to decode it back to text.
- Use the Copy link above either box to grab the result; watch for a red error state if the code is malformed.
Two lookup tables, and the separator rules
Morse conversion uses a character map built from the standard International Morse alphabet, with a reverse map derived from it for decoding. Letters within a word are separated by a space and words by a forward slash, which is the conventional way of writing Morse as text since the real distinction is a timing gap rather than a character.
That separator convention is what makes written Morse ambiguous without it. The sequence for a letter is not self-delimiting, so a run of dots and dashes with no gaps has many possible readings — which is why the spacing is not optional decoration.
Binary conversion maps each character to its numeric code point in base two. Unlike Morse it is a fixed-width encoding per byte, so it needs no separators in principle, though grouping into bytes makes it readable.
- SOS is three dots, three dashes, three dots — chosen for being unmistakable rather than as an abbreviation.
- A forward slash marks a word gap; a single space marks a letter gap.
- The letter A in binary is 01000001, its code point 65 written in eight bits.
Reasons to use it here
- Conversion is bi-directional and live — editing either side instantly updates the other, so encoding and decoding use one interface.
- It follows the conventional Morse formatting (space between letters, slash between words) and standard eight-bit binary, so the output is interoperable with other tools and charts.
- Clear, mode-specific error states flag invalid Morse symbols or non-binary digits and tell you the formatting rule to fix them.
- It runs entirely in your browser from built-in lookup tables, so it is instant, free, and private.
Timing, and what the alphabet omits
Real Morse is defined by relative durations rather than by symbols. A dash is three times the length of a dot, the gap between symbols within a letter is one dot, between letters three, and between words seven. Written dots and dashes are a transcription of that timing, which is why hearing Morse and reading it are quite different skills — and why transmission speed is quoted in words per minute rather than characters.
The standard alphabet covers the 26 Latin letters, ten digits, and a limited set of punctuation. Accented characters, most symbols, and anything outside that set have no standard representation, so a conversion will simply drop them. Prosigns — procedural signals for start of message, end of transmission, and error — are transmitted as run-together letters and are part of operating practice rather than the alphabet.
Morse remains genuinely useful because it degrades gracefully. A signal too weak or noisy for voice can still be read as tone, which is why it persisted in maritime and aviation use long after voice radio, and why amateur operators still use it for long-distance contacts at very low power.
Frequently Asked Questions
How should I format Morse code so it decodes correctly?
Separate the dots and dashes of each letter with a single space, and separate whole words with a forward slash surrounded by spaces — for example "... --- ..." is SOS, and ".... .. / -- .--. " spaces words apart. Decoding is case-insensitive and the output is shown in uppercase.
Why does my binary show an error?
Binary mode expects only 0s and 1s, with each character as an eight-bit group separated by spaces. A different digit, a letter, or missing spaces between bytes will trigger the error state. Re-space the input into clean eight-bit chunks and it will decode.
Can it handle punctuation and numbers?
Morse mode supports digits and common punctuation in addition to letters. Binary mode encodes any character from its character code, so numbers and symbols convert as readily as letters — though very high-range Unicode characters may exceed a single eight-bit byte.
Is this useful for real communication?
It is mainly an educational and hobby tool — for puzzles, learning Morse, escape rooms, and understanding how text maps to binary. It is not an encryption tool; Morse and binary are encodings anyone can reverse, not secure ciphers.