What Is PaddleOCR-VL-1.5?

Updated

PaddleOCR-VL-1.5 is a multi-task vision-language model with 0.9B parameters, built for robust document parsing in real-world conditions. According to the ERNIE Blog post announcing it, the model reaches 94.5% accuracy on OmniDocBench v1.5, which the post describes as a new state-of-the-art result on that benchmark. It is the right thing to look at if your problem is extracting structured content from messy, in-the-wild documents rather than clean, scanned pages.

What the release announcement says

The ERNIE Blog entry, dated January 29, 2026, frames PaddleOCR-VL-1.5 as an upgrade to an earlier model and highlights three things:

  • Task type: multi-task document parsing, meaning one model handles several parsing-related jobs rather than a separate model per task.
  • Scale: 0.9B parameters, small relative to the large foundation models covered elsewhere on the blog.
  • Result: 94.5% accuracy on OmniDocBench v1.5, reported as SOTA at the time of the post.

The phrase "in-the-wild" in the title signals the intended difficulty: documents that vary in layout, scan quality, and formatting, not a single controlled template.

How it fits alongside the other ERNIE releases

The blog covers several distinct model lines, and PaddleOCR-VL-1.5 is the document-parsing specialist among them:

Model Scale Primary focus
PaddleOCR-VL-1.5 0.9B Multi-task document parsing
ERNIE-Image 8B DiT Text-to-image generation
ERNIE 5.0 2.4T Unified multimodal understanding and generation
ERNIE 5.1 Not stated in post Agent, reasoning, and creative capabilities

The practical distinction: ERNIE 5.0 and 5.1 are general-purpose multimodal models, while PaddleOCR-VL-1.5 is a compact, task-specific model. If your workload is document parsing at volume, a 0.9B model is a different cost and latency profile than a trillion-parameter foundation model — though the blog post does not publish serving costs or deployment requirements, so verify those before committing.

What to check before adopting it

The blog post gives you the headline claim but not the full evaluation detail. Before you decide, confirm:

  1. Benchmark scope. 94.5% on OmniDocBench v1.5 is a single benchmark. Check which document types and languages it covers, and whether your documents resemble that distribution.
  2. Task coverage. "Multi-task" is not enumerated in the post. Confirm which parsing outputs (text, tables, formulas, layout) the model actually produces.
  3. Deployment path. The post does not state licensing, weights availability, or serving requirements. Look for the model card or repository before planning integration.
  4. Comparison baseline. Compare against whatever parser you use today on a sample of your own documents — that is a more reliable signal than a leaderboard number.

A reasonable way to test it: take 50–100 of your messiest real documents, run them through PaddleOCR-VL-1.5 and your current pipeline, and compare field-level extraction accuracy rather than overall character accuracy. That tells you whether the in-the-wild robustness claim holds for your data.