nvidia · text

Llama-3.1-Minitron-4B-Width-Base

nvidia/Llama-3.1-Minitron-4B-Width-Base

Llama-3.1-Minitron-4B-Width-Base at Q4_K_M is exactly 2,778,282,976 bytes (2.59 GiB / 2.78 GB) — an effective 4.925 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
4.5B
Architecture
llama
32 layers
Context
131,072
native (config.json)
License
other

Shipped quantizations

● exact bytes, summed from published files
QuantSize●Exact bytes●Effective bpw●Tensors●Publisher
Q2_K1.71 GiB1,839,737,4403.261—legraphista
Q2_K1.71 GiB1,839,737,8243.261—bartowski
IQ3_XS1.89 GiB2,027,602,5283.594—legraphista
IQ3_XS1.89 GiB2,027,602,9123.594—bartowski
Q3_K_S1.96 GiB2,101,527,1363.725—legraphista
Q3_K_S1.96 GiB2,101,527,5203.725—bartowski
IQ3_S1.97 GiB2,114,896,4803.749—legraphista
IQ3_M2.03 GiB2,183,414,3683.871—legraphista
IQ3_M2.03 GiB2,183,414,7523.871—bartowski
Q2_K_L2.07 GiB2,224,505,8243.943—bartowski
Q3_K2.14 GiB2,296,562,2724.071—legraphista
Q3_K_M2.14 GiB2,296,562,6564.071—bartowski
Q3_K_L2.30 GiB2,464,858,7204.370—legraphista
Q3_K_L2.30 GiB2,464,859,1044.370—bartowski
IQ4_XS2.36 GiB2,535,545,8244.495—bartowski
IQ4_XS2.38 GiB2,553,240,1604.526—legraphista
Q4_02.47 GiB2,655,599,5844.708—bartowski
Q4_K_S2.48 GiB2,664,249,9524.723—legraphista
Q4_K_S2.48 GiB2,664,250,3364.723—bartowski
IQ4_NL2.49 GiB2,675,260,0004.743—legraphista
Q4_K2.59 GiB2,778,282,5924.925—legraphista
Q4_K_M2.59 GiB2,778,282,9764.925—bartowski
Q4_K_L2.86 GiB3,070,706,6565.444—bartowski
Q5_K_S2.95 GiB3,163,339,3605.608—legraphista
Q5_K_S2.95 GiB3,163,339,7445.608—bartowski
Q5_K3.01 GiB3,230,186,0805.726—legraphista
Q5_K_M3.01 GiB3,230,186,4645.726—bartowski
Q5_K_L3.23 GiB3,473,359,8406.157—bartowski
Q6_K3.46 GiB3,710,333,5366.577—legraphista
Q6_K3.46 GiB3,710,333,9206.577—bartowski
Q6_K_L3.63 GiB3,901,178,8486.916—bartowski
Q8_04.47 GiB4,803,215,9688.515—legraphista
Q8_04.47 GiB4,803,216,3528.515—bartowski
BF168.41 GiB9,033,728,60816.015—legraphista
F168.41 GiB9,033,728,67216.015—bartowski

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-E4B-itvs Qwen3-4Bvs Qwen3-8Bvs HyperCLOVAX-SEED-Text-Instruct-1.5Bvs Llama-3.2-1B-Instructvs Qwen3-VL-8B-Instruct-abliterated-v1All 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 2.36 GiB. The real file is 2.59 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
3072
Vocab
128,256
Sliding window
none
SWA period
—
MLA
no
Experts
—
Experts per token
—
use_sliding_window
—

Questions people ask

How much VRAM does Llama-3.1-Minitron-4B-Width-Base need?
Q4_K_M is exactly 2,778,282,976 bytes (2.59 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is Llama-3.1-Minitron-4B-Width-Base'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 Llama-3.1-Minitron-4B-Width-Base 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.