MiniCPM5 1B needs about 1.2 GB of memory at Q4_K (a 0.6 GB file) with an 8K context window, so it fits on a 4 GB GPU. This repository has 10 quants, from 0.0 GB to 2.2 GB (F16).
MiniCPM5 1B – a 1B‑parameter Llama‑style model for local deployment
MiniCPM5 1B is a 1,080,632,832‑parameter causal language model built for on‑device use. It supports a 131,072‑token context and includes hybrid reasoning via a single checkpoint. The model is released under the Apache‑2.0 license.
Good at
- Long‑context reasoning
- Agentic tool use
- Code generation
Limits
- No vision support
- Requires 131,072‑token context
- No mixed‑expert architecture
Best for
- Local assistant applications
- Coding agent workflows
- Reasoning tasks on edge devices
Who it’s for. Developers and researchers who need a compact, long‑context LLM that can run on commodity hardware. The model is suitable for local assistants, coding agents, and reasoning workflows where resource constraints matter.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 0.0 GB | 0.5 GB | Fits | Get file → | |
| — | 0.2 GB | 0.8 GB | Fits | Get file → | |
| Q2_K | 0.3 GB | 0.9 GB | Fits | Get file → | |
| Q3_K | 0.5 GB | 1.0 GB | Fits | Get file → | |
| Q4_K | 0.6 GB | 1.2 GB | Fits | Get file → | |
| Q5_K | 0.7 GB | 1.3 GB | Fits | Get file → | |
| Q6_K | 0.9 GB | 1.5 GB | Fits | Get file → | |
| Q7_K | 1.0 GB | 1.6 GB | Fits | Get file → | |
| Q8_0 | 1.2 GB | 1.8 GB | Fits | Get file → | |
| F16 | 2.2 GB | 2.9 GB | Fits | Get file → |
For 8 GB VRAM, the Q4_K quant (~1.2 GB file) is a good balance of size and memory. If 4 GB VRAM is available, use Q3_K (~1 GB). For the smallest footprint, Q2_K (~0.9 GB) fits in 2 GB VRAM but may be slower. Estimates are approximate.
What GPU do you need for MiniCPM5 1B?
These figures add the file size, an fp16 KV cache at an 8K context window 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 (0.6 GB) is the middle option in this repository. The usual sweet spot between file size and quality, and the quant most people start with.
If memory is tight, the smallest file is the first one in the table at 0.0 GB, with the quality trade-offs that come with fewer bits.
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.2 GB at Q4_K with an 8K context window. That is the 0.6 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: file is 0.0 GB, file is 0.2 GB, Q2_K is 0.3 GB, Q3_K is 0.5 GB, Q4_K is 0.6 GB, Q5_K is 0.7 GB and 4 more.
What context length does MiniCPM5 1B support?
The GGUF header lists a trained context length of 131,072 tokens (128K).
Where can I download MiniCPM5 1B GGUF?
The files are on Hugging Face in the eaddario/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 quant (~1.2 GB file) requires about 1.2 GB of VRAM at 8 k context, which fits in 8 GB. The larger F16 quant (~2.9 GB) would exceed 8 GB.
Does MiniCPM5 1B support vision tasks?
No, the model has no vision capabilities.