Morse Converter 2026: Text to Morse & Back (Free Tools)

By the Learn Morsy Content Team · Reviewed by Enes Vural (Morsy founder) · Published July 31, 2026 · Verified against ITU-R M.1677-1 (2009)

Morse converters are the most-used Morse tools on the web. Type “hello”, get .... . .-.. .-.. ---. Paste ... --- ..., get “SOS”. Simple in theory, surprisingly inconsistent in practice. Most free tools handle the 26-letter alphabet fine and quietly break on prosigns, accented characters, or punctuation edge cases.

Here is what a proper Morse converter should do, the 5 tools we recommend for different use cases, what “correct” conversion actually requires per the ITU standard, and the character-coverage gaps to watch for when you copy-paste output into anything permanent.

What is a Morse code converter?

A Morse converter is software that translates between plain text and Morse code notation, in either direction. In 2009, the ITU published Recommendation M.1677-1, which defines the current international letter set, timing rules, and prosign patterns every serious converter follows. If a tool ignores that standard, the output is not real Morse and won’t be readable by any trained operator or on-air receiver.

The bidirectional capability matters. Good converters accept both:

• Text input: type “MORSE” and get -- --- .-. ... . as dit-dah output.
• Morse input: paste -- --- .-. ... . and get “MORSE” back.
• Audio input (some tools): record or upload a Morse tone recording and get decoded text.

Our Morse translator does all three modes at once. Simpler tools stop at bidirectional text conversion without audio.

How is a Morse converter different from a Morse translator?

The terms overlap heavily. Most sites use them interchangeably. In stricter usage, “converter” implies text-form output (dit-dah symbols you can copy and paste), while “translator” implies audio playback (Morse tones you actually hear). Real tools blur the line.

Look at what a search for “morse converter” typically returns: browser tools that do both text conversion and audio playback. Search “morse translator” and the top results are the same tools with different marketing labels. The keyword distinction matters more for SEO than for the underlying feature set. Details of the audio-specific side are covered in our Morse translator audio guide.

If you need a tool that outputs only dit-dah text for a puzzle, a tattoo, or a jewelry inscription, any of the five tools below work. If you need to actually hear the Morse played back at a specific WPM, our translator and morsecode.world are the two that handle audio playback well.

What output formats do Morse converters produce?

Three common formats. Some tools produce all three from one input, others focus on one.

The dit-dah format is what “converter” usually returns by default. The audio format is closer to what “translator” implies. Visual flash output is rare in web tools but common in phone apps like Morsy (which uses the phone flashlight LED to output the pattern physically).

Wondering which one you actually need? For most casual queries the text output is enough. For learning to copy Morse by ear, audio matters. For signalling practice, visual flash is closest to the real thing.

What does “correct Morse conversion” require?

Correct conversion means the tool follows ITU-R M.1677-1 (2009) for the letter set and spacing rules. Every dit is 1 time unit, every dah is 3 units, gaps are 1/3/7 units for intra-letter, inter-letter, and inter-word respectively. Any tool that changes those ratios or uses a non-ITU letter mapping produces output that won’t be readable elsewhere.

Beyond the alphabet, correctness includes:

• Prosign handling. Prosigns like SOS, AR, SK are sent as one continuous shape with no letter gap. A converter that puts a 3-unit gap between the S, O, and S of “SOS” is technically producing three separate letters, not the distress prosign.
• Punctuation coverage. ITU-R M.1677-1 defines 16 punctuation marks. Many converters skip the less common ones (semicolon, apostrophe, quote marks) and silently drop them.
• Accented character support. The standard includes patterns for Ä, Ö, Ü, É, Ñ, Ç and others. Converters that ignore these produce broken output for anyone converting non-English text.

Our international Morse standard post covers the full ITU spec if you want to verify what any tool should be doing.

Which Morse converter tools are worth using?

Five tools cover the practical needs. We’ve tested all of them against ITU-R M.1677-1 and against real edge cases (prosigns, accented characters, high-speed audio).

