Morse Code Decoder

Start with a clearly separated sequence

Paste .-. . .- -.. / .. - into Your Morse code. The result should read READ IT. Four letter groups form READ, a slash separates the words, and two more groups form IT. Read the output against the source before copying it. The tool updates while you edit, so each change to a boundary can immediately change the result.

Keep an untouched copy of an unfamiliar sequence before correcting it. A puzzle, worksheet or pasted message may use its own notation. The source copy lets you distinguish a change made by the sender from a change you introduced during inspection. If you only have a screenshot, transcribe the marks and spaces carefully; this page does not read images.

The Morse code decoder works with written dots, dashes and separators. It does not listen to a recording or infer a missing word from the surrounding sentence. Check an explicit warning when one appears, and also check an unexpected answer even when every group is technically valid.

Find the problem before changing the message

First decide what has changed: the symbols, their grouping, the supported alphabet or the meaning you expected. An ordinary word pasted next to a signal may be a label, not part of the encoded message. A character displayed in ⟦brackets⟧ needs inspection; deleting the brackets from a copied result does not fix the source.

Use Check input issues to review the marked items, then select an issue to locate its source position. Inspect character mapping connects source ranges with output groups. Activating a group selects its original position, so you can repair one item without searching through the entire message. The tool keeps unresolved items visible instead of treating a partial answer as complete.

Work on one suspect position at a time. Compare it with the untouched source, make an evidence-based correction, and reread the neighboring groups. If the original contains the same unexpected mark, the next step may be asking the sender about it rather than deleting it. Record any interpretation you add yourself when passing the result to someone else.

Preserve the boundaries your source provides

For standard written notation, use one space between letters and / between words. The input also accepts three or more spaces and line breaks as word boundaries. Compact notation uses | between letters. These conventions let you decode a message from several readable formats, but they also mean that reformatting whitespace can change how the message is divided.

A line break added for layout can be interpreted as a word boundary. If a document wraps a signal visually, check whether copying it inserts an actual newline. Similarly, do not expand every letter space into several spaces just to improve its appearance. Keep a consistent notation and compare the decoded word boundaries with the original layout.

Supported typographic dot and dash forms are normalized, but not every similar-looking mark is accepted. When a symbol is flagged, compare it with an ordinary period or hyphen and inspect the source before replacing it. The visual shape alone cannot establish whether a mark was intended as an element, punctuation or a separator.

Why grouping can change the answer

The same sequence of elements can form one character or several characters, depending on where the letter boundaries fall. Compare the three rows below. Each contains three dots followed by one dash, but the spaces create different groups. V, ST and EEET are all consistent with their respective written inputs.

A continuous sequence is therefore not automatically an error. The group ...- is already a valid V. The tool has no evidence that the sender meant ST unless a source, notation key or other context establishes that boundary. Conversely, a group that is not in the selected alphabet cannot become a reliable answer merely because one possible split happens to spell a familiar word.

Try each row separately, keeping the spaces exactly as printed. Compare the number of output characters with the number of groups, then return to your source. This experiment shows what boundaries do; it does not provide a rule for reconstructing boundaries that were never supplied.

A valid character is not always the intended character

Validation tells you whether the supplied groups belong to the selected alphabet. It cannot prove that the groups were copied correctly or that they match the sender’s intention. Replacing one valid pattern with another can produce a clean result with the wrong letter. Word boundaries can also change while all the individual letters remain valid.

For ordinary text, re-encoding the decoded result provides a useful transcription check. Compare the normalized groups and boundaries with the received sequence. This can reveal a copying mistake, but it cannot prove that your source was correct in the first place. An incorrect sequence may round-trip perfectly because the same mapping is applied in both directions.

Use context as evidence to investigate, not as permission to silently rewrite. A room number, name or puzzle answer may be unfamiliar yet correct. If you supply a guessed correction, preserve the original and explain what you changed. After copying the accepted result, inspect the destination too; another app can alter spacing or punctuation after the decoder has finished.

To compare a decoded phrase with an encoding of the same text, open the text-to-Morse translator.

Check character conventions and context

Some patterns have distinct text and operational meanings. The sequence .-.-. represents a plus sign in the text alphabet and AR in the operational alphabet. The code alone does not establish which meaning an unfamiliar sender intended. Use the interpretation choices offered by the tool to select the convention that matches your source.

Operational signals, also called prosigns, communicate procedural meanings through joined patterns. They are not created simply by decoding their names as separate ordinary letters. A valid choice in one alphabet does not imply that the same interpretation applies in another. Review an offered ambiguity before using the result, especially when a worksheet mixes text notation with procedural examples.

For the text tool’s letters, punctuation and substitutions, check the supported character reference.

Know when missing information cannot be recovered

This public decoder uses explicit boundaries and does not offer speculative recovery of an unseparated stream. If spacing is missing, return to the source layout, ask for a separated copy, or consult the puzzle’s supplied clues. Several valid divisions may remain possible even after you have checked every mark.

For example, ...---... is an unrecognized group in the text alphabet, while ... --- ... reads SOS. That familiar example does not make automatic splitting safe for arbitrary input. Without supporting information, report the uncertainty instead of presenting one guessed reading as the recovered message.