Skip to main content

Image to Text

Image to Text

Turn image text, document snapshots, and screenshots into editable text.

Extract text from images in your browser

Drop PNG, JPG, WebP, GIF, BMP, HEIC or SVG images. Your files are never uploaded.

Max 50MB per fileUp to 50 files

How to Convert an Image or Picture to Text (OCR)

How to Use Image to Text

  1. 1

    Upload Image

    Drop your photo, screenshot, or scan (PNG, JPG, WebP, GIF, BMP, HEIC or SVG) into the workspace.

  2. 2

    Select Language

    Choose one of 55 languages, and a second one for a picture that mixes two — matching the document is the single biggest accuracy gain available.

  3. 3

    Copy or Download Text

    Copy the recognised text, or save it as TXT, Word, a searchable PDF or JSON, and a detected table as Excel or CSV.

What Image to Text Can Do

  • In-Browser Tesseract OCR

    Your image is recognised on your own device by a local WebAssembly engine.

  • Image Clean-up Before Scanning

    Contrast, brightness, greyscale, black-and-white threshold and sharpening presets for scans, receipts and whiteboards.

  • 55 Recognition Languages

    English, Spanish, French, German, Hindi, Arabic, Japanese, Chinese and more, with an optional second language.

  • Zero Cloud Uploads

    Read sensitive receipts, cards or IDs without the image leaving your browser.

Tools & Settings Reference

OCR Language Selection
One of 55 languages, with an optional second one for a picture that mixes two. The engine and each language are downloaded from a public CDN the first time they are used, so that step needs a connection.
Read Selected Area
Drag across the picture to read only that part of it, at the picture’s full resolution. The notes beside the text say when only an area was read.

Frequently Asked Questions

Yes, but you have to flip one switch — light text on a dark background is the one case the engine cannot handle as-is, because it expects dark characters on a light page. Turn on Invert in the image clean-up panel and the screenshot is flipped to dark-on-light before recognition, which usually takes the result from unusable to clean. There is no auto-detection for this, deliberately: guessing wrong would silently ruin a normal screenshot, so it is left as a control you can see.

Resolution, nine times out of ten. OCR needs enough pixels per character to tell letterforms apart — roughly 25 pixels of character height, which is about what 300 DPI gives for normal body text. A photo of a document taken from too far away, or a screenshot scaled down before saving, simply does not contain the shapes any longer. Re-capture closer or at a higher resolution rather than trying different settings; sharpening a source that lacks the detail cannot recover it.

Not reliably, and it is fairer to say no. The engine is trained on printed and typeset characters, where letterforms are consistent, and handwriting breaks that assumption — joined letters, varying slant and personal letterforms produce output that takes longer to correct than retyping. Neat block capitals sometimes come through. Cursive and normal note-taking handwriting will not.

Because recognition is not purely shape matching — the engine uses the selected language's character set and word patterns to resolve ambiguous glyphs. With the wrong language selected, characters that exist in one alphabet and not another get forced into the nearest available shape, and the correction step then pulls words toward a vocabulary that does not apply. Selecting the actual language of the document is usually the single largest accuracy gain available, ahead of any image preprocessing.