dots.ocr vs Tesseract.js
Pick dots.ocr when you need PDFs turned into Markdown with layout, tables and formulas, and you have a CUDA GPU to host a 3B model. Pick Tesseract.js when you need simple printed text read in the browser or Node.js, with images that never leave the user's device. The main split is output: dots.ocr returns structure, Tesseract.js returns plain text, hOCR or boxes and does not take PDFs.
dots.ocrrednote/dots-ocr | Tesseract.jstesseract/tesseract-js | |
|---|---|---|
| Type | Open source | Open source |
| Price | 2 credits / page | 1 credit / page |
| Per 1,000 pages | $2.00 | $1.00 |
| Typical speed | 1.5 s / page | 2.0 s / page |
| Best for | Multilingual document parsing | OCR in the browser |
| Inputs | PDF, images | images |
| Languages | 100+ languages | 100+ languages |
| Max pages per request | 500 | 500 |
| Tables | ✓ Yes | No |
| Handwriting | No | No |
| Math | ✓ Yes | No |
| Bounding boxes | ✓ Yes | ✓ Yes |
| Confidence | No | ✓ Yes |
| 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 dots.ocr if
- You need layout boxes, categories and text from one model, with tables as HTML and formulas as LaTeX.
- You process multilingual PDFs, academic papers or business documents that mix tables and text.
- You want a published benchmark: the authors report 79.1 on olmOCR-bench for dots.ocr and 83.9 for dots.mocr (v1.5).
Choose Tesseract.js if
- You need OCR fully client side in the browser, so images never leave the user's device.
- You read clean screenshots or scans of simple printed text in any of more than 100 languages.
- You want an Apache-2.0 library that installs from npm, ESM or a CDN script tag, with no GPU or server to run.
Key differences
| dots.ocr | Tesseract.js | |
|---|---|---|
| How you run it | Self-hosted 3B model (1.7B LLM backbone) served with vLLM or Hugging Face Transformers | JavaScript and WebAssembly library in the browser or Node.js |
| Hardware | Single CUDA GPU with vLLM is the documented path. A CPU inference guide is linked. No VRAM figure is stated. | Runs on the user's device or your server. No GPU needed. |
| Licence | MIT, plus a separate dots.ocr license agreement file in the repository | Apache-2.0 |
| Output formats | JSON, Markdown, HTML, LaTeX, bounding boxes, SVG | Plain text, hOCR, bounding boxes |
| PDF input | Multilingual PDFs to Markdown with layout | Does not accept PDF files. The README points to Scribe.js for PDFs. |
| Benchmarks | olmOCR-bench 79.1 (dots.ocr) and 83.9 (dots.mocr), reported by the authors | Not published |
| Known failures | Runs of ellipses or underscores can make output repeat endlessly. A table above 1000 grid cells raised an error and dropped the whole page in a Docling issue. | Lower accuracy than the native Tesseract CLI on the same image. One Electron user measured about 15 s per page versus 1.5 s with the CLI. Fails on screen resolution text unless images are upscaled first. |
Sources
- dots.ocr GitHub README
- Docling issue #5146
- Tesseract.js GitHub README
- Issue #251 accuracy vs CLI
- HN thread
What each one is
dots.ocr
Single vision model from rednote that does layout detection and content recognition together.
dots.ocr detailsTesseract.js
Tesseract compiled to JavaScript and WebAssembly, so OCR runs in the browser or in Node.js.
Tesseract.js 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": "rednote/dots-ocr","fallbacks": ["tesseract/tesseract-js"],"file_url": "https://example.com/document.pdf"}Questions
More comparisons
dots.ocr alternativesTesseract.js alternativesBest OCR models in 2026