openbmb · text

MiniCPM-Llama3-V-2_5

openbmb/MiniCPM-Llama3-V-2_5

MiniCPM-Llama3-V-2_5 at Q4_K_M is exactly 4,920,733,792 bytes (4.58 GiB / 4.92 GB) — an effective 4.611 bits per weight, not the nominal 4. Its KV cache at 32K is 4.00 GiB.

From the file· summed from 1 file(s)From the file· KV per layer
Parameters
8.5B
Architecture
—
32 layers
Context
8,192
native (config.json)
License
—

Shipped quantizations

● exact bytes, summed from published files
QuantSize●Exact bytes●Effective bpw●Tensors●Publisher
Q2_K2.96 GiB3,179,130,9762.979—second-state
Q2_K2.96 GiB3,179,643,9362.980—openbmb
IQ3_XS3.28 GiB3,519,259,6803.298—openbmb
Q3_K_S3.41 GiB3,664,498,7843.434—second-state
Q3_K_S3.41 GiB3,665,011,7443.434—openbmb
IQ3_S3.43 GiB3,682,837,5363.451—openbmb
IQ3_M3.53 GiB3,785,335,8403.547—openbmb
Q3_K_M3.74 GiB4,018,917,4723.766—second-state
Q3_K_M3.74 GiB4,019,430,4323.767—openbmb
Q3_K3.74 GiB4,019,430,4323.767—openbmb
Q3_K_L4.03 GiB4,321,955,9364.050—second-state
Q3_K_L4.03 GiB4,322,468,8964.051—openbmb
IQ4_XS4.18 GiB4,484,875,2964.203—openbmb
Q4_04.34 GiB4,661,211,2324.368—second-state
Q4_04.34 GiB4,661,724,1924.368—openbmb
Q4_K_S4.37 GiB4,692,668,5124.397—second-state
Q4_K_S4.37 GiB4,693,181,4724.398—openbmb
IQ4_NL4.38 GiB4,707,861,5364.412—openbmb
Q4_K_M4.58 GiB4,920,733,7924.611—second-state
Q4_K_M4.58 GiB4,921,246,7524.612—openbmb
Q4_K4.58 GiB4,921,246,7524.612—openbmb
Q4_14.78 GiB5,130,765,3444.808—openbmb
Q5_05.21 GiB5,599,293,5365.247—second-state
Q5_K_S5.21 GiB5,599,293,5365.247—second-state
Q5_05.22 GiB5,599,806,4965.247—openbmb
Q5_K_S5.22 GiB5,599,806,4965.247—openbmb
Q5_K_M5.34 GiB5,732,986,9765.372—second-state
Q5_K_M5.34 GiB5,733,499,9365.373—openbmb
Q5_K5.34 GiB5,733,499,9365.373—openbmb
BF165.43 GiB5,834,104,8325.467—openbmb
Q5_15.65 GiB6,068,847,6485.687—openbmb
Q6_K6.14 GiB6,596,005,9846.181—second-state
Q6_K6.14 GiB6,596,518,9446.181—openbmb
Q8_07.95 GiB8,540,770,4008.003—second-state
Q8_07.95 GiB8,541,283,3608.004—openbmb
F1614.97 GiB16,068,890,72015.058—second-state
F1614.97 GiB16,068,890,81615.058—openbmb

KV cache by context

computed per layer
ContextKV cache (f16)●Flat formulaOverstated byFull / windowed / recurrent
4,0960.50 GiB0.50 GiB—32 / 0 / 0
8,1921.00 GiB1.00 GiB—32 / 0 / 0
16,3842.00 GiB2.00 GiB—32 / 0 / 0
32,7684.00 GiB4.00 GiB—32 / 0 / 0
65,5368.00 GiB8.00 GiB—32 / 0 / 0
131,07216.00 GiB16.00 GiB—32 / 0 / 0

Compare with

same modality, comparable size
vs gemma-4-12B-it-qat-q4_0-unquantizedvs gemma-4-E4B-itvs Qwen3-30B-A3B-Thinking-2507vs Qwen3-4Bvs Qwen3-8Bvs Llama-3.2-1B-InstructAll alternatives →Will it fit on my card? →

Will it run on your card?

full quant x context sweep
By VRAM:8GB12GB16GB24GB32GB48GB
Radeon RX 6500 XT 4GBGeForce RTX 3050 6GBGeForce RTX 5050 8GBGeForce RTX 3080 10GBGeForce RTX 2080 Ti 11GBGeForce RTX 5070 12GBGeForce RTX 5060 Ti 16GBApple M3 Pro 18GBGeForce RTX 3080 Ti 20GBGeForce RTX 5090 D V2 24GBGeForce RTX 5090 D 32GBApple M5 Max 36GBApple M5 Pro 48GBApple M5 Max 64GBApple M3 Ultra 96GBApple M5 Max 128GBApple M2 Ultra 192GBApple M3 Ultra 256GBApple M3 Ultra 512GB

Why other calculators give a different number

A parameters × bits ÷ 8 estimate puts Q4_K_M at roughly 4.47 GiB. The real file is 4.58 GiB, because a quantization is a mixture and some tensors are always kept at higher precision.

Architecture

from config.json
Layers
32
Attention heads
32
KV heads
8
Head dim
128
Hidden size
4096
Vocab
128,256
Sliding window
none
SWA period
—
MLA
no
Experts
—
Experts per token
—
use_sliding_window
—

Questions people ask

How much VRAM does MiniCPM-Llama3-V-2_5 need?
Q4_K_M is exactly 4,920,733,792 bytes (4.58 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is MiniCPM-Llama3-V-2_5's KV cache?
4.00 GiB at 32K context with an f16 cache, computed per layer. Quantizing the cache to q8_0 roughly halves it, which is often the difference between a context length fitting and not.
Which quantization of MiniCPM-Llama3-V-2_5 should I use?
Q4_K_M is the usual default. Pick the largest quantization that fits your card at the context you actually need — the table above gives exact sizes for every one published.