OCRmyPDF vs OCR.space
OCRmyPDF is faster; only OCR.space supports tables, bounding boxes.
OCRmyPDFocrmypdf/ocrmypdf | OCR.spaceocrspace/ocr-space | |
|---|---|---|
| Type | Open source | OCR API |
| Price | 1 credit / page | 1 credit / page |
| Per 1,000 pages | $1.00 | $1.00 |
| Typical speed | 1.0 s / page | 1.5 s / page |
| Best for | Searchable PDFs from scans | Cheap simple OCR |
| Inputs | PDF, images | PDF, images |
| Languages | 100+ languages (via Tesseract) | 20+ languages |
| Max pages per request | 1,000 | 100 |
| Tables | No | ✓ Yes |
| Handwriting | No | No |
| Math | No | No |
| Bounding boxes | No | ✓ Yes |
| Confidence | No | No |
| Forms | No | No |
| Multilingual | ✓ Yes | ✓ Yes |
| On OCRRouter | Coming soon | Coming soon |
Prices are what you pay on OCRRouter. Speed is the provider's typical figure, not a benchmark we ran.
What each one is
OCRmyPDF
Command-line tool that adds a searchable text layer to scanned PDFs, using Tesseract.
OCRmyPDF detailsOCR.space
Low-cost OCR API with a large free tier. Returns text, word boxes and searchable PDFs.
OCR.space detailsUse one, fall back to the other
Request body
{
"model": "ocrmypdf/ocrmypdf",
"fallbacks": ["ocrspace/ocr-space"],
"file_url": "https://example.com/document.pdf"
}