MiniCPM-V 4.7 35B-A3B (MoE)
MiniCPM-V 4.7 35B-A3B (MoE) needs 22 GB of VRAM at Q4_K_M with 8k context, computed from its config.json as checked on 3 November 2026. The smallest card that holds it has 24 GB, a tight fit, and the fastest desktop card that runs it, the RTX 5090, generates at most 721 tokens per second.
- Parameters
- 35.2B, 3B active
- Context
- 262,144 tokens
- Licence
- Apache 2.0
- Released
- October 2026
- Config checked
- 3 November 2026
Open MiniCPM-V 4.7 35B-A3B (MoE) in the LLM checker
Which card size runs it
22 GB against each memory size. A model may use 95% of a card, and only what is left over, or missing, is coloured; tight means above 85%, with little room for a longer conversation.
Other quantisations, context lengths or a Q8 KV cache: the VRAM calculator.
Computed 3 November 2026Which GPU to pick
The smallest card here that loads it at Q4_K_M with 8k of context is the RTX 5090 Laptop GPU (24 GB): 22 GB needed, an estimated 360 tokens per second, and a tight fit that leaves little for the conversation. For room to work, meaning 32,768 tokens of context while staying under 85% of memory, step up to the RTX 5090 (32 GB), which needs 22.5 GB for that and generates at about 721 tokens per second.
At Q8_0, which is near-lossless, the card is the RTX A6000 (48 GB), needing 39.5 GB. On Apple silicon, a Mac mini M4 Pro holds it with 32,768 tokens of context at an estimated 110 tokens per second; prompt processing is slower than on Nvidia, which long documents make obvious. Among unified-memory desktops, the Ryzen AI Max+ 395 holds it at 32,768 tokens in 22.5 GB, at an estimated 103 tokens per second.
Speed on each card
| GPU | Fits | Est. tokens/s | Feels like | Memory | Bandwidth |
|---|---|---|---|---|---|
| H100 SXM | Yes | ≤ 1,348 | faster than you can read | 80 GB | 3,350 GB/s |
| A100 | Yes | ≤ 820 | faster than you can read | 80 GB | 2,039 GB/s |
| RTX 5090 | Yes | ≤ 721 | faster than you can read | 32 GB | 1,792 GB/s |
| RTX PRO 6000 Blackwell | Yes | ≤ 721 | faster than you can read | 96 GB | 1,792 GB/s |
| RTX PRO 5000 Blackwell | Yes | ≤ 541 | faster than you can read | 48 GB | 1,344 GB/s |
| RTX 4090 | Tight | ≤ 406 | faster than you can read | 24 GB | 1,008 GB/s |
| RX 7900 XTX | Tight | ≤ 386 | faster than you can read | 24 GB | 960 GB/s |
| RTX 6000 Ada | Yes | ≤ 386 | faster than you can read | 48 GB | 960 GB/s |
| RTX 3090 | Tight | ≤ 377 | faster than you can read | 24 GB | 936 GB/s |
| RTX 5090 Laptop GPU | Tight | ≤ 360 | faster than you can read | 24 GB | 896 GB/s |
| RTX PRO 4500 Blackwell | Yes | ≤ 360 | faster than you can read | 32 GB | 896 GB/s |
| L40S | Yes | ≤ 348 | faster than you can read | 48 GB | 864 GB/s |
| RTX A6000 | Yes | ≤ 309 | faster than you can read | 48 GB | 768 GB/s |
| RTX PRO 4000 Blackwell | Tight | ≤ 270 | faster than you can read | 24 GB | 672 GB/s |
| Radeon AI PRO R9700 | Yes | ≤ 257 | faster than you can read | 32 GB | 640 GB/s |
| Arc Pro B70 | Yes | ≤ 245 | faster than you can read | 32 GB | 608 GB/s |
| Arc Pro B60 | Tight | ≤ 183 | faster than you can read | 24 GB | 456 GB/s |
| RTX PRO 4000 Blackwell SFF | Tight | ≤ 174 | faster than you can read | 24 GB | 432 GB/s |
| RTX Spark | Yes | ≤ 121 | faster than you can read | 128 GB (102 for the GPU) | 300 GB/s |
| DGX Spark | Yes | ≤ 110 | faster than you can read | 128 GB (126 for the GPU) | 273 GB/s |
| Ryzen AI Max+ 395 | Yes | ≤ 103 | faster than you can read | 128 GB (96 for the GPU) | 256 GB/s |
| RX 7900 XT | No | - | does not fit | 20 GB | 800 GB/s |
| RTX 4060 Ti | No | - | does not fit | 16 GB | 288 GB/s |
| RTX 5060 Ti | No | - | does not fit | 16 GB | 448 GB/s |
| RTX 5080 | No | - | does not fit | 16 GB | 960 GB/s |
| RTX 5070 Ti | No | - | does not fit | 16 GB | 896 GB/s |
| RTX 4080 SUPER | No | - | does not fit | 16 GB | 736 GB/s |
| RX 9070 XT | No | - | does not fit | 16 GB | 640 GB/s |
| RX 9060 XT | No | - | does not fit | 16 GB | 320 GB/s |
| RTX 3060 | No | - | does not fit | 12 GB | 360 GB/s |
| RTX 4070 | No | - | does not fit | 12 GB | 504 GB/s |
| RTX 5070 | No | - | does not fit | 12 GB | 672 GB/s |
| Arc B580 | No | - | does not fit | 12 GB | 456 GB/s |
Single-stream decode, from memory bandwidth at 70% efficiency. Prompt processing and batching not included. These are ceilings, not measurements: MiniCPM-V 4.7 35B-A3B (MoE) reads only 1.7 GB of weights per token at Q4, so little that the per-token costs the formula leaves out decide much of the real speed. The 21 figures marked ≤ are where a real runtime falls furthest below the number shown. See the speed estimator for other quantisations and Apple hardware, or every card compared if you are choosing hardware rather than a model.
Computed 3 November 2026Memory by quantisation and context
| Quant | 4,096 ctx | 8,192 ctx | 32,768 ctx |
|---|---|---|---|
| Q8_0 | 39.4 GB · fits 48 GB | 39.5 GB · fits 48 GB | 40 GB · fits 48 GB |
| Q5_K_M | 26.6 GB · fits 32 GB | 26.7 GB · fits 32 GB | 27.2 GB · fits 32 GB |
| Q4_K_M | 21.9 GB · fits 24 GB | 22 GB · fits 24 GB | 22.5 GB · fits 24 GB |
Weights at this quant: 20.4 GB at Q4. Every extra 1,000 tokens of context adds about 0.02 GB of KV cache at FP16, on top of a fixed 0.06 GB of recurrent state that does not grow. Try other settings in the VRAM calculator.
About the model
MiniCPM-V 4.7 35B-A3B (MoE) has 35.2B parameters with 3B active per token (mixture of experts). It has 40 layers, of which only 10 are full attention (2 KV heads of dimension 256) and keep a cache that grows with the conversation; the other 30 are Gated DeltaNet linear-attention layers with a small fixed state. OpenBMB's MiniCPM-V 4.7 from October 2026, the first mixture-of-experts model in its MiniCPM-V vision series: 35B of weights with 3B read per token, on a Qwen3.5 and Qwen3.6 language backbone with a SigLIP2 vision encoder. It reads single images, several images at once, and video.
Text, images and video 262,144-token window Apache 2.0 October 2026 3B of 35.2B active
Reasoning. The card's examples run with thinking off. Its GGUF repos keep it off in the main files and turn it on in a separate thinking/ folder.
All 256 experts stay in memory; 3B are active per token. The parameter count includes the vision encoder; a text-only GGUF is slightly smaller.
Native context window: 262,144 tokens. Licence: Apache 2.0, a permissive licence. Weights published in October 2026.
Good at
- Documents, screenshots and video, locally: OCR, PDF parsing and visual grounding each get their own guide on the card.
- Mixture-of-experts speed: only 3B parameters are read per token.
- More official formats than most releases: GGUF, AWQ, GPTQ and FP8 builds from OpenBMB, and an Ollama model.
- Apache 2.0.
Watch out for
- All 35B of weights sit in memory to read 3B per token: it is fast, not small. The card says so itself: an MoE model's storage needs are "not limited to those active parameters".
- The phone speed on the card comes from OpenBMB's own llama.cpp fork and a draft model, not from plain llama.cpp.
- Transformers needs version 5.18 or later.
- The hybrid layers need a current runtime. On an older build, expect the 2025 arithmetic.
Similar models
The models that need about the same memory as MiniCPM-V 4.7 35B-A3B (MoE) at Q4_K_M and 8k, which makes them the real alternatives on whatever card you have. The context column is what each extra 1,000 tokens costs, and it is where models of the same size differ most.
| Model | Size | Needs | Per 1k context | Window | Released |
|---|---|---|---|---|---|
| MiniCPM-V 4.7 35B-A3B (MoE) | 35.2B · 3B active | 22 GB | 0.02 GB | 256k | 2026-10 |
| Nanbeige4.3 33B | 33.1B | 22.2 GB | 0.213 GB | 512k | 2026-10 |
| Qwen3 32B | 32.8B | 22.4 GB | 0.262 GB | 40k | 2025-04 |
| DeepSeek-R1 Distill Qwen 32B | 32.8B | 22.4 GB | 0.262 GB | 128k | 2025-01 |
| Qwen2.5 Coder 32B | 32.8B | 22.4 GB | 0.262 GB | 32k | 2024-11 |
See every model compared, which models fit on 8 to 96 GB, or the cheapest hour of every cloud card.
Questions
- Can I run MiniCPM-V 4.7 35B-A3B (MoE) on a 24 GB card?
- Yes, at Q4_K_M and 8k context it needs about 22 GB, which fits a 24 GB card tightly.
- How much VRAM does MiniCPM-V 4.7 35B-A3B (MoE) need at Q8?
- About 39.5 GB at 8k context, or 40 GB at 32k. Q8 is near-lossless; use it when it fits.
- What is the context length of MiniCPM-V 4.7 35B-A3B (MoE)?
- 262,144 tokens natively. Holding all of it at Q4_K_M takes about 27.2 GB, of which 5.4 GB is context.
- Why does MiniCPM-V 4.7 35B-A3B (MoE) need so little memory for long context?
- Because most of its layers do not keep a cache that grows. It has 40 layers, of which only 10 are full attention (2 KV heads of dimension 256) and keep a cache that grows with the conversation; the other 30 are Gated DeltaNet linear-attention layers with a small fixed state. At 32k tokens the context costs about 0.7 GB; if all 40 layers kept a conventional full-length cache, the same conversation would cost about 2.7 GB.
- How fast is MiniCPM-V 4.7 35B-A3B (MoE) on an RTX 4090?
- At most about 406 tokens per second at Q4, single stream, which is faster than you can read. That is a ceiling worked out from the card's memory bandwidth, not a measurement, and at a figure this high real runtimes land well below it, because the costs the formula leaves out take a growing share of each token.
- Architecture values from config.json in openbmb/MiniCPM-V-4.7-35B-A3B on Hugging Face, and its model card, checked 3 November 2026. Every figure on this page is computed from those values; check them before buying hardware for this model.
- Estimates assume a single conversation on a card that is otherwise free. A desktop on the same GPU takes 0.5 to 2 GB.