Morse Code Reader

Use typed dots and dashes from a puzzle, worksheet, message, or copied text block.

A separated group such as .... is one character. Spaces between groups tell the reader where letters end.

Slash separators are easier to preserve than repeated spaces when Morse is copied through apps.

Check the decoded text, then fix spacing or unknown groups if the output includes ? or looks joined together.

Typed Morse needs a visible separator between character groups so .... . reads as H E, not one long unknown group.

Use / for word breaks when a normal word gap might be collapsed by a text field, chat app, or note.

Real Morse uses pauses for letter and word gaps. Typed Morse uses visible spacing so a reader can keep the same boundaries.

A continuous run can often be split more than one way. Add separators before trusting the decoded result.

Use this page when you want the simplest paste-and-read flow for typed dots, dashes, spaces, and slashes.

Use the technical decoder when you want the standard conversion tool for checking unknown groups and spacing details.

Use the audio decoder when your input is a sound file rather than pasted text symbols.

Use the encoder when you are starting with normal text and need clean Morse output.

Use the book translator when the readable text is long enough to become a chapter, article, or book-length audio export.

The reader needs boundaries. Add spaces between letters before treating the decoded text as reliable.

Hyphen-minus is safest for typed dashes. Rich text can replace it with dash characters that are harder to share.

A period in normal writing is not the same job as a Morse dot inside a separated Morse group.

If word separators disappear, decoded words can run together or become harder to check.

This reader handles typed symbols. Use the audio decoder for uploaded recordings.

Decorative dots, bullets, and styled dash characters can change how pasted Morse behaves.