llmrun
litert-communityMiniCPM

MiniCPM5 1B — Hardware Requirements & GPU Compatibility

Chat

MiniCPM5 1B is a 1B-parameter open language model from litert-community in the MiniCPM family. At Q4_K_M it needs about 0.66 GB of VRAM — see which GPUs and Macs can run it below.

1B params · denseApache 2.07 likes
Based on MiniCPM5 1B
S

Runs great on a 24 GB GPU

Runs from8 GB Q4_K_M · 32KBest on24 GB Q4_K_M · ~993 tok/s · 32KMacs from8 GB Q4_K_M · ~109 tok/s

Apache 2.0

Reference GPU · RTX 4090 24 GB

Estimates, ±20% · how we estimate

Run MiniCPM5 1B

One recommended way. Every other method, OS and quant is in the step-by-step guide.

Recommended

vLLM
one command · needs vLLM installed
$vllm serve litert-community/MiniCPM5-1B --max-model-len 16384

vLLM repo with its own quantisation

Download: Weights on Hugging Face

install, OS, other quants

Other ways

each opens step-by-step

Run in cloud

Fits on RTX 3060 12GB (9 GB headroom) · Q4_K_M

Generation speed
~355 tok/s
generation speed
Cost per 1M output tokens
$0.059
per 1M output tokens

How Much VRAM Does MiniCPM5 1B Need?

Select a quantization level; the listed hardware adheres to it.

QuantizationVRAM+32KOn RTX 4090 (reference)
0.5 GB3.5 GB2-bit · K-quant — 2-bit quantization with K-quant improvementsFits: 32K context · ~1394 tok/s
0.5 GB3.6 GB3-bit medium — 3-bit medium quantizationFits: 32K context · ~1213 tok/s
0.7 GB3.7 GB4-bit medium — 4-bit medium quantization — most popular sweet spotFits: 32K context · ~993 tok/s
0.8 GB3.9 GB5-bit medium — 5-bit medium quantization — good quality/size tradeoffFits: 32K context · ~840 tok/s
0.9 GB4 GB6-bit, very good — 6-bit quantization, very good qualityFits: 32K context · ~720 tok/s
1.1 GB4.2 GB8-bit, near-lossless — 8-bit quantization, near-losslessFits: 32K context · ~596 tok/s
2.2 GB5.3 GB16-bit · bfloat — Brain floating point 16 — preferred for trainingFits: 32K context · ~298 tok/s
est.calculated, no published file yet

Selected Q4_K_M

4-bit medium quantization

2.1GBat 16K context

Weights
0.2 GB
KV cache
1.6 GB
Overhead
0.3 GB

Fits RTX 4090 (reference) · 21.9 GB free · ~993 tok/s

≥50 tok/s needs ≥51 GB/s · RTX 5090 ~1765, RTX 3090 Ti ~993

Which Hardware Can Run MiniCPM5 1B?

Q4_K_M · 0.7 GB

MiniCPM5 1B (Q4_K_M) requires 0.7 GB of VRAM to load the model weights. For comfortable inference with headroom for KV cache and system overhead, 1+ GB is recommended. 52 GPUs can run it, including NVIDIA GeForce RTX 5090, NVIDIA GeForce RTX 3090 Ti. 163 devices with unified memory can run MiniCPM5 1B, including Mac Studio (M3 Ultra, 256GB), Mac Studio (M3 Ultra, 512GB).

By VRAM tier · typical GPUs and Macs at Q4_K_M
8 GB · RTX 4060Q4_K_M · 2.1 GB · ~268 tok/s · 32K8 GB tier →
12 GB · RTX 3060 12GBQ4_K_M · 2.1 GB · ~355 tok/s · 32K12 GB tier →
16 GB · RTX 5060 Ti 16GBQ4_K_M · 2.1 GB · ~441 tok/s · 32K16 GB tier →
24 GB · RTX 4090referenceQ4_K_M · 2.1 GB · ~993 tok/s · 32K24 GB tier →
Mac 32 GB · Mac Mini M4Q4_K_M · 2.1 GB · ~127 tok/s · 32KMacs →
Mac 64 GB · Mac Studio M4 MaxQ4_K_M · 2.1 GB · ~579 tok/s · 32KMacs →

