FAQ

Document AI

Text extraction and OCR datasets

Scene text, invoices, document parsing and structured forms — the cases where recognition is still hard.

Recognition of clean printed text is largely solved, so the datasets that matter are the ones covering everything that is not clean.

Before collecting data for this, test an off-the-shelf engine on your documents. If they are clean printed text in a Latin script, you may need no training data at all, and that is the cheapest possible outcome.

Where training is still needed: handwriting, which varies without limit between writers; historical documents with period typography, degradation and archaic orthography; scene text photographed at an angle under uncontrolled lighting; low-resolution scans and faxes; non-Latin scripts, particularly those with complex shaping or right-to-left ordering; and structured documents where recovering the layout matters as much as the characters. The sets below cover scene text, invoices and document parsing; handwriting beyond MNIST's isolated digits, and historical documents, need sources not on this list.

Six panels of word images in different Indian scripts, rendered in varied fonts, colours, curves and backgrounds, some on photographic textures.
Synthetic word images in six Indian scripts (clockwise from top left: Gujarati, Hindi, Bangla, Tamil, Telugu and Malayalam). Characters join along a top line in Hindi and Bangla, and vowel signs sit above and below the base characters, so an engine tuned on Latin print has much more to learn. Rendering words like these is a common way to cover scripts with little labelled data. Image: Figure 4 of the article · CC BY 4.0 · from Gunna et al. 2022, Journal of Imaging, “Improving Scene Text Recognition for Indian Languages with Transfer Learning and Font Diversity”, doi:10.3390/jimaging8040086
DatasetModalitySizeLicenceBest for
Text Extraction for OCRMultimodal1,560 imagesCC0Invoice-specific entity extraction
OCRFlux Bench SingleText2,000 pagesApache 2.0OCR accuracy on complex layouts
OCR BenchmarkMultimodal1,000 examplesMITOCR accuracy of multimodal models
BLIP3 OCR 200MMultimodal96M rowsResearch onlyVLMs on text-heavy images
TextOCR: Extraction of text on natural imagesImage28,134 imagesCC BY 4.0OCR on complex text
Sujet Finance QA Vision 100kMultimodal107,050 pairsApache 2.0Visual question answering for complex documents
MNISTImage70,000 imagesCC BY-SA 3.0Image classification
Licences in this shortlist — computed from the 7 datasets below. Red marks licences that are unclear or restricted; amber marks non-commercial, share-alike or mixed terms.
Panel (a) shows thirteen cropped scene-text images each captioned with a filename from word_1.png to word_13.png, including a price '$500', handwritten 'who', a 'SMRT' sign, 'COACH', 'FALL', 'SEASON!', the road marking 'HUMP', 'OUT' and 'TOBACCO'; panel (b) shows the matching gt.txt file listing each filename paired with its quoted transcription.
A recognition dataset as it actually ships: cropped word images and a text file pairing each filename to its transcription. Simple enough that a single misaligned line silently poisons the run. Image: PaddlePaddle/PaddleOCR · Apache-2.0 repository
№ 01

Text Extraction for OCR

Multimodal
Size
About 1,560 invoice images (JPG/PNG) paired with XML entity annotations, including extracted tabular data
Licence
CC0: Public Domain

About 1,560 pairs of invoice images in JPG or PNG with XML files holding extracted entities such as invoice number, date, business name, telephone and address, plus extracted tabular data. A ready-made document-NER set.

What to train on it

Developing invoice-specific entity extraction, improving recognition of tabular data in complex images, and building OCR robust to typographic and quality errors.

Source: innovatiana.com

№ 02

OCRFlux Bench Single

Text
Size
2,000 annotated pages (Markdown), bilingual EN/ZH
Licence
Apache 2.0

2,000 PDF pages with manual Markdown annotations, bilingual across English and Chinese, for evaluating how accurately OCR systems parse complex layouts including titles, tables and structured text into Markdown output.

What to train on it

Measuring OCR accuracy on complex layouts, testing multilingual OCR on English and Chinese, and improving Markdown output from scanned or PDF images.

Source: innovatiana.com

№ 03

OCR Benchmark

Multimodal
Size
1,000 examples, about 386 MB, Parquet and JSON format
Licence
MIT

A 1,000-example benchmark of about 386 MB in Parquet and JSON, for comparing how well multimodal LLMs perform OCR and extract structured JSON from documents. Evaluation-sized rather than training-sized.

What to train on it

