Parameter count has never equaled capability, and MiniCPM-V 4.6 proves it again. Released on May 11, 2026 by OpenBMB (ModelBest) together with Tsinghua University, this on-device multimodal model uses only 1.3B parameters — a 0.8B language model plus the SigLIP2-400M vision encoder — yet scores 13 on the Artificial Analysis Intelligence Index, beating its own language backbone Qwen3.5-0.8B (10 points) and even the 3B-class Ministral 3. This is not "small enough to run" — it is "small enough to win."
Architecture: Why 1.3B Outperforms 3B
| Component | Model | Parameters | Role | |------|------|--------|------| | Vision encoder | SigLIP2-400M | 400M | Image feature extraction | | Language model | Qwen3.5-0.8B | 0.8B | Text reasoning, output | | Merger | Window-Attention Merger | - | Visual token compression | | Total | - | 1.3B | Runs on-device |
Two key design decisions:
1. Compression inside the ViT. Traditional pipelines compress tokens only after the ViT finishes processing. MiniCPM-V 4.6 moves compression into the ViT itself, cutting compute by more than 50%. 2. Switchable 4x/16x hybrid visual token compression. 4x mode for high precision, 16x mode for maximum speed — a runtime "gear switch" rather than a fixed setting.
Efficiency numbers
| Metric | MiniCPM-V 4.6 | Qwen3.5-0.8B | Comparison | |------|---------------|--------------|------| | Token throughput | 1.5x baseline | 1x | 50% faster | | Compute tokens consumed | ~5.4M | ~100M | Only 1/19 | | VRAM (Q4) | ~1.6 GB | - | Minimal | | RAM requirement | 6 GB | - | Phone-capable | | First-token latency | Milliseconds | - | Real-time interaction |
Same hardware, 19x the traffic — not an optimization, but a restructuring of the cost curve.
Capabilities
- Single-image understanding: captioning, VQA, OCR
- Multi-image understanding: cross-image comparison and sequential reasoning
- Video understanding: temporal analysis, frame-level reasoning, 128K context for long videos
- Tool calling: native function calling, usable as an agent vision module
- Document parsing: invoices, PDFs, screenshots, handwriting
- Thinking mode: optional chain-of-thought reasoning
- In-ViT compression (architecture level)
- Hybrid compression ratios (runtime level)
- SigLIP2 vision encoding (pretraining level)
- Qwen3.5 language backbone (language model level)
- Offline on-device OCR and document scanning
- Vision perception for on-device agents (screenshots, UI reading)
- High-throughput document pipelines (invoices, tables, PDFs)
- Privacy-sensitive local analysis (medical imaging, financial documents)
- Multimodal feature extraction for recommenders (the validated Kuaishou scenario)
- Team: OpenBMB (ModelBest) + Tsinghua University
- Release date: 2026-05-11
- License: Apache 2.0
- Hugging Face: https://huggingface.co/openbmb/MiniCPM-V-4.6
- GitHub: https://github.com/OpenBMB/MiniCPM-V
- Mobile demos: https://github.com/OpenBMB/MiniCPM-V-Apps
- Web demo: https://huggingface.co/spaces/openbmb/MiniCPM-V-4.6-Demo
- Supported frameworks: Ollama, vLLM, SGLang, llama.cpp, Transformers
- Fine-tuning: LLaMA-Factory, SWIFT
Industrial validation: In 2025, the same compression lineage powered Kuaishou's OneRec recommender, which served 25% of requests in the short-video main scenario — real load at hundreds of millions of DAU. MiniCPM-V 4.6 brings this proven technique down from 8B to 1.3B parameters.
Deployment
Mobile (fully open-sourced)
| Platform | Dev environment | Reference device | |---------|---------|---------| | iOS | Xcode / Swift | iPhone 17 Pro Max | | Android | Gradle / Kotlin | Redmi K70 | | HarmonyOS | DevEco / ArkTS | HUAWEI nova 14 |
Built on llama.cpp, all inference is local: offline, private, millisecond responses. The Q4_K_M quantized model is ~1.6 GB (LLM 0.5 GB + vision 1.1 GB).
Server-side options
Ollama (local testing), vLLM (high concurrency), SGLang (high-performance inference), llama.cpp (CPU/embedded), and Hugging Face Transformers (research/fine-tuning). Quantization formats cover GGUF, BNB, AWQ, GPTQ; FP16 is ~3–4 GB, INT4 ~1.5–2 GB.
Competitive Positioning
| Model | Params | Strengths | Weaknesses | Best for | |------|--------|------|------|------| | MiniCPM-V 4.6 | 1.3B | Extreme efficiency, strong OCR, low cost | Weaker complex spatial reasoning | On-device agents, document processing, OCR pipelines | | Qwen3.5-VL-2B | 2B | Alibaba ecosystem, Chinese optimization | Less efficient | Cloud Chinese apps | | Moondream | 1.8B | Minimal deployment | Weak OCR/documents | Basic captioning | | LLaVA-Phi | 3.8B | General VQA | Large, inefficient | General scene understanding | | GPT-4o | >100B | All-around | Cloud, costly, privacy risk | High-precision general tasks |
The strategy is differentiated competition: not chasing GPT-4o's versatility, but maximizing "intelligence density per parameter" among small models.
Key Judgment: Why Small Models Are Surging
MiniCPM-V has iterated from April 2024 to 4.6 under one core assumption: intelligence density > parameter scale. Traditional scaling says bigger is better; the on-device mindset says smaller and sufficient is enough. MiniCPM-V 4.6 takes a third path: maximize intelligence density within a tiny parameter budget via:
Every layer squeezes efficiency — systematic frugality, not a single trick.
Limitations and Best-Fit Use Cases
Not designed for: complex spatial reasoning ("which object is third from the left"), dense scientific chart parsing, long-video deep understanding beyond the context window, or safety-critical scenarios without dedicated safety training.
Best fit:
Bottom Line
MiniCPM-V 4.6 is not a cheap substitute for large models — it recalibrates the efficiency baseline for on-device multimodal AI. 1.3B parameters, 1.6 GB model, 6 GB RAM, a 19x token cost advantage: these numbers are not compromises, they are a new coordinate system. If you work on on-device AI, local agents, OCR pipelines, or simply want to cut multimodal serving costs, this model deserves top-priority testing.
Project info