A Morse code picture translator reads the dots and dashes that are visible in an image and turns them into plain text. Drop a screenshot, a phone photo, or a scan into the image translator above: the tool finds the marks, writes them out as an editable string, and decodes that string with the International Morse table. Nothing has to be typed symbol by symbol, and every detected group can be corrected before the text is trusted.
How to Translate Morse Code from a Picture
- Get the clearest picture you can: a screenshot beats a photo, and a tight crop around one line of Morse beats a full page.
- Add the image to the translator by dropping it in, choosing a file, or taking a photo with your phone camera.
- Let the tool scan the image. It writes the dots and dashes it found in the Detected Morse field.
- Compare the Detected Morse with the picture. Fix a missed dot, a merged dash, or a missing space between letters directly in the field.
- Copy the decoded text, or copy the Morse itself if you need it for another tool. The text updates as you edit, so there is no need to rescan.
What the Picture Translator Can Read
The tool accepts PNG, JPEG, and WebP files, and what comes out depends far more on the picture than on the format. The rows below are the image types people actually bring to a picture translator, ranked by how often the first scan is right.
| Image type | What to expect | What helps |
|---|---|---|
Screenshot of typed Morse (.-- .... -.--) |
Cleanest read; marks are uniform and evenly spaced | Save as PNG; JPG compression blurs small dots |
| Graphic dots and bars (puzzle art, game HUD) | Good read once dots and dashes differ clearly in width | Crop to the Morse row; the detector handles light marks on a dark background automatically |
| Phone photo of a printed worksheet | Usually right after one or two corrections | Shoot square-on in even light; avoid flash glare and shadows |
| Scan of a book page or old telegraph sheet | Faded marks may drop out | Use a higher-contrast scan, then check for extra noise |
| Handwritten Morse | Works only when each dot and dash is distinct | Expect to edit; uneven dash lengths confuse the width test |
| Multi-row Morse | Rows are read top to bottom when gaps between rows are clear | Keep each row straight and running left to right |
How the Tool Turns Marks into Morse and Text
The decoder does not read letters; it measures shapes. The image is converted to grayscale, a threshold splits every pixel into mark or background, and touching pixels are grouped into connected components. A compact component becomes a dot, a wider horizontal component becomes a dash, and the width of the gaps between components decides where one letter ends and the next word begins.
That string of dots, dashes, and spaces is then looked up in the International Morse table, one group at a time. A group that matches no character is not guessed; it appears as # in the decoded text so you can find the corresponding group in Detected Morse. The whole process is deterministic image processing, which is why a clean screenshot gives the same answer every time.
Check the Detected Morse Before You Trust the Text
Most wrong translations come from spacing, not from misread marks. If the decoded text is nonsense while the dots and dashes on screen look right, a gap was read as too small (two letters merged into one invalid group) or too large (one letter split into two). Add or remove a space between letters, or put a slash between words, and the text corrects itself.
A # in the decoded text means the corresponding symbols do not form a valid Morse character. The usual causes are two marks that touched after thresholding, a speck of noise counted as a dot, or a dash so short it was measured as a dot. Compare Detected Morse with the original image and correct only the groups that produce #; that is faster than retaking the picture.
Fix a Bad Read: Contrast, Crop, Rotation, Spacing
A clearer crop or a quick correction in Detected Morse fixes many failed scans. Work through the likely causes below.
| Symptom | Likely cause | Fix |
|---|---|---|
| Nothing detected | Low contrast, blur, or too much surrounding detail | Crop to the marks and try a clearer image |
| Marks missing from Detected Morse | Faded or thin marks | Use a higher-contrast scan or add the missing marks in Detected Morse |
| Extra marks that are not Morse | Texture, shadows, or text in the crop | Crop out captions, margins, and decorations; remove stray marks in Detected Morse |
| Dots read as dashes (or the reverse) | Blur or glare stretched the marks | Retake in sharper focus, or edit the Detected Morse |
| Text looks shuffled | Rows are vertical or tilted | Rotate the source image so Morse runs left to right, then scan again |
| Words run together | No word gaps in the source image | Insert / between words in the Detected Morse |
Using Your Phone as a Morse Code Scanner
A phone camera is enough to scan Morse from a printed worksheet, a whiteboard, or a message on another screen. Hold the phone parallel to the surface so the dashes keep their true length, use even room light instead of the flash, and fill the frame with the Morse row rather than the whole page.
If you already have the Morse as a screenshot from a chat, a practice app, or a social post, use that file instead of photographing the screen. A screenshot has no perspective, glare, or moiré, so it almost always decodes on the first pass.
Picture Translator vs Text Translator vs Audio Decoder
Morse arrives in three forms, and Morse Beacon has a tool for each. Use the comparison to pick the right one before uploading.
| Picture translator (this page) | Text translator | Audio decoder | |
|---|---|---|---|
| Input | Photo, screenshot, or scan of dots and dashes | Typed or pasted .- text, or plain English |
Microphone or recording of Morse tones |
| What it measures | Shape and spacing of marks | Characters you typed | Length of each tone and silence |
| Editable Morse before decoding | Yes | Yes | Open in the text decoder to correct the result |
| Also handles | Phone camera photos | English to Morse, playback | Live CW off a radio |
If the message is still an image, stay here. If you can select the dots and dashes as text, paste them into the text translator; it skips detection entirely. If it arrives as a sound or a blinking light, use the audio decoder or the camera light decoder.
Where Morse Shows Up in Pictures
The picture translator earns its keep whenever Morse cannot be selected as text. Puzzle hunts, ARGs, escape rooms, and geocaching clues hide messages as rows of dots and bars; video games put Morse into HUDs and loading screens; teachers hand out worksheets and flashcards; and radio handbooks, museum displays, and scanned telegraph forms carry marks that no keyboard will reproduce.
For a puzzle, scan the whole clue, then correct any groups that produce #. For a classroom sheet or a study guide, keep the picture open beside the decoded text so each line can be checked against the original.
Privacy and What the Tool Does Not Read
The image is processed in your browser. It is not uploaded to a server or passed to a remote AI service, and closing or reloading the page clears the current picture from the tool. That makes the translator usable with photos you would not want to send anywhere.
The translator reads International (ITU) Morse only: A–Z, 0–9, and common punctuation. It does not decode American railroad Morse, whose timings differ, and it does not recognize ordinary printed sentences, because it is a mark detector rather than a general OCR engine. Heavy blur, strong perspective, touching marks, and loose handwriting all reduce accuracy, so the Detected Morse should always be checked before the text is used.
Frequently Asked Questions
Can I translate a screenshot of Morse code?
Yes. Screenshots are the most reliable input because the marks are sharp and evenly spaced. Save the screenshot as PNG, crop to the Morse line, and the translator will usually decode it on the first scan without any edits.
Can the picture translator read handwritten Morse?
Sometimes. Handwriting decodes when every dot is clearly shorter than every dash and the gaps between letters are visible. Uneven strokes can cause # in the decoded text, so plan to correct a few groups by hand.
What does a # in the decoded text mean?
It means the corresponding group of dots and dashes matches no International Morse character. Two marks probably touched, or a speck of noise was counted as a dot. Edit that group in Detected Morse while looking at the original image.
Is my picture uploaded or stored?
No. The image is read and analyzed in your browser, and it is cleared when the page is reloaded or closed. Nothing is sent to a server for decoding.
How do I decode white Morse on a black background?
Upload the image as usual. The detector checks the background and can read light marks on a dark background automatically. If marks are missing, try a tighter crop or a clearer image.
Does it work with American Morse or other variants?
No. The translator decodes International Morse as standardized by the ITU. American Morse uses different dash lengths and internal spacing, so its images are read incorrectly and need manual decoding.