Model reference · open weights
MiniCPM-V-4.7 is an open-weight language model from openbmb. MiniCPM-V-4.7-35B-A3B-gguf (GGUF) weighs 21.2 GB; the smallest configuration that runs it is 2× RTX 3060 12 GB.
For self-hosting, compare this build's requirements below with the GPU you plan to rent.
Summary of the openbmb/MiniCPM-V-4.7-35B-A3B-gguf model card, 2026-10-13
What it is
| Released by | openbmb |
|---|---|
| Released | 2026-10-06 |
| VRAM | 21.2 GB for the weights |
What it runs on
How much memory each request adds isn't estimated yet for this architecture. The weights need at least the cards below, plus room for the context.
| Card | Weights alone |
|---|---|
| RTX 3060 12 GB … RTX 4060 Ti 16 GB 2 smaller cards | does not fit |
| RTX 3090 24 GB | tight |
| RTX 4090 24 GB | tight |
| RTX 5090 32 GB | fits |
| L40S 48 GB | fits |
| A100 80 GB | fits |
| H100 80 GB | fits |
| RTX PRO 6000 Blackwell 96 GB | fits |
| DGX Spark (GB10) 128 GB unified | fits |
| H200 141 GB | fits |
| B200 180 GB | fits |
| 2× RTX 3060 12 GB split by layers (llama.cpp) | tight |
| 2× RTX 4060 Ti 16 GB split by layers (llama.cpp) | fits |
| 2× RTX 4090 24 GB split by layers (llama.cpp) | fits |
| 2× RTX 3090 24 GB split by layers (llama.cpp) | fits |
Builds
| Build | Params | Precision | Weights | Smallest setup |
|---|---|---|---|---|
| MiniCPM-V-4.7-35B-A3B-gguf (above) ↗ 12 builds: GGUF 15.5 GB … F16 69.4 GB |
GGUF | 21.2 GB | 2× RTX 3060 12 GB | |
| MiniCPM-V-4.7-1B ↗ | 1.6B | BF16 | 3.1 GB | RTX 3060 12 GB |
| MiniCPM-V-4.7-35B-A3B-FP8 ↗ | 35.2B | FP8 | 38.0 GB | L40S 48 GB |
| MiniCPM-V-4.7-1B-GPTQ ↗ | 1.3B | GPTQ | 1.9 GB | RTX 3060 12 GB |
| MiniCPM-V-4.7-1B-AWQ ↗ | 1.6B | AWQ | 2.4 GB | RTX 3060 12 GB |
| MiniCPM-V-4.7-1B-int4 ↗ | 1.6B | INT4 | 1.6 GB | RTX 3060 12 GB |
| MiniCPM-V-4.7-35B-A3B-int4 ↗ | 7.3B | INT4 | 22.6 GB | 2× RTX 4060 Ti 16 GB |
| MiniCPM-V-4.7-35B-A3B-AWQ ↗ | 7.3B | AWQ | 22.6 GB | 2× RTX 4060 Ti 16 GB |
| MiniCPM-V-4.7-35B-A3B-GPTQ ↗ | 7.3B | GPTQ | 22.6 GB | 2× RTX 4060 Ti 16 GB |
From the model card
This repository hosts the GGUF (llama.cpp) quantized version of MiniCPM-V 4.7 35B-A3B. For the original BF16 weights and the full model card, please refer to openbmb/MiniCPM-V-4.7-35B-A3B.
On-device results · Evaluation · Examples · Usage · Model weights
MiniCPM-V 4.7 is the latest model in the MiniCPM-V series, available in a 35B-A3B variant, with 35B-A3B being the first MoE model in the MiniCPM-V series. It builds on the family's single-image, multi-image, and video understanding capabilities, combining stronger foundation capabilities with efficient visual encoding and on-device inference. Notable features of MiniCPM-V 4.7 include:
An MoE model can have far more total parameters than it activates for a single token, but its on-device storage requirements are not limited to those active parameters. Different tokens can select different experts at different layers, while device memory often cannot hold all expert weights. Without a latency constraint, weights can remain on SSD or other storage, be loaded as needed, and be released after computation. This makes large-model inference possible, but repeated loading stalls can make decoding too slow for real-time interaction.
Another approach is to restrict the pool of available experts. For example, fixing an expert subset for an entire prompt can reduce loading frequency, but limits subsequent token-level routing to that subset, potentially excluding experts the model would otherwise select and reducing its capabilities. The central goal is therefore smooth inference without compromising performance: preserving model capability while delivering sufficient throughput under limited memory and bandwidth.
MiniCPM-V 4.7 35B-A3B addresses this challenge through three complementary techniques:
Together, these techniques make MiniCPM-V 4.7 35B-A3B the first open-source MoE model to run smoothly on-device without compromising performance, achieving 13+ tokens/s on iPhone 17 Pro Max.
**On-Device MoE Inference: Before and Af
Quoted from the model card on Hugging Face. The full card is behind the Hugging Face link above.
How it works