AIToday
Large Language ModelsOpen-Source AIQiita 機械学習Published: Oct 31, 2026, 16:00 JST

Baidu's Unlimited-OCR-2 gets a local workbench on a 16GB GPU

Send on LINE
Baidu's Unlimited-OCR-2 gets a local workbench on a 16GB GPU

3 Key Points

  1. What happened

    Baidu open-sourced Unlimited-OCR-2, a 3B vision-language OCR model, and a developer's lumichy-unlimited-OCR workbench ran it on an RTX 5060 Ti 16GB with a 0.401-second time to first token and 40.32 seconds of total inference.

  2. Why it matters

    The workbench keeps document parsing entirely on-premise, so sensitive contracts, medical records, and legal files never leave the machine, and the model's SR-SWA attention design holds VRAM roughly constant even across hundreds of pages.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The pitch is aimed at teams already paying per-page fees or sending files to cloud OCR services. The developer contrasts Unlimited-OCR-2 with Tesseract, which is free but breaks down on multi-column layouts, formulas, and merged-cell tables, and with cloud OCR APIs that charge per page and take data off-site. The workbench, distributed on GitHub as lumichy/lumichy-unlimited-OCR, wraps the model in FastAPI with a WebSocket feed that streams GPU utilization, VRAM, CPU load, and temperature every 1.2 seconds, plus PyMuPDF for on-demand page rasterization and four output views for rendered, Markdown, raw-tag, and log output.

The core architectural claim is that Unlimited-OCR-2 avoids the memory explosion that crashes conventional vision-language models on long PDFs. Its SR-SWA attention compresses the necessary reference region into a fixed-length sparse working reference, and Unlimited-Horizon Decoding carries the required key-value cache across page boundaries while purging local cache that is no longer needed, so multi-page tables and sentences that continue across pages stay coherent.

The demo is honest about limits. Native BF16 inference kept VRAM at a 15.26 GB peak of 15.93 GB, or 95.8%, which the developer describes as uncomfortably close to the ceiling, and the author notes that 8GB to 12GB GPUs would likely need future INT4/INT8 quantization or a vLLM backend. Throughput of 30 to 40 seconds per page rules out high-frequency real-time use, pointing instead to overnight batch processing or one-off deep analysis of a paper or book.

FAQ
What hardware do I need to run it?
Native BF16 inference needs a CUDA GPU with at least 12GB of VRAM; 16GB or more is recommended as the safe zone. The demo ran on an NVIDIA GeForce RTX 5060 Ti with 16GB of VRAM.
How fast is it on long documents?
Expect roughly 30 to 40 seconds of inference per page, which the developer says suits overnight batch jobs or carefully analyzing a single paper or book rather than high-frequency real-time APIs.
What can it output that older OCR tools can't?
It extracts structured Markdown, KaTeX/LaTeX math, and merged-cell HTML tables, so formulas and complex tables come out directly copy-pasteable instead of collapsing into plain text.
Qiita 機械学習Read Original Article
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleEasyProver clears all 189 VERINA tasks with zero fine-tuning