MiniCPM V 4.7 1B needs about 1.6 GB of memory at Q4_K_M (a 0.7 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 31 quants, from 0.4 GB (F16) to 2.0 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 1.6 GB.
MiniCPM‑V 4.7 1B – a lightweight vision‑enabled LLM
MiniCPM‑V 4.7 1B is a 1 billion‑parameter model built on the qwen35 architecture. It supports single‑image, multi‑image, and video understanding with efficient visual encoding. The model is available in multiple GGUF quantizations for local inference.
Good at
- Vision‑enabled text generation
- Efficient on‑device inference
- Supports mixed 4x/16x visual token compression
Limits
- No text‑only mode, requires vision input
- Requires at least 1.3 GB VRAM for 8 k context (approx.)
- Licensed under Apache‑2.0
Best for
- Mobile on‑device chat assistants
- Embedded vision‑based QA
- Low‑resource local inference
Who it’s for. Developers building on‑device applications that need both language and vision capabilities within a 1 B parameter budget. The model is suitable for mobile, IoT, and edge deployments that support GGUF and llama.cpp.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| F16 | 0.4 GB | 1.3 GB | Fits | Get file → | |
| IQ3_XS | 0.6 GB | 1.5 GB | Fits | Get file → | |
| IQ3_XS | 0.6 GB | 1.5 GB | Fits | Get file → | |
| IQ3_M | 0.6 GB | 1.5 GB | Fits | Get file → | |
| IQ3_M | 0.6 GB | 1.5 GB | Fits | Get file → | |
| IQ4_XS | 0.6 GB | 1.5 GB | Fits | Get file → | |
| IQ4_XS | 0.6 GB | 1.5 GB | Fits | Get file → | |
| Q4_0 | 0.6 GB | 1.5 GB | Fits | Get file → | |
| Q4_0 | 0.6 GB | 1.5 GB | Fits | Get file → | |
| Q4_K_S | 0.6 GB | 1.6 GB | Fits | Get file → | |
| Q4_K_S | 0.6 GB | 1.6 GB | Fits | Get file → | |
| IQ4_NL | 0.7 GB | 1.6 GB | Fits | Get file → | |
| IQ4_NL | 0.7 GB | 1.6 GB | Fits | Get file → | |
| Q4_K_M | 0.7 GB | 1.6 GB | Fits | Get file → | |
| Q4_K_M | 0.7 GB | 1.6 GB | Fits | Get file → | |
| Q4_1 | 0.7 GB | 1.6 GB | Fits | Get file → | |
| Q4_1 | 0.7 GB | 1.6 GB | Fits | Get file → | |
| Q5_0 | 0.7 GB | 1.6 GB | Fits | Get file → | |
| Q5_K_S | 0.7 GB | 1.6 GB | Fits | Get file → | |
| Q5_0 | 0.7 GB | 1.6 GB | Fits | Get file → | |
| Q5_K_S | 0.7 GB | 1.6 GB | Fits | Get file → | |
| Q5_K_M | 0.8 GB | 1.7 GB | Fits | Get file → | |
| Q5_K_M | 0.8 GB | 1.7 GB | Fits | Get file → | |
| Q5_1 | 0.8 GB | 1.7 GB | Fits | Get file → | |
| Q5_1 | 0.8 GB | 1.7 GB | Fits | Get file → | |
| Q6_K | 0.8 GB | 1.7 GB | Fits | Get file → | |
| Q6_K | 0.8 GB | 1.7 GB | Fits | Get file → | |
| Q8_0 | 1.1 GB | 2.0 GB | Fits | Get file → | |
| Q8_0 | 1.1 GB | 2.0 GB | Fits | Get file → | |
| F16 | 2.0 GB | 2.9 GB | Fits | Get file → | |
| F16 | 2.0 GB | 2.9 GB | Fits | Get file → |
For 8 GB VRAM, use Q4_K_M (0.67 GB) or Q5_K_M (0.75 GB) for a good balance of size and speed. If memory is tighter, IQ3_XS (0.55 GB) or IQ4_XS (0.64 GB) are viable. For maximum quality, F16 (0.44 GB) offers the best precision within the same memory budget.
What GPU do you need for MiniCPM V 4.7 1B?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: the best quant that fits is F16 (2.0 GB file, about 2.9 GB in use).
Which MiniCPM V 4.7 1B quant should you choose?
Q4_K_M is the usual starting point for MiniCPM V 4.7 1B: it balances file size and quality well. Here it is a 0.7 GB file.
The Q8_0 file is 1.1 GB, about 1.6 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
If memory is tight, the smallest file is F16 at 0.4 GB, with the quality trade-offs that come with fewer bits. The unquantized model. It gives original quality and needs the most memory, so it is mainly for conversion or reference.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about MiniCPM V 4.7 1B
How much VRAM does MiniCPM V 4.7 1B need?
About 1.6 GB at Q4_K_M with an 8K context window. That is the 0.7 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run MiniCPM V 4.7 1B on an 8 GB GPU?
Yes, with F16: the 2.0 GB file needs about 2.9 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of MiniCPM V 4.7 1B GGUF?
It depends on the quant: F16 is 0.4 GB, IQ3_XS is 0.6 GB, IQ3_XS is 0.6 GB, IQ3_M is 0.6 GB, IQ3_M is 0.6 GB, IQ4_XS is 0.6 GB and 25 more.
What context length does MiniCPM V 4.7 1B support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.4 GB at 8K and 1.6 GB at 32K.
Where can I download MiniCPM V 4.7 1B GGUF?
The files are on Hugging Face in the openbmb/MiniCPM-V-4.7-1B-gguf repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does MiniCPM V 4.7 1B use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run MiniCPM‑V 4.7 1B on 8 GB VRAM?
Yes, using a quantization such as Q4_K_M or Q5_K_M will keep VRAM usage below 8 GB for 8 k context.
Does the model support text‑only inference?
No, the model is vision‑enabled and requires image input for its capabilities.
What license applies to this model?
The model is released under the Apache‑2.0 license.