How much VRAM does MiMo-V2.6-Pro need?

About 603.8 GB at MXFP4 with 4K of context and batch 1, rising to roughly 605.3 GB at 32K. That figure is weights plus KV cache plus a 10% activation buffer, calculated from the model's architecture rather than measured on a card.

Can MiMo-V2.6-Pro run on a single GPU?

Not comfortably on any single card in this index at MXFP4. It needs about 603.8 GB, which means splitting across GPUs or offloading layers to system RAM.

Which quantization of MiMo-V2.6-Pro should I use?

MXFP4 is the only level in the index for this model, so there is nothing to choose between here. Note this is a mixture-of-experts model — all parameters must be resident even though only a fraction are active per token, so the memory cost follows the total, not the active count.

MiMo-V2.6-Pro

1T-A42B

Xiaomi MiMo

Xiaomi's open-weight flagship, near the top of the open-model rankings this autumn. It has about 1.02 trillion parameters, roughly 42B of them active per token, and ships under the MIT licence. The released weights are already 4-bit (MXFP4 experts), and the GGUF builds repack them rather than quantize again. At that level it needs about 604 GB at 4K context, more than any single machine in this index. The largest Mac Studio gives its GPU about 384 GB, and four 80 GB H100s hold 320 GB. Eight 80 GB cards (640 GB) are about the smallest server that holds it, and even that is tight on this site's rule. It is listed so the calculator can say so. Only 10 of its 70 layers keep a growing cache, so even 1M tokens adds only about 50 GB. llama.cpp runs it as `mimo2`, and vision loads through a separate encoder. Sizes come from a published GGUF file; no per-level quality loss has been published.

⬇ 95.7K HF downloads♥ 698 likesXiaomiMiMo/MiMo-V2.6-Pro-RL· stats from 10/12/2026

Pro GPU

1049K

Max Context

Quant Variants

GGUF MXFP4

Best Quality

100.0%

Accuracy Retained

Calculate VRAM Hugging Face Compare

Quantization Variants

Per-quant VRAM, quality loss, and inference speed on RTX 4090

Measured = run on this site · Estimated = not run here: calculated, or a figure this site has not verified · Community = public reports

Format	Level	BPW	VRAM	PPL Loss	Speed	Source	Actions
GGUF	MXFP4	4.52	603.8 GB	0.0%	—	Estimated	Calc HF

Similar models

Compare with Mistral Large

675B MoE

Mistral Large 3 675B Instruct

Mistral AI

Pro GPU

312.0 GBmin VRAM97.9%accuracy

Mistral 3 flagship MoE (41B active / 675B total) with vision encoder. FP8 on 8×H200; GGUF quant for research clusters only. Its attention is DeepSeek-style MLA, so the real KV cache is smaller than the figure below, which uses an unverified conventional layout. At 32K that is a rounding error beside ~390 GB of weights; at the full 256K window, treat the cache figure as an upper bound.

132B MoE

DBRX Instruct

Databricks

Pro GPU

63.2 GBmin VRAM97.5%accuracy

MoE flagship (~36B active). Needs multi-GPU; strong code and reasoning at scale.

109B MoE

Llama 4 Scout 17B (16E)

Meta Llama 4

Pro GPU

55.0 GBmin VRAM97.6%accuracy

Meta Llama 4 Scout MoE (17B active / 109B total). Multimodal; needs ~68GB VRAM at Q4_K_M.

400B MoE

Llama 4 Maverick 17B (128E)

Meta Llama 4

Pro GPU

198.0 GBmin VRAM97.8%accuracy

Llama 4 Maverick flagship MoE (17B active / 400B total). Multi-GPU or H100 cluster territory.

Running MiMo-V2.6-Pro locally

At MXFP4 and 4K of context, MiMo-V2.6-Pro needs about 603.8 GB — 548.5 GB of weights, 0.42 GB of KV cache and a 54.9 GB activation buffer. MXFP4 is the format MiMo-V2.6-Pro was released in, so it is the reference here rather than a community requantization. No card in this index clears that comfortably, so it is a multi-GPU or CPU-offload proposition. These are calculated figures, not measurements: the estimate stops counting a card as comfortable at 88% of its VRAM, which is roughly the room a desktop session needs.

What longer context costs

Going from 4K to 32K adds about 1.36 GB, taking the total to 605.3 GB. That is gentler than the parameter count suggests: only 10 of 70 layers keep a KV cache that grows with context, and 60 more cap theirs at a sliding window, so the cache scales at a fraction of the usual rate. The model's native window is 1M; holding all of it at MXFP4 would need about 659 GB.

Which build to download

This index only tracks MiMo-V2.6-Pro in GGUF, across 1 level (MXFP4). No throughput has been measured for this model on this site's hardware. GGUF runs on llama.cpp and Ollama across NVIDIA, AMD and Apple silicon; AWQ and GPTQ target vLLM on CUDA and ROCm; EXL2 is ExLlamaV2 — CUDA only, and now archived, so local use rather than serving.

Common questions

How much VRAM does MiMo-V2.6-Pro need?: About 603.8 GB at MXFP4 with 4K of context and batch 1, rising to roughly 605.3 GB at 32K. That figure is weights plus KV cache plus a 10% activation buffer, calculated from the model's architecture rather than measured on a card.
Can MiMo-V2.6-Pro run on a single GPU?: Not comfortably on any single card in this index at MXFP4. It needs about 603.8 GB, which means splitting across GPUs or offloading layers to system RAM.
Which quantization of MiMo-V2.6-Pro should I use?: MXFP4 is the only level in the index for this model, so there is nothing to choose between here. Note this is a mixture-of-experts model — all parameters must be resident even though only a fraction are active per token, so the memory cost follows the total, not the active count.

Where this model fits

Sized at MXFP4 with a 4K context window, smallest card first. Comfortable means the estimate uses at most 88% of the memory.

Just misses: Mac M5 Ultra 512G+219.8GB over Mac M5 Ultra 256G+411.8GB over
Ships in: GGUF
Try it yourself: Size it in the calculator Generate the run command

How to actually run this

Deployment guides for this model and this class of hardware.

This page's figures change when the model or the runtime does.Last updated 2026-10-12 RSS → /feed.xml