How much VRAM does MiniMax-M2.7 need?

Q4_K_M is exactly 138,342,384,096 bytes (128.84 GiB) in weights. Add the KV cache, which depends on context length, plus roughly half a gigabyte of runtime overhead.

How large is MiniMax-M2.7's KV cache?

7.75 GiB at 32K context with an f16 cache, computed per layer from the model's architecture. Quantizing the cache to q8_0 roughly halves it.

Is MiniMax-M2.7 a mixture-of-experts model?

Yes — 256 experts with 8 routed per token. Every expert must be resident in memory, but only the routed ones are read per token, so its memory requirement and its speed behave very differently.

MiniMaxAI · text · mixture of experts

MiniMax-M2.7

MiniMaxAI/MiniMax-M2.7

MiniMax-M2.7 at Q4_K_M is exactly 138,342,384,096 bytes (128.84 GiB / 138.34 GB) — an effective 4.839 bits per weight, not the nominal 4. Its KV cache at 32K is 7.75 GiB.

From the file· summed from 4 file(s)From the file· KV per layer

Parameters

229B

total, not active

Architecture

minimax-m2

62 layers

Context

204,800

native (config.json)

License

other

Shipped quantizations

● exact bytes, summed from published files

Quant	Size●	Exact bytes●	Effective bpw●	Tensors●	Publisher
IQ1_S	43.47 GiB	46,670,399,008	1.633	—	bartowski
IQ1_M2 shards	48.62 GiB	52,200,589,024	1.826	—	bartowski
UD-IQ1_M3 shards	56.53 GiB	60,700,770,496	2.123	—	unsloth
IQ2_XXS2 shards	56.67 GiB	60,845,049,568	2.128	—	bartowski
UD-IQ2_XXS3 shards	60.89 GiB	65,381,613,760	2.287	—	unsloth
IQ2_XS2 shards	63.21 GiB	67,866,314,496	2.374	—	bartowski
IQ2_S2 shards	64.38 GiB	69,131,975,424	2.418	—	bartowski
UD-IQ2_M3 shards	65.32 GiB	70,139,281,600	2.454	—	unsloth
IQ2_M2 shards	71.17 GiB	76,417,481,440	2.673	—	bartowski
Q2_K3 shards	74.55 GiB	80,051,669,856	2.800	—	bartowski
UD-IQ3_XXS3 shards	74.60 GiB	80,103,688,384	2.802	—	unsloth
Q2_K_L3 shards	75.11 GiB	80,651,861,856	2.821	—	bartowski
UD-IQ3_S3 shards	77.87 GiB	83,614,320,800	2.925	—	unsloth
UD-Q3_K_S3 shards	87.21 GiB	93,637,298,368	3.275	—	unsloth
IQ3_XXS3 shards	88.65 GiB	95,183,862,656	3.329	—	bartowski
Q3_K_S3 shards	92.49 GiB	99,314,040,672	3.474	—	bartowski
UD-Q3_K_M4 shards	94.29 GiB	101,243,668,768	3.542	—	unsloth
Q3_K_M3 shards	96.98 GiB	104,127,004,512	3.642	—	bartowski
IQ3_XS3 shards	96.98 GiB	104,127,004,512	3.642	—	bartowski
UD-IQ4_XS4 shards	100.97 GiB	108,413,781,312	3.792	—	unsloth
Q3_K_L3 shards	101.05 GiB	108,501,434,240	3.795	—	bartowski
IQ3_M3 shards	101.33 GiB	108,803,129,184	3.806	—	bartowski
UD-IQ4_NL4 shards	103.15 GiB	110,754,202,912	3.874	—	unsloth
IQ4_XS4 shards	114.00 GiB	122,403,189,760	4.282	—	bartowski
IQ4_NL4 shards	120.57 GiB	129,462,535,136	4.529	—	bartowski
Q4_04 shards	120.93 GiB	129,844,741,088	4.542	—	bartowski
UD-Q4_K_S4 shards	121.97 GiB	130,959,213,888	4.581	—	unsloth
Q4_K_S4 shards	124.65 GiB	133,846,107,104	4.682	—	bartowski
Q4_K_M4 shards	128.84 GiB	138,342,384,096	4.839	—	lmstudio-community
Q4_K_M4 shards	129.27 GiB	138,805,347,296	4.855	—	bartowski
Q4_K_L4 shards	129.70 GiB	139,261,493,216	4.871	—	bartowski
UD-Q4_K_M4 shards	130.54 GiB	140,169,905,504	4.903	—	unsloth
Q4_14 shards	133.65 GiB	143,508,087,776	5.020	—	bartowski
Q5_K_S4 shards	146.87 GiB	157,699,916,768	5.516	—	bartowski
UD-Q5_K_S5 shards	148.12 GiB	159,042,126,272	5.563	—	unsloth
Q5_K_M5 shards	151.50 GiB	162,668,299,360	5.690	—	bartowski
UD-Q5_K_M5 shards	157.23 GiB	168,828,486,080	5.906	—	unsloth
Q6_K5 shards	174.87 GiB	187,763,082,880	6.568	—	lmstudio-community
UD-Q6_K5 shards	175.15 GiB	188,060,778,912	6.578	—	unsloth
Q6_K5 shards	183.52 GiB	197,054,679,168	6.893	—	bartowski

KV cache by context

computed per layer

Context	KV cache (f16)●	Flat formula	Overstated by	Full / windowed / recurrent
4,096	0.97 GiB	0.97 GiB	—	62 / 0 / 0
8,192	1.94 GiB	1.94 GiB	—	62 / 0 / 0
16,384	3.88 GiB	3.88 GiB	—	62 / 0 / 0
32,768	7.75 GiB	7.75 GiB	—	62 / 0 / 0
65,536	15.50 GiB	15.50 GiB	—	62 / 0 / 0
131,072	31.00 GiB	31.00 GiB	—	62 / 0 / 0

Compare with

same modality, comparable size

vs Qwen3-Coder-30B-A3B-Instruct vs Qwen3.6-27B vs Qwen3.8-27B vs DeepSeek-V4-Flash vs Qwen3-30B-A3B-Thinking-2507 vs Laguna-XS-2.1 All alternatives →Will it fit on my card? →

Why other calculators give a different number

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

Architecture

from config.json

Layers

Attention heads

KV heads

Head dim

128

Hidden size

3072

Vocab

200,064

Sliding window

none

SWA period

—

MLA

Experts

256

Experts per token

use_sliding_window

—

Questions people ask

How much VRAM does MiniMax-M2.7 need?: Q4_K_M is exactly 138,342,384,096 bytes (128.84 GiB) in weights. Add the KV cache, which depends on your context length, plus roughly half a gigabyte of runtime overhead.
How large is MiniMax-M2.7's KV cache?: 7.75 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.
Is MiniMax-M2.7 a mixture-of-experts model?: Yes — 256 experts, 8 routed per token. Every expert must be resident, but only the routed ones are read per token, which is why its memory requirement and its speed behave very differently.
Which quantization of MiniMax-M2.7 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.