OpenBMB Releases Quantized Versions of MiniCPM-OCR-Jev

OpenBMB Releases Quantized Versions of MiniCPM-OCR-Jev

At a Glance

Item Value
Repository openbmb/MiniCPM-OCR-Jev-GPTQ
Family guide MiniCPM-OCR-Jev guide (1 articles)
Publisher guide OpenBMB: models and licenses
Published 2026-10-26
License apache-2.0
Formats safetensors
Source type Primary source (the publisher itself)

Values determined by this site’s code when the information was collected. Dates are JST.

Overview

openbmb has released quantized versions (in GPTQ and AWQ formats) of “MiniCPM-OCR-Jev", a model designed for OCR quality evaluation. Given text, formula, or table region images along with candidate OCR results, this model returns a score from 0 to 1 indicating the likelihood that the candidate is correct.

This model is designed to automatically accept reliable regions, route uncertain ones to human review, or select the optimal result among multiple OCR models.

Specifications

Specifications for the source model, MiniCPM-OCR-Jev, are as follows:

  • Number of parameters: 2B
  • Architecture: Based on Qwen3.5-2B, with the language model output head replaced by a binary classification head

Performance

The released quantized versions inherit the performance of the source MiniCPM-OCR-Jev model. According to evaluations in the model card, the decision AUROC (×100) on JevOCRBench is 93.6. Despite having 2B parameters, it outperforms JEV-35B-A3B (90.1) and approaches the performance of Qwen3.5-397B-A17B (93.8).

It also demonstrates stable versatility against analysis results from other OCR models, with AUROC (×100) ranging between 91.9 and 93.4 when using analysis results from MiniCPM-OCR 1.0, GLM-OCR, PaddleOCR-VL-1.6, and Xiaomi-OCR-0.

A comparison of discrimination performance for each OCR model, as stated in the model card, is as follows:

→ Scroll horizontally to see all columns

OCR model MiniCPM-OCR 1.0 GLM-OCR PaddleOCR-VL-1.6 Xiaomi-OCR-0
AUROC (×100) 92.7 91.9 93.4 93.1

This table shows that MiniCPM-OCR-Jev can accurately distinguish the correctness of results generated by existing OCR models such as MiniCPM-OCR 1.0, PaddleOCR-VL-1.6, and Xiaomi-OCR-0.

Strengths and Use Cases

MiniCPM-OCR-Jev functions as a powerful tool to ensure the reliability of OCR processing in document analysis. It proves particularly valuable in quality control when automatically digitizing large volumes of documents.

Specific operational scenarios include the following three:
– Automation and efficiency in OCR workflows: Based on the scores calculated by this model, you can build a workflow where highly reliable results are directly fed into the system, while only “suspicious" low-score sections are extracted and presented to humans. This maintains high analysis accuracy while eliminating the effort of human verification for every single item.
– Accuracy improvement through ensemble methods: Run multiple OCR engines (such as MiniCPM-OCR 1.0, PaddleOCR-VL-1.6, and Xiaomi-OCR-0) on the same image region, and evaluate each output with this model. By adopting the candidate that achieves the highest score as the final result, you can obtain more accurate analysis results even for complex formulas, tables, or text with special fonts that are prone to misreading by a single model.
– Support for diverse regions: A major strength is its ability to determine consistency with images with high precision not only for text, but also for regions traditionally difficult to evaluate with standard OCR, such as formulas and tables.

When integrating into a pipeline, the configuration sends document region images, categories, and text candidates output by OCR engines to the model’s inference service. The service performs internal rendering and returns an image-text alignment score. Developers can branch subsequent processing dynamically by comparing this score against a threshold.

For API usage, endpoints are available such as score for evaluating a single candidate, score_best for selecting the optimal one from multiple candidates, and score_best_batch for processing multiple blocks together. Additionally, when using inference results, it is recommended to verify not just the numerical score, but also that verdict (the judgment status) is set to scored. This prevents errors such as rendering failures or pre-check errors from being mistakenly treated as low scores.

Hardware Requirements

Estimated requirements (calculated by Local Model Watch) — 2.2B parameters (taken from the base model openbmb/MiniCPM-OCR-Jev)

Your VRAM Quantization File size Est. memory needed
4GB (laptop iGPU / phone class) GPTQ 4bit 2.2GB 2.7GB

