LLM Hardware Requirements Calculator
Enter your RAM or GPU VRAM and see exactly which local AI models you can run, the single best pick, and how fast it will go.
What LLM can I run? A local model at Q4 quantization needs roughly 0.6 GB of memory per billion parameters. ModelFit budgets about 70% of unified memory for the model on machines up to 32GB, scaling to ~85% at 128GB and above, and about 90% of a discrete GPU's VRAM. That means an 8GB device runs models up to ~9B, a 16GB device comfortably runs up to ~14B, 32GB unlocks ~35B-class models, and 64GB or more runs 70B-class models. Use the calculator below to size your exact hardware against 113 local models.
With 16 GB of unified memory, ModelFit budgets about 11 GB for the model and comfortably runs local LLMs up to ~12B parameters at Q4. The best single pick is Qwen3.5 9B Instruct.
Tokens/sec are ModelFit estimates from chip bandwidth and model size, not measured benchmarks. Ollama commands are registry-verified.
Local LLM memory requirements by RAM tier
Every row is derived from ModelFit's catalog of 113 local models across 26 families. Click a tier for the full list.
| Memory | Model budget (~70-85%) | Max dense model size | Models that fit | Top pick |
|---|---|---|---|---|
| 8 GB | ~5.6 GB | ~9B params | 32 / 113 | Ornith 1.0 9B |
| 16 GB | ~11.2 GB | ~14B params | 53 / 113 | Qwen3.5 9B Instruct (Q8) |
| 24 GB | ~16.8 GB | ~29.3B params | 67 / 113 | Qwen3.8 27B |
| 32 GB | ~22.4 GB | ~35B params | 81 / 113 | Qwen3.6 35B-A3B |
| 48 GB | ~34.8 GB | ~35B params | 92 / 113 | Qwen3.8 27B (Q8) |
| 64 GB | ~48 GB | ~70B params | 97 / 113 | Qwen3.6 35B-A3B (Q8) |
| 96 GB | ~76.8 GB | ~123B params | 104 / 113 | Qwen3.5 122B-A10B Instruct |
| 128 GB | ~108.8 GB | ~123B params | 108 / 113 | Qwen3.5 122B-A10B Instruct |
Q4_K_M assumed. Fit and tok/s are ModelFit estimates from the dataset, not measured benchmarks. Updated 2026-09-29.
What each memory tier adds
Each card leads with the models that tier unlocks over the tier below, then the best models that already fit, all from the same 113-model catalog as the calculator above. Every model name links to its own memory math.
8 GB
32 OF 113 MODELS FIT~5.6 GB usable for weights · everything that fits starts here
- Ornith 1.0 9B9B · Q4_K_M · ~5.6 GB
- Qwen3.5 4B Instruct (Q8)4B · Q8_0 · ~4.3 GB
- LFM2.5 8B-A1B8.3B · Q4_K_M · ~5.5 GB
- Granite 4.1 8B Instruct8B · Q4_K_M · ~5.5 GB
- DeepSeek-R1 Distill Qwen 7B7B · Q4_K_M · ~5.5 GB
16 GB
53 OF 113 MODELS FIT~11.2 GB usable for weights · 5 newly unlocked over 5.6 GB
- Qwen3.5 9B Instruct (Q8)9B · Q8_0 · ~10.7 GB
- Gemma 4 12B12B · Q4_K_M · ~8 GB
- MiMo-V2.6-Distill-Qwen-9B9B · Q4_K_M · ~5.8 GB
- Qwen3 14B14B · Q4_K_M · ~11 GB
- DeepSeek-R1 Distill Qwen 14B14B · Q4_K_M · ~11 GB
24 GB
67 OF 113 MODELS FIT~16.8 GB usable for weights · 5 newly unlocked over 11.2 GB
- Qwen3.8 27B27B · Q4_K_M · ~16.5 GB
- Gemma 4 12B (Q8)12B · Q8_0 · ~12.8 GB
- Qwen3.5 27B Instruct27B · Q4_K_M · ~16 GB
- Gemma 4 26B-A4B26B · Q4_K_M · ~16 GB
- Devstral Small 2 24B24B · Q4_K_M · ~15.2 GB
32 GB
81 OF 113 MODELS FIT~22.4 GB usable for weights · 5 newly unlocked over 16.8 GB
- Qwen3.6 35B-A3B35B · Q4_K_M · ~22 GB
- Qwen3.6 27B27B · Q4_K_M · ~18 GB
- Qwen3.5 35B-A3B Instruct35B · Q4_K_M · ~20 GB
- Gemma 4 31B31B · Q4_K_M · ~20 GB
- Ornith 1.0 35B35B · Q4_K_M · ~21.2 GB
48 GB
92 OF 113 MODELS FIT~34.8 GB usable for weights · 5 newly unlocked over 22.4 GB
- Qwen3.8 27B (Q8)27B · Q8_0 · ~27.1 GB
- Qwen3.6 27B (Q8)27B · Q8_0 · ~30 GB
- Gemma 4 31B (Q8)31B · Q8_0 · ~30.9 GB
- Qwen3.5 27B Instruct (Q8)27B · Q8_0 · ~27.1 GB
- Gemma 4 26B-A4B (Q8)26B · Q8_0 · ~28.1 GB
64 GB
97 OF 113 MODELS FIT~48 GB usable for weights · 5 newly unlocked over 34.8 GB
- Qwen3.6 35B-A3B (Q8)35B · Q8_0 · ~38.7 GB
- Qwen3.5 35B-A3B Instruct (Q8)35B · Q8_0 · ~38.7 GB
- Llama 3.3 70B Instruct70B · Q4_K_M · ~42 GB
- DeepSeek-R1 Distill Llama 70B70B · Q4_K_M · ~42 GB
- Llama 3.1 70B Instruct70B · Q4_K_M · ~42 GB
96 GB
104 OF 113 MODELS FIT~76.8 GB usable for weights · 5 newly unlocked over 48 GB
- Qwen3.5 122B-A10B Instruct122B · Q4_K_M · ~72 GB
- Devstral 2 123B123B · Q4_K_M · ~74.9 GB
- GPT-OSS 120B117B · MXFP4 · ~65.4 GB
- Qwen3-Next 80B-A3B80B · Q4_K_M · ~50.4 GB
- Llama 4 Scout109B · Q4_K_M · ~67 GB
128 GB
108 OF 113 MODELS FIT~108.8 GB usable for weights · 4 newly unlocked over 76.8 GB
- Qwen3-Next 80B-A3B (Q8)80B · Q8_0 · ~84.8 GB
- Laguna S 2.1118B · Q4_K_M · ~96 GB
- Nemotron 3 Super 120B-A12B120B · Q4_K_M · ~86.8 GB
- Ling-3.0-flash124B · Q4_K_M · ~77.8 GB
- Qwen3.5 122B-A10B Instruct122B · Q4_K_M · ~72 GB
Loads are Q4_K_M estimates including weights only; context and KV-cache need headroom on top. Click a tier for the full ranked list, or a model name for its per-hardware fit math.
Frequently asked questions
How much RAM do I need to run a local LLM?
At Q4 quantization a local LLM needs roughly 0.6 GB of memory per billion parameters, and ModelFit budgets ~70% of unified memory for the model up to 32GB, scaling to ~85% at 128GB and above. In practice 8GB runs models up to ~9B, 16GB comfortably runs up to ~14B, 32GB unlocks ~35B-class models, and 64GB or more runs 70B-class models.
What LLM can I run with my GPU VRAM?
VRAM is the hard ceiling for a discrete GPU, and about 90% of it is usable for model weights. 8GB fits up to an 8B model, 12GB reaches 9B, 16GB unlocks 14B-class models, 24GB runs 32B-class models, and 32GB reaches 70B-class MoE models. Switch the calculator to GPU VRAM mode and enter your card memory to see the exact picks.
How does the calculator work?
Enter your memory amount and pick Apple unified memory or GPU VRAM. The calculator runs ModelFit’s recommendation engine in your browser: it sizes each model at ~0.6 GB per billion parameters, applies the memory budget for your hardware, and ranks the models that fit by quality and speed. A shared link carries its configuration in the URL, and that configuration is rendered on the server first, so /calculator/?gb=32 already shows the 32 GB picks before any JavaScript runs. Tokens per second are ModelFit estimates from memory bandwidth and model size, not measured benchmarks.
Can I combine two GPUs to run bigger local models?
Yes. Ollama and llama.cpp split model layers across cards automatically, so two or three GPUs pool their VRAM for fit: about 90% of the combined VRAM is usable for weights. Expect real throughput below a single card with the same total VRAM, because inter-GPU transfers add overhead and mixed cards run at the slower card’s pace. Switch the calculator to Multi-GPU rig mode to pick your exact cards and see which models fit, and use the Copy link button to share the setup.
Is the ModelFit calculator free?
Yes. The calculator is completely free, needs no sign-up, and runs entirely in your browser with no data sent to a server. The underlying compatibility dataset is open under CC BY 4.0, and the same engine ships as the free npx @wecko-ai/modelfit command-line tool.
Go deeper
Per-card picks, plus what long context costs on a discrete GPU.
The memory arithmetic: weights, KV cache, and the usable budget.
Card by card: what each GPU holds, its largest model, its best pick.
Real GGUF sizes from 1B to 80B, and the smallest card that fits each.
Apple unified memory against a discrete GPU, tier by tier.
Pick your exact MacBook, iPhone or GPU for a tuned recommendation.
Every model against every hardware tier, open under CC BY 4.0.
The model-size-to-memory matrix explained, tier by tier.
Citable key facts on RAM, VRAM and model fit.
The same engine runs offline as a one-line command that detects your machine and names the best local model:
npx @wecko-ai/modelfit