Can I run OLMo 2 13B?
OLMo 2 13B by Ai2 needs around 12 GB of RAM at the recommended 4-bit quantization (8.3 GB download). Your hardware is checked below β instantly, nothing leaves your browser. Expect roughly ~37 tok/s on a NVIDIA RTX 3060 12GB.
Reading your hardware signalsβ¦
Real-world notes
OLMo 2 13B is Ai2's fully open chat model, and its appeal is as much about provenance as performance: the weights, training data, and recipe are all public under Apache 2.0, so you can use it commercially without second-guessing the terms. At a 4-bit quant it lands around 8.3 GB, which is a bit much for a 12 GB card once you account for overhead, but it sits fine on a 16 GB GPU or in unified memory on an Apple Silicon Mac. If you are tight, the 2-bit build drops to about 5.7 GB. Plan on roughly 12 GB of RAM as a floor.
In daily use it feels like a solid, even-tempered chat partner. On an RTX 3060 12 GB you can expect around 37 tokens per second at 4-bit, comfortably faster than you read, and a 4090 pushes that to about 103 tok/s. An M-series Max sits near 42 tok/s. The one thing to keep front of mind is the 4K context window, which is small by 2024-2025 standards. Even maxed out the model only needs about 9 GB total, but you simply cannot feed it long documents or sprawling chat histories without truncating, so treat it as a short-turn assistant.
Against its size class, OLMo 2 13B is the open-data pick rather than the raw-capability leader. Models like Qwen 3 14B and Phi-4 14B generally edge it out on reasoning and structured tasks, and both carry far larger context windows if long inputs matter to you. Ministral 3 14B adds vision, which OLMo does not. What OLMo offers that none of them do is genuine end-to-end openness: if you care about knowing exactly what went into your model, or you are doing research and reproducibility work, this is the one to reach for. Apache 2.0 means no usage strings attached.
Specifications
Size by quantization
| Quantization | Bits/weight | Download | Min RAM | Quality |
|---|---|---|---|---|
| Q2_K | 3.35 | 5.7 GB | 12 GB | Noticeable loss |
| Q4_K_MRecommended | 4.85 | 8.3 GB | 12 GB | Recommended |
| Q5_K_M | 5.65 | 9.7 GB | 16 GB | High |
| Q8_0 | 8.5 | 14.6 GB | 24 GB | Near-original |
| F16 | 16 | 27.4 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.0 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 | ~37 tok/s |
| NVIDIA RTX 4090 24GB | 1008 GB/s | ~103 tok/s |
| Apple M-series (base) | 100 GB/s | ~10 tok/s |
| Apple M-series Pro | 270 GB/s | ~28 tok/s |
| Apple M-series Max | 410 GB/s | ~42 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 olmo2:13bSources & downloads