Inference engine support (architecture name matched against each project’s own model registry in its source code, checked 2026-11-17): llama.cpp: not registered, vLLM: not registered, MLX (mlx-lm): registered. “Not registered" means the name is absent from that registry today, not that the model cannot run.

Memory estimates add a 20% runtime overhead (KV cache, etc.) to the actual size of the distributed files. Actual usage varies with context length, batch size and inference engine. These figures are computed by this site from file sizes, not published by the model’s authors. Compare with other models in our VRAM quick reference. What the quantization names mean: glossary.

Can You Run It Locally?

Runs in Ollama, LM Studio and llama.cpp via a converted build.

The publisher ships safetensors, but openbmb/MiniCPM-OCR-Jev-gguf provides a GGUF build you can use.

License — apache-2.0 (Commercial use allowed): Permits commercial use, modification and redistribution. Redistribution requires including the license and stating changes; includes a patent grant.

Compiled by this site’s code from the published formats, converted builds we have found, and each engine’s own model registry. “Not found" means we have not seen such a build, not that none exists. License summaries are not legal advice — check the publisher’s original terms before relying on them.

Recent Models in the Same Size Class

Models with up to 4B parameters that Local Model Watch covered recently, listed by code from our article log for comparison. VRAM tiers are this site’s estimates; licenses are as stated on the model cards.

→ Scroll horizontally to see all columns

Model Parameters Smallest VRAM tier License Our article
LiquidAI/d1-omni-600M 587M 4GB lfm1.0 d1-omni-600M Multimodal Decision Model: 4GB+ VRAM, GGUF Builds (2026-11-17)
LiquidAI/d1-3B 3.1B 4GB lfm1.0 d1-3B Vision-Language Model: 4GB+ VRAM, GGUF Builds (2026-11-17)
baidu/Unlimited-OCR-2 3.3B 8GB mit Unlimited-OCR-2 Vision-Language Model: 8GB+ VRAM (2026-11-17)
openbmb/MiniCPM-OCR-1.0-DSpark 297M 4GB apache-2.0 MiniCPM-OCR-1.0-DSpark OCR Acceleration Draft Model: 4GB+ VRAM (2026-11-17)
LiquidAI/d1-2B-GGUF 1.9B 4GB lfm1.0 d1-2B-GGUF Text, Image, and Video Decision-Making Model: 4GB+ VRAM (2026-11-17)

How to Get It

The newly released models are 4-bit quantized (W4A16) in GPTQ and AWQ formats. They are distributed in safetensors format under the Apache-2.0 license. Hugging Face gating (agreement to terms of use) is not required, and anyone can download and start using them without restrictions.

vLLM is supported as an inference engine, and you can spin up an API server loading the model locally or on a server by running the following commands:

Startup command for the GPTQ version:

vllm serve openbmb/MiniCPM-OCR-Jev-GPTQ \
  --served-model-name MiniCPM-OCR-Jev \
  --trust-remote-code

Startup command for the AWQ version:

vllm serve openbmb/MiniCPM-OCR-Jev-AWQ \
  --served-model-name MiniCPM-OCR-Jev \
  --trust-remote-code

Additionally, the “Quick start" section of the model card provides links to deployment guides for various other backends such as SGLang, llama.cpp (GGUF format), Ollama, and FlagOS. A system is in place allowing users to select and deploy the optimal format for their infrastructure environment and preferred inference engine.

Quantized and Converted Variants

→ Scroll horizontally to see all columns

Added Publisher Format Repository Smallest VRAM tier (build, est. memory)
2026-10-28 openbmb GGUF openbmb/MiniCPM-OCR-Jev-gguf Q8_0 2.2GB (fits in 4GB VRAM)

File sizes of each build:

  • Available builds in openbmb/MiniCPM-OCR-Jev-gguf: IQ3_XS 1.0GB / IQ3_M 1.0GB / IQ4_XS 1.1GB / Q4_0 1.1GB / Q4_K_S 1.1GB / IQ4_NL 1.2GB / Q4_K_M 1.2GB / Q4_1 1.2GB / Q5_0 1.3GB / Q5_K_S 1.3GB / Q5_K_M 1.3GB / Q5_1 1.4GB / Q6_K 1.4GB / Q8_0 1.9GB / F16 3.5GB

This section is appended automatically by Local Model Watch when a converted build of this model appears after publication. Memory figures are estimated from the size of the distributed files. What the quantization names mean: glossary.

Related Articles

What to Read Next

Sources