Photo2Text - home
Menu

Home / Screenshot to Text

Screenshot to Text, Free Online OCR

Turn screenshots into editable text in seconds. Private browser OCR , your captures never leave your device.

When screenshot to text saves time

Screenshots are everywhere: an error dialog you cannot select, a chat quote locked inside an app, a boarding pass image, a receipt from a payment screen. Screenshot to text OCR lets you copy that content into notes, emails, or bug reports without retyping. Photo2Text defaults to English for typical UI captures and keeps recognition local so sensitive on-screen data is not shipped to a remote OCR API.

Common use cases

  • Error messages, paste stack traces or support codes into tickets accurately.
  • Chat and email screenshots , recover wording when the original thread is hard to export.
  • Receipts and confirmations , grab totals and reference numbers from payment UIs.
  • Slides and webinars, capture bullet points from a paused video frame (quality permitting).

Tips for cleaner screenshot OCR

Capture at full resolution, crop to the text block, and avoid heavy compression. Prefer a lossless file and run OCR on a PNG screenshot; if the capture is already a phone JPEG, convert the JPG instead. Bilingual UIs? Switch to Urdu OCR or Arabic OCR. For the general English workflow, use the homepage image to text tool.

Step-by-step help: how to extract text from an image. Comparing privacy-first options? Read the best free OCR tools guide.

Error messages and dialogs: capture the exact wording

An error dialog is the single most common reason people reach for screenshot OCR. The message appears in a window you cannot select text from, it carries an error code or a file path you must copy exactly, and it disappears when you click OK. The right move is to capture the whole dialog before you dismiss it: the title bar, the message body, and any buttons or codes at the bottom. The title bar often names the program or the failing step, and the code at the bottom is what a support team or a search engine needs. Crop the desktop around the dialog, but keep the entire dialog inside the crop.

Once you have the text, paste it into a bug report, a support ticket, or a search query exactly as it came out, then check the error code character by character. Codes mix letters and digits that look alike, such as the letter O and the digit 0, or a lowercase l and the digit 1, and one wrong character sends the search in the wrong direction. Stack traces and log windows deserve the same treatment: capture them in readable chunks, keep the line order intact, and do not retype them from memory, because a retyped path or version number is where mistakes creep in. A screenshot plus OCR gives you a faithful copy of what the machine actually said.

Chat captures: quoting messages without retyping

Chat apps rarely offer a clean export, so a screenshot is often the only way to keep a quote. The text you need is usually a bubble in the middle of a busy screen: avatars, timestamps, reaction icons, and a reply thread around it. Crop tightly to the message bubbles you want, and keep the sender name with each message if the quote needs attribution. Timestamps help too when the quote is part of a longer story, because they show the order of events.

Long threads need a plan. Capture one screen at a time with a small overlap between shots, and run OCR on each capture separately, so the text stays large and the engine reads whole words instead of guessing at small ones. If a message is in a different language from the rest of the thread, run that capture with the matching language setting. Remember that chat screenshots can contain private information about other people, so think before you paste the extracted text anywhere public. The privacy advantage of browser OCR matters here: the screenshot never leaves your device, and the text you extract stays yours to handle.

Receipts and order confirmations on screen

Payment screens, order confirmations, and booking receipts are full of numbers that must be exact: an order number, a total amount, a date, and a reference code. A screenshot is often the only record you have, because the app shows the confirmation once and then moves on. Capture the full confirmation area, including the merchant name at the top and the reference number at the bottom, and do not cut off the currency symbol or the decimal point. A total of 1,250 looks very different from 12.50 if the decimal point is lost.

After OCR, check every digit against the image before you paste the details into an expense report or a support message. Order numbers often mix letters and digits, and dates can appear in day-month-year or month-day-year order depending on the app, so confirm which order the screen used. If the confirmation arrived as an email instead of an app screen, a screenshot of the email works the same way, but the plain text of the email is usually easier if you can select it. For boarding passes and tickets, capture the whole pass, including the booking reference and the barcode number printed below it, and keep the original screenshot as backup even after you have the text.

Cropping UI chrome, small text, and dark mode

A raw screenshot carries a lot of chrome that is not text you want: the status bar with the clock and battery, the navigation bar, notification banners, and the app header with its icons. Crop those away before you run OCR, because every extra element is a chance for the engine to read a time or a badge count as part of your message. Keep the text block generous, with a little margin around it, and leave the paragraph structure intact so line breaks fall where the app put them.

Small text is the hardest part of screenshot OCR. Phone interfaces use tiny labels for menu items, timestamps, and settings, and a full-screen capture shrinks them further. The fix is to enlarge the region before you capture it: zoom the app, turn on a larger text size, or capture a smaller area so the text fills more of the image. A screenshot taken at the full device resolution is far better than a thumbnail or a compressed copy sent through a messaging app, which may have been downscaled on the way.

Dark mode needs its own check. Light text on a dark background usually reads well when the contrast is strong, but thin grey text on a near-black background can fade into the background and confuse the engine. If the result is poor, invert the colours in any image editor so the text becomes dark on a light background, or switch the app to light mode and capture again. Never photograph a screen with another camera when a real screenshot is possible: a direct screenshot is pixel sharp, while a photo of a monitor adds glare, wavy patterns, and a tilted angle that no amount of cropping can fix.

Try our OCR tools

Same private browser OCR. Pick the page that matches your language or file type.

Frequently asked questions

Yes. Upload the PNG or JPG screenshot (or use Take photo if you photographed another screen). English is the default language; switch if the UI is in Urdu or Arabic.