Granite Docling vs GOT-OCR 2.0
Pick Granite Docling for English PDFs with tables, code and equations, especially inside a Docling pipeline on CPU or a small GPU. Pick GOT-OCR 2.0 for formulas, sheet music, chemical structures, region-specific OCR, or English and Chinese pages. The main split is scope: Granite Docling (258M) converts documents into structured output, while GOT-OCR 2.0 (580M) reads a wider range of content types.
Granite Doclingibm/granite-docling | GOT-OCR 2.0stepfun/got-ocr-2 | |
|---|---|---|
| Type | Open source | Open source |
| Price | 1 credit / page | 1 credit / page |
| Per 1,000 pages | $1.00 | $1.00 |
| Typical speed | 1.5 s / page | 1.5 s / page |
| Best for | Small-model document conversion | Formatted text, formulas and charts |
| Inputs | PDF, images | images |
| Languages | English, experimental CJK and Arabic | Chinese, English |
| Max pages per request | 500 | 100 |
| Tables | ✓ Yes | ✓ Yes |
| Handwriting | No | No |
| Math | ✓ Yes | ✓ Yes |
| Bounding boxes | ✓ Yes | ✓ Yes |
| Confidence | No | No |
| Forms | No | No |
| Multilingual | No | No |
| On OCRRouter | Available | Available |
Prices are what you pay on OCRRouter. Speed is the provider's typical figure, not a benchmark we ran.
Which to choose
Choose Granite Docling if
- You want table structure from English PDFs: IBM reports TEDS 0.97 on FinTabNet at 150dpi.
- You run Docling and want output as DocTags, Markdown, HTML, LaTeX or bounding boxes from a 258M-parameter model that is Apache-2.0 licensed.
- You need low-cost conversion on CPU or a small GPU, and your pages are mostly English with code and equations (code F1 0.988, equation F1 0.968 per the model card).
Choose GOT-OCR 2.0 if
- You need formulas, sheet music, chemical structures or charts, with output as LaTeX, TikZ, SMILES or kern.
- You want to OCR one region of a page, guided by box coordinates or color, or run multi-page OCR with dynamic resolution.
- Your documents are English or Chinese. Granite Docling marks Chinese as experimental.
Key differences
| Granite Docling | GOT-OCR 2.0 | |
|---|---|---|
| Size | 258M parameters | 580M parameters |
| Licence | Apache-2.0 | Code Apache-2.0; training data CC BY-NC 4.0 |
| Output formats | DocTags, Markdown, HTML, LaTeX, bounding boxes | Plain text, Markdown, LaTeX, TikZ, SMILES, kern |
| How you run it | Self-hosted, typically inside Docling. On GPUs without bfloat16 such as T4, run in float32 or it may output only exclamation marks. vLLM needs the untied revision. | Self-hosted, available in Hugging Face Transformers with batched inference. README lists CUDA 11.8 and PyTorch 2.0.1; CPU users are pointed to a llama.cpp port. |
| Published benchmarks | Table TEDS 0.97 (FinTabNet), full-page OCR F1 0.84, equation F1 0.968, OCRBench 500, all from the authors | Not published |
| Languages | English primary; Japanese, Arabic and Chinese experimental | English and Chinese documents |
| Known failure | Repetitive loops on page headings and invoices (HF discussion #24) | Looping characters midway through recognition (issue #226); wrong text instead of empty output on images with no text (issue #235); format mode much worse than plain OCR mode (issue #317) |
Sources
- Granite-Docling model card
- HF discussion #24 repetition
- GOT-OCR2.0 GitHub
- GOT-OCR 2.0 paper
- GitHub issue index
What each one is
Granite Docling
Compact IBM vision model that converts pages to DocTags for the Docling pipeline.
Granite Docling detailsGOT-OCR 2.0
Unified OCR model that reads plain text, tables, formulas, sheet music and charts.
GOT-OCR 2.0 detailsTry both on your own file
Run the file once with each model and compare the output.
Use one, fall back to the other
{"model": "ibm/granite-docling","fallbacks": ["stepfun/got-ocr-2"],"file_url": "https://example.com/document.pdf"}Questions
More comparisons
Granite Docling alternativesGOT-OCR 2.0 alternativesBest OCR models in 2026