OCRRouter

Tesseract.js vs Chunkr

Pick Tesseract.js when you need OCR inside a browser or Node.js app and images must stay on the user's device. Pick Chunkr when you need to parse PDFs, slides and Word files into Markdown, HTML or JSON for RAG, because Tesseract.js does not accept PDF and returns no layout or Markdown.

Tesseract.jstesseract/tesseract-jsChunkrchunkr/chunkr
TypeOpen sourceOCR API
Price1 credit / page14 credits / page
Per 1,000 pages$1.00$14.00
Typical speed2.0 s / page3.0 s / page
Best forOCR in the browserLayout-aware chunks for RAG
InputsimagesPDF, images, DOCX
Languages100+ languagesMultilingual
Max pages per request5001,000
TablesNo✓ Yes
HandwritingNoNo
MathNo✓ Yes
Bounding boxes✓ Yes✓ Yes
Confidence✓ YesNo
FormsNoNo
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 Tesseract.js if

  • Runs fully client side in the browser, so images never leave the user's device.
  • Apache-2.0 licence with npm, ESM and CDN script tag installs, and no closed-use restriction.
  • Supports more than 100 languages through Tesseract traineddata files.

Choose Chunkr if

  • Accepts PDF, PPT, Word and images, while Tesseract.js does not accept PDF.
  • Returns HTML, Markdown, JSON and OCR with bounding boxes, so it suits RAG chunking of PDFs and slides.
  • Offers both a cloud API and a self-host version via Docker, with GPU, CPU-only and Mac ARM options.

Key differences

Tesseract.jsChunkr
How you run itJavaScript and WebAssembly library in the browser or Node.jsCloud API or self-hosted Docker (GPU, CPU-only, Mac ARM)
LicenceApache-2.0AGPL-3.0 or commercial licence; closed-source products need the commercial licence
PriceFree, self-hosted on the user's device or your serverHosted credit-based plans, prices not published; open-source version is free but you pay for compute and an LLM endpoint
Input formatsImages only; no PDF input (the README points to Scribe.js for PDFs)PDF, PPT, Word and images; no Excel in the open-source version
Output formatsPlain text, hOCR, bounding boxesHTML, Markdown, JSON, bounding boxes
Tables and layoutNot supported; no table, layout or Markdown outputLayout analysis and semantic chunking
Known failureLower accuracy than the native Tesseract CLI on the same image; fails on screen resolution text unless upscaled; one Electron user measured about 15 s per page versus 1.5 s with the CLIOpen-source version uses community models, less accurate than the cloud's in-house models; self-host still needs an external LLM endpoint

Sources

What each one is

Tesseract.js

Tesseract compiled to JavaScript and WebAssembly, so OCR runs in the browser or in Node.js.

Tesseract.js details

Chunkr

Document parsing API that segments and chunks pages for RAG. Self-hostable version available.

Chunkr 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": "tesseract/tesseract-js","fallbacks": ["chunkr/chunkr"],"file_url": "https://example.com/document.pdf"}

Questions

More comparisons

Tesseract.js alternativesChunkr alternativesBest OCR models in 2026