For most people, our translator or morsecode.world covers the job. dcode.fr is worth knowing about if you’re solving cipher puzzles that mix Morse with other codes. browserling is minimal and fast if you only need dit-dah text output with zero features.

Our finding: In our translator usage data from the past 3 months, roughly 68% of conversions are text-to-Morse (people converting a name, phrase, or message), 22% are Morse-to-text (people decoding something they found), and 10% use the audio playback for practice. The dominant use case is one-off symbol lookup, not sustained practice.

What are Morse converters used for?

Converters get used for things Morse code was never designed for. Most of the demand isn’t from ham radio operators (they don’t need converters, they read Morse by ear). It’s from puzzle designers, tattoo enthusiasts, film prop makers, and social media people who want a fun caption.

The tattoo case is the one where mistakes are permanent. We’ve seen requests to fix Morse tattoos with missing letters, wrong prosign handling, or output from a converter that didn’t support the accented character in the person’s name. Print the output on paper first. Compare it against our Morse chart. Then commit.

What character sets do Morse converters actually support?

Coverage varies. The 26-letter English alphabet is universal. Everything else depends on the tool. Here’s what to check before trusting output for a specific use case.

Emoji doesn’t map to Morse. There’s no ITU-defined pattern for it and no tool supports it. If someone asks you to Morse-convert an emoji, the answer is you can’t. Convert the description instead (“heart” instead of ❤️) and note that the receiver won’t decode back to the original emoji.

Numbers deserve one note: standard digit patterns are 5 symbols each (all 5 tools handle these). Ham radio cut numbers (T=0, N=9, E=5) are contest shortcuts and only Learn Morsy supports them as an optional output mode. Details in our Morse code numbers post.

Can you embed a Morse converter in your own tool?

Yes. Three levels of programmatic access exist for developers who want to build Morse conversion into another app or site.

Client-side JavaScript library. Our converter exposes a public JS module you can import into any web project. Zero API calls, zero rate limits, runs entirely in the browser. Simplest option for prototypes and hobby projects. The W3C Web Audio API handles the audio playback side.

Third-party REST API. RapidAPI and similar marketplaces list free Morse converter APIs with basic rate limits (typically 100-500 requests/day free tier). These work if you need server-side conversion in a language other than JavaScript. Verify the underlying tool follows ITU spec before committing.

Self-hosted Cloudflare Worker / edge function. For projects with volume, self-hosting a converter as a Cloudflare Worker or Vercel Function gives unlimited free requests at the free tier and adds ~10 ms to your response times globally. Our own translator runs this pattern in production.

Our finding: The single most-converted text on our translator over the past 6 months is “I love you” (about 3.4% of all conversions). SOS is second (2.8%). The most-converted prosign is SOS by an order of magnitude over the next contender. This tells us the tool’s primary emotional use case is personal messages, not ham radio prep.

How do converters handle Morse accessibility input?

Both iOS (since iOS 14) and Android support Morse code as a system-wide alternative keyboard for users with motor disabilities. The user taps short and long presses on the screen, and the OS converts the taps to text in real time using the same ITU-R M.1677-1 mapping any converter uses.

This is a genuine accessibility feature, not a novelty. For users who can reliably control one motor input (a switch, a screen tap, a puff-and-sip tube), Morse is the fastest one-switch text entry method available. Some users reach 30-40 words per minute after months of practice. Our Koch method guide covers the training that makes this speed possible.

If you’re building an accessibility tool that includes Morse input, use the OS-provided input method rather than reimplementing the converter yourself. The system-level implementation is more reliable, better tested, and stays consistent with system-wide accessibility settings the user has already configured.

What are the legal notes on Morse conversion?

Two things worth knowing. First, converting text is unrestricted. Any converter output you generate is yours to use freely. No copyright applies to standard Morse patterns and no license is required for the ITU-R M.1677-1 letter set.

Second, transmitting converted Morse is restricted in some contexts. The most important rule: never transmit a real SOS as a prank. SOS carries legal weight under maritime and aviation regulations in most countries. Broadcasting a fake distress signal on any radio frequency (or even signalling one visually toward a road, ship, or aircraft) can trigger a real rescue response at your cost.

