Text to Morse & Binary Converter
Translate text to Morse or binary, and hear it keyed
Text to Morse & Binary Converter tool
3 characters, 1.6 s at 20 words per minute.
Sound
Standard ITU timing: a dash is three dots, gaps are one, three and seven dots.
SOS
3 characters · 1 words · 3 sendable · 6 dots · 3 dashes · 1.6 s at 20 wpm
Text to Morse & Binary Converter: key facts
- What it does
- Translate text to Morse or binary, and hear it keyed
- 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
Morse is not really a set of glyphs — it is a rhythm. A dash lasts three times a dot, the silence inside a letter lasts one dot, between letters three, between words seven, and an operator hears all of that rather than reading it. So this converter does not stop at printing dots and dashes: press Play and it keys a sidetone through your speakers on that exact timing, at a speed you set in words per minute, with a lamp that blinks along and a WAV file you can keep.
Two modes share the same pair of boxes. Text ↔ Morse handles the international alphabet — 26 letters, 10 digits, 18 punctuation marks — plus the accented and national letters of the ITU extension and the prosigns operators actually use, written between angle brackets as <SOS> or <AR>. Text ↔ Binary treats a character as the number it is stored as, in base 2, 8, 10 or 16. Type on either side: whichever box you are typing in is marked as the source, and the other one follows it.
The rule throughout is that nothing disappears quietly. If a character has no Morse code — a euro sign, a hash, an em dash — the tool names it instead of deleting it, and offers to fold accented letters down to plain ones so the rest of the sentence can be sent. If a run of binary is not a whole number of bytes, that is an error with the offending group quoted back to you, not a wrong character presented as a right one.
Getting a result
- Pick a mode: "Text ↔ Morse", or "Text ↔ Binary" for character codes in base 2, 8, 10 or 16.
- Type plain text in the left box to encode it, or paste Morse or numbers in the right box to read them back — the box you type in becomes the source.
- If something cannot be sent in Morse, read the amber note and use "Fold accents" to turn café into a sendable cafe.
- Press Play to hear it keyed. Set the speed in words per minute, and raise the character speed above it for Farnsworth spacing — fast letters, slow gaps.
- Switch on the lamp to watch the keying, turn on Loop to repeat it, or press WAV to download the transmission as an audio file.
- Open the Reference tab for the full chart, or expand the character inspector to see code points and UTF-8 bytes side by side.
Speed, spacing, and why two numbers are better than one
Speed is quoted in words per minute against a fixed reference word — PARIS followed by a space, chosen because it happens to measure exactly 50 units of dots, dashes and silence. One dot therefore lasts 1200 divided by the speed, in milliseconds: 60 ms at 20 wpm, 240 ms at a beginner's 5 wpm. The slider here covers 5 to 40 wpm and recomputes every duration from that single figure.
The second slider is what makes the tool useful for learning rather than only for listening. Sending everything slowly teaches you to count dots, which is a habit you then have to unlearn, because a letter at speed is a shape rather than a sequence. Farnsworth spacing solves it by sending the characters at full speed and stretching only the silence between them, so the shapes are the ones you will eventually hear while the thinking time is generous. Set the character speed to 18 and the overall speed to 5 and the gaps take up the difference by the standard formula, holding the reference word at twelve seconds.
Pitch matters more than it sounds like it should. A tone that sits clear of the noise your ear is already filtering is far easier to follow, which is why receivers settled on something in the 600 Hz region; the slider runs from 400 to 1000 Hz. Each element also gets a five-millisecond fade in and out, because a sine wave switched on and off abruptly produces a click at every edge that is louder and more tiring than the tone itself.
- 1200 ÷ 20 wpm = a 60 ms dot, so a dash is 180 ms and a word gap 420 ms.
- Characters at 18 wpm with a 5 wpm overall speed gives roughly 1.57 s between letters.
- The WAV is 16-bit mono at 44.1 kHz, rendered from the same timing you are hearing.
Reasons to use it here
- It produces sound, not just symbols: a keyed sidetone on ITU timing with adjustable speed, Farnsworth spacing, pitch and volume, plus a synchronised lamp and a WAV download.
- Characters it cannot represent are named on screen rather than silently deleted, with one button to fold accents down to sendable letters.
- Editing either box is safe — one side is the source and the other is derived, so a mistyped symbol never overwrites the text you typed, case and accents included.
- The numeric side defaults to UTF-8 bytes, so every group really is eight bits and every character round-trips; a group of the wrong width is an error, not a wrong character.
- A searchable 100-row chart covering letters, digits, punctuation, accented letters and prosigns ships with the tool, and any row can be inserted into your text.
- Everything runs on your device: the tables are part of the page, the tone is synthesised by your browser, and no text or audio is uploaded.
What the alphabet leaves out, and what a byte really is
The international alphabet is small on purpose, and the gaps in it are real. There is no code for a hash, a percent sign, an asterisk, a tilde, a bracket pair beyond round ones, or a caret — fourteen printable keyboard characters in all. Accented letters are better served: the ITU extension and national practice between them cover à ä ç é è ñ ö ø ü ż and a couple of dozen more, all in the table here, and several deliberately share a code because Morse has fewer distinct signals than Europe has letters. Ä, Æ and Ą are one signal; so are Ó, Ö and Ø. Prosigns share codes with punctuation for the same reason, which is why the chart lists what each code decodes back to: the plus sign and the prosign AR are the same thing being read two ways.
Reading Morse back is deliberately forgiving. Charts are typeset with a middle dot and a Unicode minus rather than a full stop and a hyphen, some sources separate words with a pipe or a double slash, and pasted text arrives with all of it mixed. All of those are accepted, and a group that still cannot be read is quoted back with its position rather than swallowed.
The numeric side answers a different question, and the default answer is UTF-8 bytes. That distinction is worth a moment: a character's code point is its number in Unicode, but what is stored on disk is a sequence of bytes encoding that number, and only for the first 128 characters are the two the same thing. An emoji is one code point and four bytes; the euro sign is one code point and three. Grouping by byte is what makes "eight bits each" a true statement and what lets any character survive the trip out and back. Code points and UTF-16 units are both available too, labelled for what they are, and the inspector puts all of them in one table next to the character's Morse.
- A is 01000001 — one byte, code point 65, hex 41.
- € is 11100010 10000010 10101100 — one code point, three bytes.
- ··· −−− ··· pasted from a printed chart decodes to SOS.
Frequently Asked Questions
How should I format Morse so it decodes correctly?
Separate the dots and dashes of each letter with a single space and each word with a forward slash. Beyond that it is tolerant: a middle dot, a bullet or an asterisk all read as a dot, a Unicode minus, an en dash, an em dash or an underscore all read as a dash, and a pipe, a double slash or three consecutive spaces all read as a word gap. A leading or trailing separator is ignored. Anything genuinely unreadable is quoted back with its position instead of being dropped.
Why does my binary show an error when it decoded elsewhere?
Because a group that is not eight bits is ambiguous, and guessing is how you get the wrong answer. Paste 0100000101000010 with no spaces and this tool says so rather than reading it as a single 16-bit character — which is exactly what a lenient decoder does, and it produces one Chinese character instead of the letters A and B. When the input is a clean multiple of the group width, a button appears offering to read it as eight-bit groups, so the fix is one click.
What is Farnsworth spacing, and which speed should I set?
It sends each character at one speed while stretching the silence between characters to bring the overall rate down. Learners are usually pointed at characters around 18 to 20 wpm with an overall speed of 5 to 13, so the letters sound the way they will at full speed but you get thinking time between them. Leave both sliders equal for standard timing, where the gaps are the usual three and seven dots.
Why did an accented letter or a symbol disappear from my Morse?
It should not have, and it will not silently. Accented letters are covered by the extended table that is on by default; anything genuinely outside the alphabet — a euro sign, a hash, an em dash — is listed in an amber note above the boxes rather than removed without comment. If the characters are accented, "Fold accents" rewrites them as plain letters so the sentence can be sent; if they are symbols with no equivalent at all, there is nothing to send and the note tells you which ones.
Can I use the audio in a video or a recording?
Yes — the WAV button renders exactly what you are hearing as 16-bit mono PCM at 44.1 kHz and saves it to your device. It is generated from the same timeline the playback uses, so the speed, spacing, pitch and volume you set are what you get. Playback and rendering are capped at 20,000 characters, because at slow speeds that is already hours of audio and a file of several gigabytes.
Is any of this encryption?
No. Morse and binary are encodings, not ciphers: they change how a message is written or transmitted, and anyone with the chart can read them straight back — which is the whole point of a standard. Treat this as a tool for puzzles, radio practice, classroom demonstrations, escape rooms and understanding how text is stored, and use a real cipher if the content needs protecting.