OCRRouter

Google Document AI vs dots.ocr

Pick dots.ocr if you want to run OCR yourself, pay only for compute, and get Markdown with layout from multilingual PDFs. Pick Google Document AI if you want a hosted API with per-page pricing, batch jobs and RAG chunking, and you already use Google Cloud. The main split is how you run it: a metered cloud service versus an MIT-licensed 3B model you host on your own GPU.

Google Document AIgoogle/document-aidots.ocrrednote/dots-ocr
TypeOCR APIOpen source
Price10 credits / page2 credits / page
Per 1,000 pages$10.00$2.00
Typical speed1.4 s / page1.5 s / page
Best forMultilingual scansMultilingual document parsing
InputsPDF, imagesPDF, images
Languages200+ languages100+ languages
Max pages per request500500
Tables✓ Yes✓ Yes
Handwriting✓ YesNo
MathNo✓ Yes
Bounding boxes✓ Yes✓ Yes
Confidence✓ YesNo
Forms✓ YesNo
Multilingual✓ Yes✓ Yes
On OCRRouterAvailableAvailable

Prices are what you pay on OCRRouter. Speed is the provider's typical figure, not a benchmark we ran.

Which to choose

Choose Google Document AI if

  • Enterprise Document OCR costs $1.50 per 1,000 pages and drops to $0.60 above 5M pages a month, with the first 1,000 free.
  • Layout Parser includes chunking for RAG at $10 per 1,000 pages, so you do not build that step yourself.
  • Batch requests accept up to 500 pages, which suits bulk OCR runs on Google Cloud.

Choose dots.ocr if

  • There is no per-page fee. It is MIT-licensed code and you pay only for the compute you run it on.
  • One model returns layout boxes, categories and text in one pass, with tables as HTML and formulas as LaTeX, plus Markdown output.
  • The authors report 83.9 on olmOCR-bench for dots.mocr (v1.5), up from 79.1 for the original model.

Key differences

Google Document AIdots.ocr
How you run itHosted API on Google CloudSelf-hosted with vLLM or Hugging Face Transformers; a single CUDA GPU with vLLM is the documented path
LicenceProprietaryMIT (the repository also includes a separate dots.ocr license agreement file)
Price$1.50 per 1,000 pages for Enterprise Document OCR; $10 for Layout Parser; $30 for Form ParserFree; you pay for compute
Output formatsJSON, plain text, bounding boxes, chunksJSON, Markdown, HTML, LaTeX, bounding boxes, SVG
Request limitsOnline requests capped at 15 pages (30 in imageless mode); batch up to 500 pages; Form Parser batch up to 100 pagesNot published
Table quality64.6% on Reducto's RD-TableBench, independent result, behind Azure and TextractAuthors say complex tables remain difficult at this model size; a table above 1000 grid cells raises an error and drops the whole page in Docling (issue #5146)
Known failureLong PDFs do not fit in one synchronous callRuns of ellipses or underscores can make output repeat endlessly; occasional parsing failures per the README

Sources

What each one is

Google Document AI

Google Cloud OCR with layout parsing and specialised processors.

Google Document AI details

dots.ocr

Single vision model from rednote that does layout detection and content recognition together.

dots.ocr details

Try both on your own file

Run the file once with each model and compare the output.

PDF, PNG, JPG, WebP, HEIC. Up to 20 MB each, 10 files.No file?

Use one, fall back to the other

{"model": "google/document-ai","fallbacks": ["rednote/dots-ocr"],"file_url": "https://example.com/document.pdf"}

Questions

More comparisons

Google Document AI alternativesdots.ocr alternativesBest OCR models in 2026