Can I run Llama 4 Scout?
Llama 4 Scout by Meta needs around 96 GB of RAM at the recommended 4-bit quantization (66.1 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~34 tok/s on a Apple M-series Max.
Reading your hardware signalsβ¦
Real-world notes
Llama 4 Scout is Meta's mixture-of-experts model, and the key thing to understand is the gap between its two sizes. It has 109B total parameters but only routes 17B of them per token, so it generates at the speed of a 17B model while still demanding the memory of the full 109B. At a 4-bit quant that is about 66 GB on disk, and you need at least 96 GB of RAM or unified memory to load it. This is not a 24 GB consumer GPU model: both an RTX 3060 and an RTX 4090 simply do not fit it. Realistically this is a workstation or a maxed-out Apple Silicon machine.
On an Apple M Max with enough unified memory it runs around 34 tokens per second at 4-bit, which is comfortably faster than you read and fine for interactive chat and its vision tasks. On CPU with DDR5 you drop to roughly 5 tokens per second, usable for batch work but painful for back-and-forth. The advertised context is enormous, but be careful: pushing toward 128K tokens drives total memory to about 120 GB, so the long context is a hardware-budget decision, not a free setting. Keep working context modest unless you have headroom to spare.
Against GPT-OSS 120B, the other large model in this class, Scout is the multimodal pick since it handles vision, while GPT-OSS generally has the edge on pure reasoning. Compared to small siblings like Llama 3.2 3B, Scout is a completely different commitment: those run on a phone-class footprint, this needs a server. Its standout trait is being a genuinely fast, image-capable model at this scale. One caveat: it ships under the Llama Community license, which is open-weight rather than open-source, so check the terms before building anything commercial on it.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 45.6 GB | 64 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 66.1 GB | 96 GB | Recommended |
| Q5_K_M | 5.65 | 77.0 GB | 128 GB | High |
| Q8_0 | 8.5 | 115.8 GB | 192 GB | Near-original |
| F16 | 16 | 218.0 GB | 256 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 | ~1.7 GB | ~67.8 GB |
| 8K tokens | ~3.4 GB | ~69.5 GB |
| 32K tokens | ~13.6 GB | ~79.7 GB |
| 128K tokens | ~54.3 GB | ~120.4 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 | Won't fit in VRAM |
| NVIDIA RTX 4090 24GB | 1008 GB/s | Won't fit in VRAM |
| Apple M-series (base) | 100 GB/s | ~8 tok/s |
| Apple M-series Pro | 270 GB/s | ~22 tok/s |
| Apple M-series Max | 410 GB/s | ~34 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~5 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 llama4:scoutSources & downloads