Can I run Llama 3.1 8B?
Llama 3.1 8B by Meta needs around 8 GB of RAM at the recommended 4-bit quantization (4.9 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~63 tok/s on a NVIDIA RTX 3060 12GB.
Reading your hardware signalsβ¦
Real-world notes
Llama 3.1 8B is the model most people actually mean when they say they want to "run a local LLM." At a 4-bit quant it lands around 4.9 GB, which means it fits comfortably on an 8 GB GPU, sits well within unified memory on any Apple Silicon Mac from an M1 onward, and will even run on CPU if you are patient. That combination of small footprint and genuinely useful output is why it became the default starting point for self-hosting.
In day-to-day use it feels fast and coherent for chat, summarisation, and light coding help. On a mid-range modern GPU you can expect well over 40 tokens per second at 4-bit, fast enough that the reply streams faster than you read. The 128K context window is real, but treat it as a ceiling rather than a cruising altitude: filling it pushes KV-cache memory up sharply, so on an 8 GB card you will want to keep working context to a few thousand tokens unless you drop to a smaller quant.
Where it shows its size is reasoning and instruction-following on harder, multi-step prompts β newer 7-8B models like Qwen 3 8B tend to edge it out on math and structured tasks, while Gemma 3 4B is the lighter pick if you are tight on memory. Llama 3.1 8B's advantage is maturity: it has the broadest tooling support, the most quantised builds on Hugging Face and Ollama, and the fewest surprises. If you want one model that just works as a local assistant, this is still the safe default.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 3.4 GB | 6 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 4.9 GB | 8 GB | Recommended |
| Q5_K_M | 5.65 | 5.7 GB | 12 GB | High |
| Q8_0 | 8.5 | 8.5 GB | 16 GB | Near-original |
| F16 | 16 | 16.0 GB | 24 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.5 GB | ~5.4 GB |
| 8K tokens | ~1.0 GB | ~5.9 GB |
| 32K tokens | ~4.2 GB | ~9.1 GB |
| 128K tokens | ~16.8 GB | ~21.7 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 | ~63 tok/s |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~177 tok/s |
| Apple M-series (base) | 100 GB/s | ~18 tok/s |
| Apple M-series Pro | 270 GB/s | ~47 tok/s |
| Apple M-series Max | 410 GB/s | ~72 tok/s |
| CPU only (dual-channel DDR5) | 60 GB/s | ~11 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 llama3.1Sources & downloads