Our SOS in Morse code post covers the full history and legal context. Short version: convert SOS to text for tattoos, puzzles, or personal use freely. Never send it as an actual radio or optical signal unless there’s a real emergency.

For amateur radio broadcasting of any Morse (not just SOS), you need a valid ham radio license (Technician class or higher in the US). See our CW trainer guide for the on-air path.

Try a Morse converter right now

Open our Morse translator. Type your name. See it convert to dit-dah notation instantly. Hit Play to hear the audio at 15 WPM Farnsworth timing (character speed 20, effective 7). Try adding a <SOS> at the end and notice how it renders as one continuous prosign shape without letter gaps between the S, O, and S.

Compare the output against our Morse chart to verify the letter mapping matches ITU spec. For decode-direction testing, paste -.-. --- -.. . and confirm you get “CODE” back. If any converter fails these two basic tests, don’t trust it for real use.

For deeper theory on why the conversion rules matter, see our how Morse code works post on timing rules and our Morse decoder guide on the reverse direction (audio to text).

FAQ

What is a Morse code converter?

A Morse converter turns text into Morse code notation (dit-dah symbols) and vice versa. Bidirectional tools also play the audio and accept spoken or recorded Morse input. Every serious converter follows ITU-R M.1677-1 (2009) for letter mapping, timing, and prosign handling. Good ones also handle numbers, punctuation, and accented characters.

What is the difference between a Morse converter and a Morse translator?

The terms overlap heavily in practice, but converter usually implies text-form output (dit-dah symbols you can copy-paste), while translator implies audio playback (Morse tones you hear). Our Morse translator does both. Most modern web tools do both regardless of what they call themselves.

Can a Morse converter handle prosigns like SOS?

Better ones can. Prosigns are Morse patterns sent as one continuous shape with no letter gap between the component letters. SOS, AR, SK, KN are the common ones. A converter that outputs ... --- ... with letter gaps between S, O, S is technically wrong. The correct output collapses the pattern into one 9-symbol block.

Do Morse converters support accented characters?

Some do. ITU-R M.1677-1 includes patterns for accented letters used in French, German, Spanish, and Swedish (Ä, Ö, Ü, É, Ñ, Ç). Our converter and most modern web tools support these. Older or simpler converters skip them entirely and either silently drop the character or output a placeholder.

Is there a free Morse converter API?

Yes, several free options. Our translator exposes a public JavaScript library for browser embedding at no cost. Third-party APIs on RapidAPI and free Cloudflare Workers implementations also exist. Most cover text-to-Morse conversion only. Audio playback usually requires the Web Audio API implemented client-side.

Can I use a Morse converter for tattoos or jewelry?

Yes, and it’s a common use case. Convert your text to dit-dah notation, then work with the artist or engraver to render the symbols visually. Double-check the output against a printed Morse chart before committing to permanent ink. Common mistakes: missing letters, wrong prosign handling, or converting to an obsolete Morse variant.

Are Morse converters accurate?

The good ones are ~100% accurate for the 26-letter, 10-digit core alphabet defined in ITU-R M.1677-1 (2009). Accuracy drops for punctuation (16 marks in the standard, but tools often skip half), prosigns (many tools mishandle the letter-gap rule), and accented characters (regional extensions, patchy support). Verify edge cases before trusting output.

Sources

• ITU, Recommendation ITU-R M.1677-1: International Morse code, 2009. Retrieved 2026-07-31 from https://www.itu.int/rec/R-REC-M.1677-1-200910-I/
• ARRL, Learning Morse Code — resource index, 2025. Retrieved 2026-07-31 from https://www.arrl.org/learning-morse-code
• Wikipedia contributors, Morse code — character set and encoding standards, 2026. Retrieved 2026-07-31 from https://en.wikipedia.org/wiki/Morse_code
• W3C, Web Audio API specification, 2025. Retrieved 2026-07-31 from https://www.w3.org/TR/webaudio/
• Morsy internal usage data, 6-month window ending 2026-07-31 (text-conversion frequency, most-converted phrases, prosign confusion rates)