MiniCPM5 1B needs about 1.4 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 5 quants, from 0.7 GB (Q4_K_M) to 2.2 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 0.8 GB.
MiniCPM5 1B – a 1B‑parameter Llama‑style model for local, long‑context use
MiniCPM5 1B is a 1,080,632,832‑parameter causal language model built for on‑device deployment. It supports a 131,072‑token context window and hybrid reasoning with built‑in think/no‑think modes. The model is released under the apache‑2.0 license.
Good at
- Long‑context reasoning
- Tool‑use and coding tasks
- Hybrid think mode
Limits
- No vision support
- Requires 8k context for memory estimates
- No mixture of experts
Best for
- Local assistants
- Coding agents
- Tool‑use workflows
Who it’s for. Developers and researchers needing a compact, long‑context LLM for local inference. The model is suitable for edge devices and CPU‑only setups.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 0.7 GB | 1.4 GB | Fits | Get file → | |
| Q5_K_M | 0.8 GB | 1.5 GB | Fits | Get file → | |
| Q6_K | 0.9 GB | 1.6 GB | Fits | Get file → | |
| Q8_0 | 1.2 GB | 1.9 GB | Fits | Get file → | |
| F16 | 2.2 GB | 2.9 GB | Fits | Get file → |
For 8 GB VRAM, use Q4_K_M (file size 0.69 GB, estimated 1.4 GB memory at 8k context). If 16 GB VRAM is available, Q5_K_M (0.79 GB, 1.5 GB memory) or Q6_K (0.89 GB, 1.6 GB memory) are suitable. For higher precision, Q8_0 (1.15 GB, 1.9 GB memory) or F16 (2.17 GB, 2.9 GB memory) can be used with larger GPUs.
What GPU do you need for MiniCPM5 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.2 GB file, about 2.9 GB in use).
Which MiniCPM5 1B quant should you choose?
Q4_K_M is the usual starting point for MiniCPM5 1B: it balances file size and quality well. Here it is a 0.7 GB file.
The Q8_0 file is 1.2 GB, about 1.7 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.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about MiniCPM5 1B
How much VRAM does MiniCPM5 1B need?
About 1.4 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 MiniCPM5 1B on an 8 GB GPU?
Yes, with F16: the 2.2 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 MiniCPM5 1B GGUF?
It depends on the quant: Q4_K_M is 0.7 GB, Q5_K_M is 0.8 GB, Q6_K is 0.9 GB, Q8_0 is 1.2 GB, F16 is 2.2 GB.
What context length does MiniCPM5 1B support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 0.2 GB at 8K and 0.8 GB at 32K.
Where can I download MiniCPM5 1B GGUF?
The files are on Hugging Face in the Abiray/MiniCPM5-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 MiniCPM5 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 MiniCPM5 1B on 8 GB VRAM?
Yes, the Q4_K_M quantization requires about 1.4 GB of VRAM at 8k context, which fits in 8 GB.
Does MiniCPM5 1B support vision tasks?
No, the model does not include vision capabilities.
What is the maximum context length?
The model supports a context length of 131,072 tokens.