Does it fit your GPU?
2.5B dense parameters, conventional full attention on all 42 layers (GQA, 16 query heads / 2 KV heads), 131K native context. Ships with a hybrid reasoning toggle — the same checkpoint switches between a fast no-think mode and a deliberate think mode via the chat template's enable_thinking flag, rather than needing two separate downloads.
| VRAM | Fit |
|---|---|
| 4 GB / CPU only | Q4_K_M (1.56 GB) — runs on integrated graphics or plain CPU at usable speed · 131K context |
| 8 GB | Q8_0 (2.68 GB) fully in VRAM, near-lossless, with plenty of room for context or an embedding model alongside it · 131K context |
openbmb/MiniCPM5-2B-GGUFHow to run it
Install TurboLLM
npx turbollm— no install step, works on Windows, macOS, and Linux. It detects your GPU and auto-provisions a matchingllama-serverbuild (no CUDA toolkit, no Python, no compiler).Get the model
Paste
openbmb/MiniCPM5-2B-GGUFinto TurboLLM's in-app Hugging Face search — it lists every quant with a VRAM-fit verdict against your real free VRAM, and downloads are resumable and SHA-256 verified.Let auto-fit pick the setup
Flip the auto-fit toggle and TurboLLM chooses the GPU/CPU layer split (and, for a Mixture-of-Experts model, the expert-offload split) for your card — the same manual flag-hunting every other guide walks you through by hand.
Load it
TurboLLM benchmarks the model on your exact GPU as it loads and shows the real measured tokens/sec — not a number copied from someone else's card.
Use it
Chat in the built-in UI, or point any OpenAI- or Anthropic-compatible tool (including Claude Code) at TurboLLM's local API — see the API docs.
The thinking-mode toggle lives in the chat template's enable_thinking flag. OpenBMB's own GGUF ships the template with it wired up, but a re-quant from a different uploader may not carry it — if thinking mode won't switch off, check that the GGUF you loaded came from the first-party openbmb/MiniCPM5-2B-GGUF repo.
FAQ
Which quant should I use for MiniCPM5-2B?
Pick the highest quant that fits your VRAM with room left over for the KV cache and compute buffer — not just the model weights. As a starting point, Q4_K_M is usually the sweet spot (small quality loss for a large size drop); step up to Q5_K_M/Q6_K/Q8_0 if you have headroom, or down to Q3_K_M/an IQ quant if you don't. TurboLLM shows a VRAM-fit verdict for every quant against your card's real free VRAM before you download — see Quantization explained for what the letters and numbers actually mean, or llama.cpp flags that actually matter for the other settings worth knowing.
Will MiniCPM5-2B run on my GPU?
Check the VRAM table above for the tier closest to your card. If you're not sure which tier you're in, or want picks tailored to your exact hardware, use What can I run? — enter your VRAM (or Apple unified memory) and it suggests the model, quant, and offload split that fits, the same logic TurboLLM's auto-fit runs when you load a model.
How is running MiniCPM5-2B on TurboLLM different from Ollama or LM Studio?
All three can run MiniCPM5-2B as a GGUF. The differences show up around the edges: TurboLLM auto-tunes the quant and GPU/CPU split against your card's measured free VRAM rather than a fixed default, shows real generation speed instead of a guess, and lets you add a community fork — like the one behind this page, where relevant — without compiling anything yourself. Ollama and LM Studio each ship one blessed runtime you can't swap out. If your current setup already works well for you, there's no need to switch.
Run it now
One command detects your GPU, provisions the right engine, and opens the UI. New here? Start with Install & first run and Quantization explained. On different hardware, see RTX 4060 or Apple M4 (16 GB). Also see how to run it or how to run it.