Claude vs Chunkr
Pick Claude to read, question or extract from long PDFs when you want reasoning and page-level citations. Pick Chunkr when you need bounding boxes, layout-aware chunks for RAG, or a self-hosted parser. The main split is that Claude is a hosted, token-priced language model with no bounding boxes, while Chunkr is a parsing service you can run yourself.
Claudeanthropic/claude | Chunkrchunkr/chunkr | |
|---|---|---|
| Type | Vision model | OCR API |
| Price | 25 credits / page | 14 credits / page |
| Per 1,000 pages | $25.00 | $14.00 |
| Typical speed | 2.6 s / page | 3.0 s / page |
| Best for | Long dense documents | Layout-aware chunks for RAG |
| Inputs | PDF, images | PDF, images, DOCX |
| Languages | 50+ languages | Multilingual |
| Max pages per request | 100 | 1,000 |
| Tables | ✓ Yes | ✓ Yes |
| Handwriting | ✓ Yes | No |
| Math | ✓ Yes | ✓ Yes |
| Bounding boxes | No | ✓ Yes |
| 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 Claude if
- You want document question answering or summaries of long reports, with page-level citations from the API.
- You need extraction to JSON with reasoning, and each page is read as both text and a rendered image, so charts and scans are visible.
- You send large files: up to 600 pages per request on 1M-context models (100 pages otherwise) and a 32 MB payload.
Choose Chunkr if
- You need OCR with bounding boxes, which Claude is not suited for.
- You want to self-host with Docker (GPU, CPU-only or Mac ARM) and use any OpenAI-compatible LLM endpoint.
- You are chunking PDFs, slides, Word files or images for RAG and want HTML, Markdown or JSON output.
Key differences
| Claude | Chunkr | |
|---|---|---|
| How you run it | Hosted API only | Cloud API or self-hosted open-source version |
| Licence | Proprietary | AGPL-3.0 or commercial licence; closed-source products need the commercial licence |
| Pricing | Per token, no extra PDF fee; a PDF page typically uses 1,500 to 3,000 tokens plus image tokens | Hosted credit-based plans (prices not verified); open-source version is free but you pay for compute and an LLM endpoint |
| Output formats | Markdown, JSON, plain text | HTML, Markdown, JSON, bounding boxes |
| Bounding boxes | Not suited to pipelines that need them | OCR with bounding boxes |
| Input and limits | PDFs and images; up to 600 pages per request on 1M-context models (100 otherwise), 32 MB; password-protected or encrypted PDFs not supported | PDF, PPT, Word and images; Excel not supported in the open-source version |
| Known weakness | Bulk OCR is costly versus per-page OCR APIs; no published OmniDocBench score | Open-source version uses community models that are less accurate than the cloud's; self-host still needs an external LLM endpoint |
Sources
What each one is
Chunkr
Document parsing API that segments and chunks pages for RAG. Self-hostable version available.
Chunkr 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": "anthropic/claude","fallbacks": ["chunkr/chunkr"],"file_url": "https://example.com/document.pdf"}Questions
More comparisons
Claude vs ABBYY FineReaderClaude vs UnstructuredLlamaParse vs ChunkrGPT vs ChunkrPixtral vs ChunkrGOT-OCR 2.0 vs ChunkrGoogle Document AI vs ChunkrClaude vs Unlimited OCR
Claude alternativesChunkr alternativesBest OCR models in 2026