Measuring OCR accuracy of multimodal models, comparing structured JSON extraction quality across LLMs, and improving joint visual and text comprehension.

Source: innovatiana.com

№ 04

BLIP3 OCR 200M

Multimodal
Size
About 96 million rows in Parquet (image URLs with OCR text and boxes); the BLIP-3 paper describes 200 million images
Licence
Apache 2.0, but released for research purposes only; records hold image URLs and OCR metadata, not the images

Roughly 96 million Parquet rows of OCR annotations for web images that the records reference by URL rather than include, built to help vision-language models read text-heavy visuals such as documents, diagrams and screenshots. Its Hugging Face release shows about 96 million rows, against the 200 million images the BLIP-3 paper describes (the card itself says about 2 million samples), so check what a row holds before quoting a size. Salesforce releases it for research purposes only.

What to train on it

Pre-training VLMs on text-heavy images, raising OCR accuracy on real-world documents, and boosting multimodal reasoning.

Source: innovatiana.com

Five strips of generated text on grey speckled backgrounds in different fonts, weights and slants, two of them tilted, showing random dictionary words such as 'expeditionary synetic palatograph mementoes cordwainer' and 'Khaldian semiduration nonalphabetical swankiness well-allied'.
Synthetic word images from TextRecognitionDataGenerator: random words, a font, a background and some skew or blur. Generators like this produce clean printed text in any quantity, which is the case this article calls solved, and they do little for the handwriting and degraded documents where training data is still needed. Images: Belval/TextRecognitionDataGenerator · MIT repository
№ 05

TextOCR: Extraction of text on natural images

Image
Size
28,134 images, about 900,000 word annotations, JPEG and JSON
Licence
Annotations CC BY 4.0; images CC BY 2.0 (Open Images, via TextVQA)

28,134 natural-scene images from TextVQA with about 900,000 word-level polygon annotations in JSON. Polygon rather than box annotation lets it cover curved and partially occluded text. The annotations are CC BY 4.0 and the Open Images photos CC BY 2.0, so attribution is required.

What to train on it

Training OCR on complex text such as curved or partially visible words, improving VQA or multimodal captioning, and testing robustness across fonts and backgrounds.

Source: innovatiana.com

№ 06

Sujet Finance QA Vision 100k

Multimodal
Size
107,050 QA pairs, 9,801 images, structured format (JSON/image)
Licence
Apache-2.0

107,050 English question-answer pairs generated from 9,801 images of financial documents such as reports, tables and invoices, in a structured JSON and image format. Professional document VQA rather than natural scenes.

What to train on it

Developing visual question answering for complex documents, improving financial document analysis via OCR and semantic understanding, and refining multimodal LLMs.

Source: innovatiana.com

№ 07

MNIST

Image
Size
70,000 images (60,000 for training, 10,000 for testing), PNG or IDX format
Licence
Creative Commons Attribution-Share Alike 3.0 (CC BY-SA 3.0)

70,000 centred greyscale 28x28 images of handwritten digits labelled zero to nine, split 60,000 train and 10,000 test, in PNG or IDX.

What to train on it

Training image classification, benchmarking CNNs and autoencoders, demonstrating supervised pipelines, and experimenting with dimensionality reduction or GANs.

Source: innovatiana.com

A plain invoice from 'ACME Office Supplies' with a four-row item table (recycled paper A4, ballpoint pens, desk lamp, office chair) and 'Total due 1,250.00 EUR'; every word on the page is covered by a small translucent blue box.
docTR's pretrained detector and recogniser run on the clean sample invoice from its documentation: every word is found and boxed, and the documentation's printout gives the first words a confidence of 1.00. On pages like this an off-the-shelf engine needs no training data at all, which is the test to run on your own documents first. Image: mindee/doctr · Apache-2.0 repository

How this list was put together

Found by searching Dataset Finder for datasets whose documentation describes the task, then checked by hand. A keyword match is not a fit — the first pass picked up a coral survey for the depth-estimation list because it was recorded below fifty metres — so every entry was read against what this page covers, and the ones that matched a word without matching the task were removed.

Sizes and licences come from each dataset's own documentation, vague wording included. Where we found a re-upload or catalogue card stating a licence that the original release contradicts — a CC0 tag on Flickr photographs, MIT on data whose terms require a signed agreement — the entry gives the original terms and says so. The comparison table abbreviates licences; hover a cell for the full wording.

Stop hunting. Start searching.

The datasets listed on this page are in Dataset Finder, alongside tens of thousands more — searchable in plain language.

Search Dataset Finder →