MiniCPM3 4B needs about 10.8 GB of memory at Q4_K_M (a 2.5 GB file) with an 8K context window, so it fits on a 12 GB GPU. This repository has 2 quants, from 2.5 GB (Q4_K_M) to 8.2 GB. Longer context needs more: at 32K tokens the KV cache alone adds about 31.2 GB.
MiniCPM3‑4B – 4B‑parameter LLM with 32k context
MiniCPM3‑4B is a 4‑billion‑parameter language model with a 32k token context window. It supports function call and code interpreter. The model is trained on a large multilingual corpus and offers general usage capabilities.
Good at
- Function call and code execution
- 32k context handling
- Versatile general language tasks
Limits
- No vision support
- License not specified
- Requires 8k context for memory estimates
Best for
- Chatbots needing long context
- Code generation with function calls
- Research prototyping
Who it’s for. Developers and researchers who need a compact model with extended context and function call support. It is suitable for local deployment on machines with moderate GPU memory.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 2.5 GB | 10.8 GB | Too big | Get file → | |
| — | 8.2 GB | 16.5 GB | Too big | Get file → |
For 8‑GB VRAM use the Q4_K_M quantized file (2.47 GB, ~10.8 GB RAM at 8k context). For larger budgets the 8.15 GB file provides higher precision but needs more memory (~16.5 GB at 8k context).
What GPU do you need for MiniCPM3 4B?
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: no quant fits at an 8K context.
- 6 GB VRAM: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: the best quant that fits is Q4_K_M (2.5 GB file, about 10.8 GB in use).
- 16 GB VRAM: the best quant that fits is Q4_K_M (2.5 GB file, about 10.8 GB in use).
- 24 GB VRAM: the best quant that fits is the main file (8.2 GB file, about 16.5 GB in use).
Which MiniCPM3 4B quant should you choose?
Q4_K_M is the usual starting point for MiniCPM3 4B: it balances file size and quality well. Here it is a 2.5 GB file.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about MiniCPM3 4B
How much VRAM does MiniCPM3 4B need?
About 10.8 GB at Q4_K_M with an 8K context window. That is the 2.5 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 MiniCPM3 4B on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 10.8 GB, so you would need a larger GPU or CPU offloading.
What is the file size of MiniCPM3 4B GGUF?
It depends on the quant: Q4_K_M is 2.5 GB, file is 8.2 GB.
What context length does MiniCPM3 4B support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 7.8 GB at 8K and 31.2 GB at 32K.
Where can I download MiniCPM3 4B GGUF?
The files are on Hugging Face in the openbmb/MiniCPM3-4B-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
Can I run MiniCPM3‑4B on 8 GB VRAM?
Yes, the Q4_K_M quantized model fits 8 GB VRAM and uses about 10.8 GB of RAM at 8k context.
Does MiniCPM3‑4B support image input?
No, the model does not have vision capabilities.