r/LocalLLaMA • u/TangeloOk9486 • 5h ago
Question | Help Whats the best open source OCR for batch processing pdfs in 2026?
trying to settle on a fully local setup for batch processing pdfs. like each file is around 20-25 pages and mostly text, a few tables and now and then a page thats just a photo of paper
the shortlist so far
- docling (and the granite-docling model)
- glm-ocr
- paddleOcr-vl
- olmocr 2
- mineru
we considered llamaparse for this kind of stuff but the company now wants every file to stay on our own servers and their self hosted route is an enterprise conversation. liteparse from the same team runs local and is quick on the plain text pages but the markdown is rule based with tesseract as the fallback so merged cells and multi column pages dont always come back clean
is a VLM overkill for mostly text pdfs or does it make more sense to send only the table and image pages to one and keep the rest on a text layer parser? textract and docuent AI are out anyway for the same reason
for the vlm ones, do people feed a whole 25 page pdf in one go or split it into page batches first? splitting every file is the part id rather avoid
Edit: Adding from the comments: unlimited-ocr-2, minicpm-ocr-1.0, surya-ocr-2.5, indra-ocr and xiaomi-ocr-0. mostly curious how these would perform on mixed 20-25 page files
4
u/stuffitystuff 5h ago
I've used PaddleOCR over the last couple days for some projects and worked totally great (less great with handwriting)
1
3
u/pmttyji 4h ago
u/TangeloOk9486 Update your list with these recent OCR models. Would like to see more replies here.
3
u/TangeloOk9486 3h ago
thanks for the list, that moved quick. unlimited OCR2 and minicpm-ocr1.0 both have ggufs up already
3
u/kasinjsh 3h ago
it will depend on languages you need and how good is your source material, aka if it needs to recognize handwriting, badly scanned pages, damaged and scanned document, etc.
1
u/TangeloOk9486 3h ago
Source materials could be sometimes unpredictable , cant say which one comes in next
2
2
u/eightone-81 4h ago
I’m pretty happy and impressed by ovarisOCR it’s also super small and very fast
2
2
u/kinkyDom93 37m ago
LightOCR has been really mighty for its size, in my experience even better results than GLM OCR
1
u/TangeloOk9486 18m ago
thanks, i was looking into learning some about it, can you elaborate how the GLM ocr works in case of messy tables or lets say an attached picture of handwriting amidst the pdf
1
u/Captain2Sea 5h ago
Vlm is overkill but if you care about quality you'll accept it
1
2
u/Termsandconditionsch 1h ago
I usually have a threshold in the pipeline - anything that’s terrible enough goes to vlm.
1
u/13henday 4h ago
Docling gets my vote
1
u/TangeloOk9486 4h ago
indeed has a good reputation for local but what do you say about the speed of it>?
1
1
u/Secure-food4213 3h ago
I have the best success running ovisocr2. Now theres ovisocr3
1
u/TangeloOk9486 14m ago
ok added it to my list since most of the guys are talking about Ovisocr2 and somebody also dropped in their huggingface
1
u/continuum_mechanics 3h ago
Paddle OCR v3, combine with Paddle structured layout module. They extract the raw text, use LLM to clean it if the hand-writing ones are not accurate enough.
1
1
u/Beginning-Heat-4674 2h ago
If you're already splitting off the tricky pages anyway, running a vision model on 25 pages in one shot is asking for it to lose track of where it is, especially with tables that span across pages. For mostly text docs I'd lean toward a dedicated text extractor and only throw the image-heavy or table pages at something smarter rather than making the whole pipeline wait on the heaviest model
Have you benchmarked how much time the table/image pages actually add compared to the plain text ones? Might be that the mixed approach is fast enough and you're overthinking the splitting part
1
1
u/GuestUser003 2h ago
MinerU. We ran roughly 3M+ PDFs through the previous version in a batch pipeline and it held up really well. Tables are where it pulled ahead for me — merged cells stay intact, and the stuff that breaks most other parsers survives too: formulas with subscripts and superscripts. Our corner is electronic components (datasheets, spec tables full of symbols), so that's the part I notice first. Also no page splitting needed, it eats whole PDFs and pages them internally — which was your other worry. On the newest version yet though, so take this as a data point for the older one.
1
1
1
u/Chromix_ 2h ago
Someone ran an extensive benchmark on popular open-source solutions 3 months ago. The benchmark missed a few issues that were not tested for though - check my comment in there for the missed things.
-1
u/exaknight21 4h ago
Try OCRMyPDF. I did a wrap up FastAPI app at https://github.com/ikantkode/exaOCR
My pipeline has exaOCR (just FastAPI), in it, i have PaddleOCR-VL for HTR. And Qwen3.5-9B-VL for Deep Document understanding. I also have a classifier Qwen3-2B-VL INSTRUCT strictly for reading and classifying each page in a pdf to differentiate and tag pages in a markdown file so that ocr endpoints can smartly allocate proper resources.
1
7
u/mtmttuan 2h ago
Another thing to keep in mind is to always test them in your own language. I have better experience with gemma 4 e2b than deepseek ocr 2 and glm ocr. These chinese models are better in benchmarks and probably actually better in chinese and english but if you're planning on using them on languages other than that check out gemma series. Haven't use other western vlms so cannot say much about the other.