StackMap
Subscribe

Unlimited-OCR vs xberg

Baidu's open OCR VLM that parses entire multi-page documents in one shot — 'unlimited' long-horizon parsing pushing DeepSeek-OCR further. MIT weights on HF; serve via transformers, vLLM or SGLang. — versus — Rust-core document-intelligence engine with 15 language bindings: turns 96 formats — PDF, Office, images, audio, code — into clean text, tables and RAG-ready chunks. Library, CLI, REST or MCP.

The curated verdict

Engine vs model: xberg parses 96 formats deterministically; Unlimited-OCR throws a VLM at whole documents. Same slot in a RAG ingestion pipeline.

Unlimited-OCRxberg
Stars14k8.7k
Forks1.2k520
LanguagePythonRust
LicenseMITMIT
Last activity14 days ago2 days ago
Topicsocr, ragocr, rag, local
Curated connections55

Unlimited-OCR — the curator's take

The current bar if you batch-parse long PDFs: one-shot multi-page parsing keeps cross-page structure (tables spanning pages, running sections) that page-by-page OCR pipelines lose, and first-party vLLM/SGLang recipes plus official Docker images make serving unusually painless for a fresh research model. NOT a lightweight dependency — it's a GPU-hungry VLM; for occasional single pages classic OCR or a hosted API is cheaper. Inference-only repo: no training code, and evaluation beyond the paper's claims is on you.

xberg — the curator's take

The polyglot pick: reach for Xberg when your stack spans Rust, Python, Node, Go, the JVM or WASM and you want ONE extraction engine instead of a per-language pipeline. Handles 96 formats — PDFs, Office, images, audio/video (Whisper), even source code (306 languages, syntax-aware chunking) — with pluggable OCR (Tesseract/PaddleOCR/VLM), no GPU, and library/CLI/REST/MCP entry points. It's the v1 successor to Kreuzberg. Don't reach for it if you only need max-fidelity parsing of messy scanned PDFs (a dedicated VLM like MinerU or olmocr wins there), or if you're Python-only and already committed to LlamaIndex's own readers.