// Choice · Run models on your own machine
What model size can my VRAM / RAM run?
Rule of thumb: weight memory ≈ parameters × bits per parameter ÷ 8, plus context (KV cache) and runtime overhead. At 4-bit quantisation that is roughly 0.5–0.7 GB per billion parameters.
verified 2026-10-102 official sources
Scenario: Run models on your own machine →
🖥️Self-hosted computeVRAM calculator and tier guide (moved to Self-hosted compute)→Symptoms
- The model fails to load, runs extremely slowly, or the system starts swapping
Common causes
- Weights plus context exceed available VRAM (unified memory on Apple silicon)
- The context is set too long; KV cache grows with length
How to fix
- Estimate at 4-bit: 7–8B ≈ 5 GB, 14B ≈ 9 GB, 32B ≈ 20 GB, 70B ≈ 40 GB or more (orders of magnitude only; depends on model and quantisation)
- Leave headroom for context and the OS: 8 GB VRAM suits 7–8B, 16 GB can try 14B, 24 GB can try a 4-bit 32B
- On a Mac you can use most, but not all, unified memory; MLX (mlx-lm) and llama.cpp both support Apple silicon
- Set context length to what you need instead of the model’s maximum
- See parameter counts and licences of open-weight models in our Free models section
Notes
- These are rules of thumb, not our own measurements
Official references
Compiled from official documentation and public discussions on 2026-10-10; not yet reproduced in our own environment. Follow the official docs if they differ.