Tesseract vs OCRmyPDF
Pick Tesseract when you need raw text, hOCR, TSV, ALTO or PAGE output from clean printed scans, or want to call the engine from your own code. Pick OCRmyPDF when the input is a scanned PDF and the output must be a searchable PDF/A for archiving. OCRmyPDF runs Tesseract inside, so recognition accuracy is the same. The difference is the PDF handling around it.
Tesseracttesseract/tesseract | OCRmyPDFocrmypdf/ocrmypdf | |
|---|---|---|
| Type | Open source | Open source |
| Price | Free | 1 credit / page |
| Per 1,000 pages | $0.00 | $1.00 |
| Typical speed | 0.6 s / page | 1.0 s / page |
| Best for | Clean printed text, free | Searchable PDFs from scans |
| Inputs | PDF, images | PDF, images |
| Languages | 100+ languages | 100+ languages (via Tesseract) |
| Max pages per request | 500 | 1,000 |
| Tables | No | No |
| Handwriting | No | No |
| Math | No | No |
| Bounding boxes | No | No |
| Confidence | No | No |
| Forms | No | No |
| Multilingual | ✓ Yes | ✓ Yes |
| 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 Tesseract if
- You need hOCR, TSV, ALTO or PAGE XML output, which OCRmyPDF does not produce.
- You want a CLI or C++ library you can embed, working on images as well as PDFs.
- You want to control preprocessing yourself, such as binarization, deskew and roughly 300 DPI input, which the docs advise.
Choose OCRmyPDF if
- You need validated searchable PDF/A by default for archiving or compliance.
- You want the OCR layer inserted losslessly where possible, without re-encoding other content.
- You process many pages and want work spread across all CPU cores automatically.
Key differences
| Tesseract | OCRmyPDF | |
|---|---|---|
| Licence | Apache-2.0 | MPL-2.0 |
| How you run it | Local CLI or C++ library with an LSTM recognizer; CPU only | Local command-line tool that adds a Tesseract text layer to scanned PDFs; CPU only |
| Output formats | Plain text, hOCR, searchable PDF, TSV, ALTO, PAGE | Searchable PDF/A, plain text |
| Languages | More than 100 out of the box, and can be trained for more | 100+ through Tesseract language packs |
| Parallelism | Not published | Distributes work across all CPU cores |
| Price | Free, self-hosted (you pay for compute) | Free, self-hosted (you pay for compute) |
| Known failure | Confuses digit 1 with lowercase l (issue #2753); no table, formula or reading-order output | --skip-text with default PDF/A output removes form fields (issue #1790); --deskew --clean-final can double or quadruple file size (issue #948); hangs on PDFs whose forms share one Resources dictionary (issue #1763) |
Sources
- Tesseract GitHub README
- Improving quality (tessdoc)
- Issue #2753 1 vs l
- OCRmyPDF GitHub README
- Issue #948 file size
- Issue #1790 form fields
What each one is
OCRmyPDF
Command-line tool that adds a searchable text layer to scanned PDFs, using Tesseract.
OCRmyPDF detailsTry 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": "tesseract/tesseract","fallbacks": ["ocrmypdf/ocrmypdf"],"file_url": "https://example.com/document.pdf"}Questions
More comparisons
Tesseract vs RapidOCRTesseract vs EasyOCRPaddleOCR (PP-OCR) vs OCRmyPDFDocling vs OCRmyPDFAmazon Textract vs TesseractPaddleOCR-VL vs TesseractDocling vs TesseractPaddleOCR-VL vs OCRmyPDF
Tesseract alternativesOCRmyPDF alternativesBest OCR models in 2026