MiMo-V2.6-Flash
MoE workstationThe half-terabyte flagship’s little sibling, weights included. MiMo-V2.6-Flash is the efficiency checkpoint of the MiMo-V2.6 family: 309B total parameters with 15B active per token, sparse MoE, the full omni modality stack of the Pro model (text, image, video, audio - a 681M vision encoder plus audio tokenizer), 1M-token context, and a 5-layer multi-token-prediction speculative decoder. Weights are MIT on HuggingFace, shipping as a 177.7 GB FP8 checkpoint across 67 files, 39,625 downloads in the first week.
What runs where. The memory rule is total parameters resident, so 309B at 2-bit quantization is roughly 77 GB - the straddle class: too big for the 8 GB edge boxes, comfortable in a 96 GB workstation, at home in any 128 GB+ unified-memory or dual-GPU rig, where community GGUF builds (ggml-org’s build already at 10,840 downloads) land it. At FP8 as shipped, 177.7 GB means two datacenter-class GPUs or a node. Nothing here says “premier” about the hardware: this is the biggest open model that a rich single machine can hold at high compression.
Benchmarks, labeled. Vendor-run from the launch README: DeepSWE v1.1 67.9 (the Pro sibling 71.9, GPT-5.6 Sol 73.0, Claude Opus 5 74.0), Toolathlon-Verified 73.6, AutomationBench v1.0.6 52.3 - all within a few points of models four times its active size on the same rows, and all self-reported until third parties run them. The RL story matches the family: Flash trained under the same livestreamed reinforcement-learning program whose receipts Xiaomi published ($850K Flash / $2.62M Pro, under six days).
Where it sits. The family page’s own words: the 9B distill is the only member that approaches home hardware, and the Pro flagship is a two-node cluster model. Flash is the missing middle - frontier-adjacent quality, omni modalities, a published training bill, MIT weights, and a footprint that one serious desk can actually host. For buyers of the 96-128 GB class, this is the first MiMo worth putting on the shortlist.
- 309.0B
- 1024k
- mit
- 🇨🇳 China
- Sep 2026
Scores
Related models
Save your hardware and every model page answers the real question: will it run on your machine, and how fast?
Join free - save your rig →Run it locally
Per-quant memory needs and a static "can you run it?" reference - no rig entry required
The reference hardware
22 reference configs, drawn in-house. Scroll for more.
Can you run it? - reference rigs
| Rig | Q2_K | FP8 |
|---|---|---|
| NVIDIA Jetson Orin NX 16GB | no -> cloud | no -> cloud |
| Jetson AGX Orin 64GB | no -> cloud | no -> cloud |
| Single GTX 1080 Ti (11GB) | no -> cloud | no -> cloud |
| Single RTX 4090 (24GB) | no -> cloud | no -> cloud |
| Single RTX 5090 (32GB) | no -> cloud | no -> cloud |
| 2x RTX 3090 (48GB) | offload | no -> cloud |
| 2x RTX 5090 (64GB) | offload | no -> cloud |
| 4x H100 80GB (320GB) | fast 1963.3t/s | fast 852.8t/s |
| NVIDIA DGX Station 748GB | fast 1172.1t/s | fast 509.1t/s |
| 8x RTX 3090 rack (192GB) | fast 1097.3t/s | tight |
| 4x RTX 5090 (128GB) | fast 1050.2t/s | offload |
| AMD Instinct MI300X (192GB) | fast 780.2t/s | tight |
| 4x RTX 4090 (96GB) | fast 590.8t/s | no -> cloud |
| RTX PRO 6000 Blackwell (96GB) | fast 262.6t/s | no -> cloud |
| Mac Studio M4 Ultra 192GB | fast 174.5t/s | tight |
| Mac Studio M4 Ultra 512GB | fast 174.5t/s | fast 75.8t/s |
| MacBook Pro M5 Max 128GB | fast 98.1t/s | no -> cloud |
| Dual EPYC 9004 + 768GB DDR5-4800 | fast 67.5t/s | fast 29.3t/s |
| DGX Spark 128GB unified | fast 40.0t/s | no -> cloud |
| Ryzen AI Max+ 395 128GB | fast 37.5t/s | no -> cloud |
| Epyc + 512GB DDR4-3200 + 2x RTX 3090 | fast 30.0t/s | ok 13.0t/s |
| Epyc + 512GB DDR4-2400 + 2x RTX 3090 | fast 22.5t/s | ok 9.8t/s |
Fit tiers use the same will-it-run logic as the rig finder. For comfortable fits, the badge reflects decode speed: fast >=20 t/s, ok 8-20 t/s, slow <8 t/s. t/s is a bandwidth estimate, not a measured benchmark.
Download options
Or run it in the cloud
No per-token API provider pricing tracked for MiMo-V2.6-Flash yet. For flagship list prices, see the calculator.
Inference cost over time
Data accumulates from the first daily sync - longer ranges populate over time. Prices come from OpenRouter snapshots, not a historical API.