Alternatives to MiniCPM5 1B

MiniCPM family · 16 models →

Similar models

6
ModelScoreVRAMtok/sWhy it is similar
InternVL3 5 1BOpenGVLab—2.2 GB~936same size
InternVL3 1BOpenGVLab—2 GB~1057same size
Gemma 3 1B ITGoogle—2.1 GB~993same size
InternVL2 1BOpenGVLab—2 GB~1057same size
DiffuRefill 1BAsilarkness—2.6 GB~252same size
MobileLLM R1.5 950MMeta—3.5 GB~314same size

Specifications

Publisher
litert-community
Family
MiniCPM
Parameters
1B
Release Date
2026-06-26
License
Apache 2.0

Frequently Asked Questions

How much VRAM does MiniCPM5 1B need?

MiniCPM5 1B requires 0.7 GB of VRAM at Q4_K_M, or 2.2 GB at BF16.

VRAM = Weights + KV Cache + Overhead

Weights = 1B × 4.8 bits ÷ 8 = 0.6 GB

KV Cache + Overhead ≈ 0.1 GB (at 2K context + ~0.3 GB framework)

Fit ratings and hardware model lists check this model with room for a 16K-token context, which needs a little more memory.

VRAM usage by quantization

0.7 GB

Learn more about VRAM estimation →

What's the best quantization for MiniCPM5 1B?

For MiniCPM5 1B, Q4_K_M (0.7 GB) offers the best balance of quality and VRAM usage. Q5_K_M (0.8 GB) provides better quality if you have the VRAM. The smallest option is Q2_K at 0.5 GB.

VRAM requirement by quantization

Q2_K
0.5 GB
Q4_K_M ★
0.7 GB
Q5_K_M
0.8 GB
Q6_K
0.9 GB
Q8_0
1.1 GB
BF16
2.2 GB

★ Recommended — best balance of quality and VRAM usage.

Learn more about quantization →

Can I run MiniCPM5 1B on a Mac?

Yes — MacBook Air 13" M3 (8 GB) and 145 other Macs can run MiniCPM5 1B. Apple Silicon uses unified memory, so the model shares RAM with the system. At Q4_K_M you need at least 0.7 GB of usable unified memory (RAM minus macOS overhead).

Can I run MiniCPM5 1B locally?

Yes — MiniCPM5 1B can run locally on consumer hardware. Popular tools include Ollama, LM Studio, and llama.cpp.

How fast is MiniCPM5 1B?

At Q4_K_M, MiniCPM5 1B can reach ~7273 tok/s on AMD Instinct MI350X. On NVIDIA GeForce RTX 4090: ~993 tok/s. Speed depends mainly on GPU memory bandwidth. Real-world results typically within ±20%.

tok/s = (bandwidth GB/s ÷ model GB) × efficiency

Example: NVIDIA B200 → 8000 ÷ 0.66 × 0.65 = ~7879 tok/s

Estimated speed at Q4_K_M (0.7 GB)

~7879 tok/s
~993 tok/s
~7879 tok/s
~7273 tok/s

Real-world results typically within ±20%. Speed depends on batch size, quantization kernel, and software stack.

Learn more about tok/s estimation →

What's the download size of MiniCPM5 1B?

At Q4_K_M, the download is about 0.60 GB. The full-precision BF16 version is 2.00 GB. The smallest option (Q2_K) is 0.42 GB.

Which GPUs can run MiniCPM5 1B?

52 consumer GPUs can run MiniCPM5 1B at Q4_K_M. Top options include AMD Radeon RX 6700 XT, AMD Radeon RX 6800, AMD Radeon RX 6800 XT. 52 GPUs have plenty of headroom for comfortable inference.

Which devices can run MiniCPM5 1B?

163 devices with unified memory can run MiniCPM5 1B at Q4_K_M (0.7 GB), including AMD Ryzen AI 9 HX 370 (Strix Point) Laptop, ASUS Ascent GX10, Beelink GTR9 Pro (Ryzen AI Max+ 395, 128 GB), Framework Desktop (Ryzen AI Max+ 395, 128 GB). Apple Silicon Macs use unified memory shared between CPU and GPU, making them well-suited for local LLM inference.