Image to JSON
Recognise text in an image and get it back as structured JSON, with positions and confidence.
Convert Image to JSON
Never uploadedYour file is processed in this tab and never sent anywhere.
The ads come from Google. Your files stay on your device.
How to convert Image to JSON
- Add an image. A photo, scan, screenshot, or a table.
- Pick a shape. Plain text, a word list with coordinates, or rows and columns.
- Download the .json. Ready to parse in any language.
About Image to JSON
This is Image to Text for people who are going to write code against the result. Instead of a flat block of prose, you get structured JSON, and crucially, you get the metadata that a plain text export throws away: where on the page each word sat, and how confident the recogniser was about it.
Confidence scores are the part worth understanding, because they change how you can use OCR output. Recognition is never perfect, and the difference between a usable pipeline and an unreliable one is usually whether you can tell which parts to trust. A word returned at 96 percent confidence is almost certainly right. One at 45 percent needs review. With that number in the output you can route low-confidence fields to a human instead of silently importing a wrong digit into a spreadsheet.
Three output shapes cover the common cases. Plain gives you the full text with per-page confidence, which suits search indexing and archiving. Words gives every recognised word with its bounding box and confidence, which is what you want for building a form parser, redacting a document, or overlaying a text layer on an image. Table gives inferred rows and columns as arrays, matching what Image to Excel produces but in a format a script can consume directly.
Everything runs on your device via Tesseract compiled to WebAssembly. That matters more for a developer-facing tool than it first appears: the documents people build OCR pipelines against are usually invoices, receipts, forms, and identity documents belonging to their customers. Prototyping against a free web API means sending someone else's data to a third party, often without having thought about it. Here there is nothing to send.
Output shapes
| Shape | Contains | Use for |
|---|---|---|
| Plain text | Full text plus overall confidence | Search indexing, archiving |
| Words | Each word with bounding box and confidence | Form parsing, redaction, text overlays |
| Table | Inferred rows and columns as arrays | Data import, spreadsheet pipelines |
OCR to JSON
If you came here looking for OCR to JSON, this is the tool. The difference from Image to Text is what comes back: instead of a flat block of text you get structured output. Every recognised word with its bounding box, its confidence score, and the line and paragraph it belongs to. That structure is what makes it useful in code. A script can filter by confidence, find the word nearest a coordinate, or rebuild the layout, none of which is possible from plain text.
Starting from a screenshot? PNG to JSON is the same output tuned for lossless PNGs. If you only need the table, PNG to CSV rebuilds the rows and columns for you. For the whole process, from capture to checking the result, see how to get a table out of a screenshot.
Image to JSON FAQ
What is in the JSON?
Depending on the shape you pick: the recognised text, per-word bounding boxes and confidence scores, or inferred table rows and columns.
What are the confidence scores for?
They tell you which parts of the result to trust. Above about 85 is reliable; below 60 usually needs a human to check. Routing low-confidence fields for review is what makes an OCR pipeline dependable.
Can I use this in a script?
Yes: that is the point of the format. The output is standard JSON that parses in any language with no special handling.
How is this different from Image to Text?
Image to Text gives you a flat .txt file. This keeps the structure, positions, and confidence values that plain text discards.
Does the OCR run on a server?
No. Tesseract runs as WebAssembly in this browser tab, which matters when you are prototyping against invoices or forms belonging to your customers.
Why are the coordinates useful?
Bounding boxes let you find a value by where it sits on the page rather than by matching text, which is how most reliable form and invoice parsers work.
Is this the same as OCR to JSON?
Yes. Tesseract recognises the text in the tab and the result is written out as JSON rather than plain text: words, confidence scores and coordinates in one file you can parse directly.
Related tools
- Image to text Read the words out of a photo or screenshot.
- Image to CSV Photographed table as plain CSV.
- Image to Excel Photographed table into a spreadsheet.
- OCR a PDF Make a scanned PDF searchable, or pull the text out.
- JSON formatter Format, minify, and validate JSON.
- PDF to Text Pull the words out as plain .txt.
