Shot2Text

JPG to Text — Free Online Converter, Nothing Uploaded

JPG to text, with the compression undone first. Pull the words out of a JPG and copy them as real, editable text — small and heavily compressed JPGs get upscaled and sharpened before reading, because JPEG artefacts are the main reason text fails.

Only the language you pick is downloaded.

What is a JPG to text converter?

JPG compresses by throwing away detail around edges — and letters are almost nothing but edges. That is why a screenshot saved as JPG often reads worse than the same screenshot saved as PNG, even though both look identical to you at normal size.

The damage shows up as faint rings and blocky patches hugging each letter. A human eye ignores it without thinking. A text reader treats those halos as strokes and starts inventing extra lines inside letters like e, a and 8.

So this converter does a little groundwork before reading: it upscales images that are smaller than about 1400 pixels wide, then applies a mild unsharp mask. That is enough to recover most of what JPEG took away on typical document photos, screenshots exported as JPG, and images passed through a chat app.

What can you use a JPG to text converter for?

  • Screenshots that got saved as JPG. Chat apps, email clients and image editors often convert PNG screenshots to JPG without telling you. This handles that.
  • Photos of printed documents. A form, a letter, a printed page. Crop so the text fills the frame rather than the desk.
  • JPGs sent through WhatsApp or WeChat. These get recompressed and shrunk badly. The upscale step exists precisely for this case.
  • Scanned pages exported as JPG. Most scanners default to JPG. A 300 dpi scan reads very well; a 100 dpi scan usually does not.
  • Text inside a graphic. A JPG poster or slide with text on it — as long as the text isn't sitting on a busy photo behind it.
  • Prices and figures from a photo. Menu boards, price tags, printed totals. Check digits afterwards: 1/7 and 5/6 remain the classic confusions.

Why does a JPG read badly when it looks fine?

Nearly every failure traces back to how the JPG was made. These are the patterns worth knowing.

  • The JPG is tiny (under ~800 px wide) There simply aren't enough pixels per character left after compression. Re-export at full size, or shoot the document again rather than reusing the shrunk copy.
  • It went through a messaging app Chat apps recompress aggressively — often to a third of the original dimensions. Send the file as a document instead of a photo, or use the original from your camera roll.
  • Heavy compression setting Quality below about 60 % leaves visible blocks that the reader misreads as strokes. Re-save at quality 85 or higher, or use PNG if you control the export.
  • Text on a coloured or photographic background The reader cannot separate letters from texture when both have similar contrast. Crop tightly around the text block so as little background as possible is in the frame.
  • Dark mode screenshots saved as JPG Pale text on dark grey compresses badly; the halos are as bright as the letters. Screenshot the light version of the page, or invert the image before uploading.
  • Small text on a large photo Compression hits the smallest details hardest, and those are the letters. Crop to the text region so it occupies most of the image, then upload that crop.

What do you get back?

Plain text with line breaks, in reading order. No formatting, no tables, no colours — just the words. Copy it with one click or select it by hand.

The output file is not created on a server; the text appears in the page and you copy it from there. Nothing is stored and there is no history.

If you need a Word document rather than plain text, use the image to Word converter instead — it wraps the same reading step and hands you a .docx file.

Is my JPG uploaded anywhere?

The image is decoded and read by JavaScript inside your browser tab. It is not uploaded, not queued and not stored anywhere.

This matters more for photos than for screenshots — a photo of a document can carry a letterhead, an address, a signature. Open your browser's network panel while converting and you will see that no request ever carries the image.

Questions

Does JPG to text work better than PNG to text?
No — PNG is usually more accurate, because PNG is lossless and JPG is not. The letters in a PNG arrive with clean edges; in a JPG they arrive with compression halos around them. Use PNG when you have the choice. This tool works hard to compensate, but it cannot invent detail the compression already discarded.
Why does my JPG read badly when it looks fine to me?
Because your eye is very good at ignoring compression artefacts, and a text reader is not. Those faint rings around each letter look like part of the letter to the reader. Upscaling and sharpening recovers most of it, but a JPG shrunk by a chat app is often beyond saving — re-send the original instead.
What JPG quality should I use?
85 or above. Below about 60 the blocking becomes visible and accuracy drops sharply. If the file is destined for text recognition rather than for viewing, PNG is the better choice every time.
Can it read a JPG of a scanned page?
Yes, and 300 dpi scans read very well. A 100 dpi scan usually does not, because at that resolution each character is only a few pixels tall. Check your scanner settings before blaming the tool.
Is the image uploaded?
No. The reading happens in your browser tab and the image is never transmitted. You can confirm this in your browser's network panel: the only download is the English text data, once.
Does it handle JPGs from a phone camera?
Usually. Phone photos are large and well-lit, which helps. What hurts is tilt and shadows — shoot straight down in even light. Very large photos are downscaled to about 2200 pixels wide before reading, which is well above what the reader needs.
Why is the first conversion slow?
About 3 MB of English text data is downloaded once and then cached. Later JPGs take a second or two.
Can I convert several JPGs at once?
Not on this page — it reads one image at a time. If you have a batch, do them one after another; the language data stays cached so each is fast.