Skip to main content
Jina AI's 3.4B MoE document parser running efficiently on a low-budget GPU, demonstrating accessibility.

Editorial illustration for Jina AI Releases 3.4B MoE Document Parser for Low-Budget GPUs

Jina AI's 3.4B MoE Parser Runs on Budget GPUs

Jina AI Releases 3.4B MoE Document Parser for Low-Budget GPUs

4 min read

Jina AI, the Berlin-based search and embeddings company now under Elastic, released jina-ocr-v1 this week, a document parser built to run on GPUs most labs can actually afford. The model takes a PDF, a scanned invoice or a chart-heavy report and turns it into clean Markdown in a single pass, tables rendered as HTML, formulas in LaTeX. That's the pitch, anyway: 3.4 billion parameters total, but only about 570 million decoder parameters active per token, thanks to a mixture-of-experts setup that routes each token through 6 of 64 experts. Jina AI says it targets hardware like the NVIDIA L4, a card built for inference budgets rather than flagship training rigs.

The company built jina-ocr-v1 on top of DeepSeek-OCR, keeping its two-stage encoder-decoder design rather than starting from scratch. Weights are open at roughly 6.8 GB in BF16, compatible with Transformers or vLLM, though the CC BY-NC 4.0 license restricts commercial use without contacting Jina directly. On benchmarks, the technical report cites scores on OmniDocBench v1.6 and olmOCR-Bench. What makes the release notable isn't just the size class, it's a decoding trick baked into the checkpoint itself.

On 1 A100 40 GB at concurrency 32, jina-ocr-v1 parses 2.57 pages per second. That is the highest of 14 systems Jina AI measured, against 1.22 for olmOCR-2 and 0.38 for chandra-ocr-2.

Why this matters For teams running document pipelines at scale, throughput often matters more than a leaderboard win. Jina AI isn't claiming the top accuracy score, dots.mocr and chandra-ocr-2 both beat it on olmOCR-Bench, but 2.57 pages per second on a single A100 40GB is more than double olmOCR's 1.22, and the model was built to run on something as cheap as an L4. That's a real signal for founders sizing GPU budgets around OCR-heavy products: invoice processing, scanned archives, table extraction at volume.

The 570M active decoder parameters against 3.4B total, plus the built-in speculative decoding head, explain where the speed comes from without requiring a separate serving setup. The 7.4-point jump over the raw DeepSeek-OCR backbone also tells us post-training tuning did real work here, not just architecture choice. Researchers evaluating document AI should read the olmOCR-Bench gap honestly: this is a speed-for-accuracy trade, not a universal upgrade.

Whether that trade holds up outside Jina's own 14-system benchmark is the thing worth testing before betting a production pipeline on it.

Common Questions Answered

How does jina-ocr-v1's mixture-of-experts architecture reduce computational requirements?

jina-ocr-v1 uses a mixture-of-experts setup to activate only about 570 million decoder parameters per token, despite having 3.4 billion total parameters. This selective activation significantly reduces memory and computational demands, making the model feasible to run on affordable GPUs like the L4, rather than requiring expensive high-end hardware.

What is the throughput performance of jina-ocr-v1 compared to other OCR systems?

On a single A100 40GB GPU at concurrency 32, jina-ocr-v1 parses 2.57 pages per second, which is more than double olmOCR-2's 1.22 pages per second and significantly faster than chandra-ocr-2's 0.38 pages per second. This makes it the highest performing system among the 14 OCR solutions Jina AI measured in their benchmarks.

What document formats and output types does jina-ocr-v1 support?

jina-ocr-v1 processes PDFs, scanned invoices, and chart-heavy reports, converting them into clean Markdown format in a single pass. The model renders tables as HTML and formulas as LaTeX, providing structured and usable output for various document types.

Why is jina-ocr-v1 significant for teams running document pipelines at scale?

For large-scale document processing operations, throughput and cost-efficiency are often more critical than achieving the highest accuracy scores. jina-ocr-v1 delivers more than double the throughput of competing systems while being designed to run on budget-friendly GPUs, making it ideal for founders building OCR-heavy products like invoice processing and scanned archive systems.

Who developed jina-ocr-v1 and what is their background?

jina-ocr-v1 was released by Jina AI, a Berlin-based search and embeddings company that is now under Elastic. The company specializes in creating efficient AI models for practical applications like document parsing and information retrieval.

LIVE00:06Anthropic Says Claude Leads Research, But Its AI Judge Could Repeat Errors