Can I run Ministral 3 14B?
Ministral 3 14B by Mistral AI needs around 16 GB of RAM at the recommended 4-bit quantization (8.5 GB download). Your hardware is checked below — instantly, nothing leaves your browser. Expect roughly ~36 tok/s on a NVIDIA RTX 3060 12GB.
Reading your hardware signals…
Real-world notes
Ministral 3 14B is Mistral's December 2025 mid-size model, a 14B-parameter dense network that also handles vision, so it's the pick when you want one local model that chats and reads images without juggling two checkpoints. At a 4-bit quant it lands around 8.5 GB, just past what an 8 GB card holds comfortably but right at home on a 12 GB RTX 3060 or any Apple Silicon Mac with 16 GB of unified memory or more. Drop to a 2-bit build and it shrinks to about 5.9 GB if you're squeezed; the q8 build is closer to 15 GB.
In daily use it feels quick for its size. On an RTX 3060 12 GB you'll see around 36 tokens per second at 4-bit, comfortably faster than reading speed, and an RTX 4090 pushes that to roughly 101 tok/s. An M-series Max sits near 41 tok/s. The 256K context window is the headline number, but treat it as a ceiling, not a default: even at 128K, total memory climbs to about 30 GB once the KV cache fills, well beyond a single 12 GB or 16 GB device. Keep working context to a few thousand tokens unless you have a 24 GB-plus card to spare.
Against its neighbours, Ministral 3 14B generally has the edge over older siblings like Mistral 7B and Mistral Nemo 12B on harder, multi-step prompts simply by being larger and newer, while OLMo 2 13B is the fully-open-data alternative if reproducibility matters more to you than raw capability. Its real standout is the built-in vision capability at this size with a genuinely usable speed profile. And the license is the easy part: Apache 2.0, so you can use it commercially and in production with no provider-specific strings attached.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 5.9 GB | 12 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 8.5 GB | 16 GB | Recommended |
| Q5_K_M | 5.65 | 9.9 GB | 16 GB | High |
| Q8_0 | 8.5 | 14.9 GB | 24 GB | Near-original |
| F16 | 16 | 28.0 GB | 48 GB | Original |
Sizes are estimates from parameter count × bits per weight; real GGUF builds vary slightly. · Data updated: 2026-06-11 · How we calculate these numbers →
Memory needed by context length
| Context | KV cache (est.) | Total memory (Q4) |
|---|---|---|
| 4K tokens | ~0.7 GB | ~9.2 GB |
| 8K tokens | ~1.3 GB | ~9.8 GB |
| 32K tokens | ~5.4 GB | ~13.9 GB |
| 128K tokens | ~21.6 GB | ~30.1 GB |
The KV cache grows with context length — a model that fits at 4K can run out of memory at 32K. Estimates assume an FP16 cache with grouped-query attention; actual usage varies by runtime.
Estimated speed by hardware
| Hardware | Bandwidth | ~Speed |
|---|---|---|
| NVIDIA RTX 3060 12GB | 360 GB/s | ~36 tok/s |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~101 tok/s |
| Apple M-series (base) | 100 GB/s | ~10 tok/s |
| Apple M-series Pro | 270 GB/s | ~27 tok/s |
| Apple M-series Max | 410 GB/s | ~41 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~6 tok/s |
Token generation is memory-bandwidth bound: tok/s ≈ bandwidth × 0.85 ÷ model size at Q4. Real-world numbers vary by runtime and context length.
Run it locally
The easiest path is Ollama — one command and you're chatting:
ollama run ministral-3:14b