Can I run Ministral 3 3B?
Ministral 3 3B by Mistral AI needs around 4 GB of RAM at the recommended 4-bit quantization (1.8 GB download). Your hardware is checked below — instantly, nothing leaves your browser. Expect roughly ~168 tok/s on a NVIDIA RTX 3060 12GB.
Reading your hardware signals…
Real-world notes
Ministral 3 3B is Mistral's answer to the question "what's the smallest model that still feels like a real assistant?" At 3B parameters it's built for chat and light vision work on hardware you already own. A 4-bit quant lands at about 1.8 GB, and you can squeeze the q2 build down to 1.3 GB if you're truly cramped. With a 4 GB minimum RAM footprint it runs on an entry-level laptop, an old 4 GB GPU, or any Apple Silicon Mac without you thinking twice about memory. This is the model you reach for when a bigger one won't fit.
In daily use the speed is the headline. On an RTX 3060 you'll see roughly 168 tokens per second, an M-series Max pushes around 192, and a 4090 hits about 471 - all far faster than you can read, so replies feel instant. CPU-only on DDR5 still manages about 28 tok/s, usable for batch work. The context window is a generous 256K, but treat that as a ceiling. Filling it gets expensive fast: at 128K of context the total memory load climbs to around 12.6 GB, well past the model's own footprint, so keep working context modest on small machines.
Honestly, at 3B you're trading some depth for that speed and tiny footprint. Mistral 7B generally holds up better on harder reasoning and longer instruction chains, and Mistral Nemo 12B pulls further ahead again if you have the memory to spare. Where Ministral 3 3B wins is the combination of raw throughput and the fact that it also handles vision, which the larger chat-only Mistrals don't. It ships under Apache 2.0, so you can use it commercially with no strings attached. For a fast, free, do-everything small model, it earns its place.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 1.3 GB | 4 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 1.8 GB | 4 GB | Recommended |
| Q5_K_M | 5.65 | 2.1 GB | 6 GB | High |
| Q8_0 | 8.5 | 3.2 GB | 6 GB | Near-original |
| F16 | 16 | 6.0 GB | 12 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.3 GB | ~2.1 GB |
| 8K tokens | ~0.7 GB | ~2.5 GB |
| 32K tokens | ~2.7 GB | ~4.5 GB |
| 128K tokens | ~10.8 GB | ~12.6 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 | ~168 tok/s |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~471 tok/s |
| Apple M-series (base) | 100 GB/s | ~47 tok/s |
| Apple M-series Pro | 270 GB/s | ~126 tok/s |
| Apple M-series Max | 410 GB/s | ~192 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~28 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:3b