Which GPU for Which LLM — VRAM Requirements by Model (2026)
A 32B model at Q4_K_M needs about 20 GB resident, which is why 24 GB is the floor for that class; 12 GB tops out at 14B and 70B wants 48 GB. The table below gives that mapping for Qwen3, Llama 4, DeepSeek V3.2, Gemma 4, Phi-4, with the VRAM floor, the throughput each tier is published at, and a link to the current price of a card that clears it. Per-card medians behind those figures come from the published runs aggregated on SpecPicks' benchmark pages.
As an Amazon Associate, SpecPicks earns from qualifying purchases. See our review methodology.
How to read the VRAM floor
Every floor in this guide comes from the same arithmetic rather than from a vendor chart: Q4_K_M weights run roughly 0.55 GB per billion parameters, and the runtime plus a usable context window wants about 2 GB on top. A 14B model is therefore ~9.7 GB resident, a 32B ~19.6 GB, and a 70B ~40 GB before context. Round up to the nearest card capacity and that is the floor.
The figure that stops being predictable is what happens below the floor. Once weights spill past VRAM the number is set by PCIe and system-memory bandwidth, not by the GPU, and the drop is steep rather than gradual — which is why a tier is quoted as a floor and not as a suggestion. Per-card medians over published runs, with the run counts and sources behind them, live on the benchmark pages; the GPU picker ranks the cards that clear a floor and fit your budget by median measured tok/s.
Qwen3 — VRAM floors and GPU picks
| Tier | VRAM floor | Published throughput | Card to buy at this tier |
|---|---|---|---|
| Qwen3 🧪 Minimum (8B/14B at Q4) | 12 GB32 GB DDR5 | 40–80 tok/s on 14B Q4 |
ZOTAC Gaming GeForce RTX 4060 Ti 16GB AMP DLSS 3 16GB…
Price moves too often to quote here — check the current one.
View Current Price →
|
| Qwen3 🏆 Recommended (32B at Q4) | 24 GB64 GB DDR5 | ~25 tok/s on 32B Q4 (RTX 4090) · ~38 tok/s (RTX 5090 with 32B at higher quant) |
MSI Gaming GeForce RTX 4090 24GB GDRR6X 384-Bit HDMI/DP…
Price moves too often to quote here — check the current one.
View Current Price →
|
| Qwen3 ⚡ Luxury (235B-A22B MoE at Q4, expert offload) | 48 GB128–192 GB DDR5 | Bound by system-RAM bandwidth for the offloaded experts — no cited single-rig figure yet | No tracked listing clears 48 GB in the catalogue today. Rank every card that does → |
Perfect for chatbot + coding use cases on smaller variants. 16GB lets you run 14B at Q4 with comfortable context.
Llama 4 — VRAM floors and GPU picks
| Tier | VRAM floor | Published throughput | Card to buy at this tier |
|---|---|---|---|
| Llama 4 🧪 Minimum (Scout at Q4, GPU + expert offload) | 24 GB64–96 GB DDR5 | Roughly 10–20 tok/s with llama.cpp expert offload — scales with system-RAM bandwidth |
MSI Gaming GeForce RTX 3090 24GB GDRR6X 384-Bit HDMI/DP…
Price moves too often to quote here — check the current one.
View Current Price →
|
| Llama 4 🏆 Recommended (Scout at Q4, GPU + lighter expert offload) | 32 GB64–128 GB DDR5 | Faster than a 24 GB card because fewer experts sit in system RAM; still bounded by RAM bandwidth |
ASUS ROG Astral GeForce RTX 5090 32GB GDDR7 White OC…
Price moves too often to quote here — check the current one.
View Current Price →
|
| Llama 4 ⚡ Luxury (Maverick 400B at Q4) | 96 GB256 GB+ DDR5, or 256–512 GB unified memory | Needs ~220–245 GB for Q4 weights before any context | No tracked listing clears 96 GB in the catalogue today. Rank every card that does → |
Scout's ~60 GB of Q4 weights do not fit a 24 GB card, but only 17B parameters are active per token, so keeping attention and shared layers on the GPU and the routed experts in system RAM stays usable for chat. A ~2-bit quant (~40 GB) cuts the RAM need at a quality cost.
DeepSeek V3.2 — VRAM floors and GPU picks
| Tier | VRAM floor | Published throughput | Card to buy at this tier |
|---|---|---|---|
| DeepSeek V3.2 🧪 Minimum (671B at ~2-bit, GPU + expert offload) | 24 GB256 GB system RAM | Low single-digit tok/s — bound by system-RAM bandwidth, not the GPU |
MSI Gaming GeForce RTX 3090 24GB GDRR6X 384-Bit HDMI/DP…
Price moves too often to quote here — check the current one.
View Current Price →
|
| DeepSeek V3.2 🏆 Recommended (671B at Q4, GPU + server-class RAM) | 24 GB512 GB DDR5 on an 8–12-channel server or workstation platform | Roughly 10–14 tok/s reported with ktransformers on a dual-socket Xeon plus one 24 GB card |
MSI Gaming GeForce RTX 4090 24GB GDRR6X 384-Bit HDMI/DP…
Price moves too often to quote here — check the current one.
View Current Price →
|
| DeepSeek V3.2 ⚡ Luxury (671B at Q4, fully in fast memory) | 96 GB512 GB unified memory, or 4–8 × 96 GB GPUs | ~20 tok/s at 4-bit on a Mac Studio M3 Ultra 512 GB (MLX) | No tracked listing clears 96 GB in the catalogue today. Rank every card that does → |
A ~2-bit dynamic quant shrinks the weights to roughly 170–230 GB. The 24 GB card holds attention and the shared expert; the routed experts live in system RAM (llama.cpp tensor overrides or ktransformers). Workable for batch jobs, slow for chat, and ~2-bit loses noticeably more quality than Q4.
Gemma 4 — VRAM floors and GPU picks
| Tier | VRAM floor | Published throughput | Card to buy at this tier |
|---|---|---|---|
| Gemma 4 🧪 Minimum (2B / 7B at Q4) | 8 GB16 GB DDR5 | ~140 tok/s on 2B Q4 · ~75 tok/s on 7B Q4 (RTX 4060) |
ASUS Dual GeForce RTX 4060 OC Edition 8GB GDDR6 (PCIe…
Price moves too often to quote here — check the current one.
View Current Price →
|
| Gemma 4 🏆 Recommended (9B at Q4 or Q8) | 16 GB32 GB DDR5 | ~85 tok/s on 9B Q4 (RTX 4070 Ti Super 16 GB) |
ASUS TUF Gaming GeForce RTX 4070 Ti Super 16GB GDDR6X OC…
Price moves too often to quote here — check the current one.
View Current Price →
|
| Gemma 4 ⚡ Luxury (27B at Q4, Q8 on 32 GB) | 24 GB64 GB DDR5 | ~35 tok/s on 27B Q4 (RTX 4090) · ~42 tok/s on 27B Q8 (RTX 5090) |
MSI Gaming GeForce RTX 4090 24GB GDRR6X 384-Bit HDMI/DP…
Price moves too often to quote here — check the current one.
View Current Price →
|
Gemma 4 2B at Q4 fits even on integrated graphics. 7B Q4 needs 8 GB; 12 GB lets you keep full 128K context active.
Phi-4 — VRAM floors and GPU picks
| Tier | VRAM floor | Published throughput | Card to buy at this tier |
|---|---|---|---|
| Phi-4 🧪 Minimum (mini at Q4) | 6 GB16 GB DDR5 | ~180 tok/s on Phi-4 mini Q4 (RTX 4060) · ~90 tok/s on RTX 3060 12 GB |
ASUS Dual GeForce RTX 4060 OC Edition 8GB GDDR6 (PCIe…
Price moves too often to quote here — check the current one.
View Current Price →
|
| Phi-4 🏆 Recommended (14B at Q4 or Q8) | 16 GB32 GB DDR5 | ~95 tok/s on 14B Q4 (RTX 4070 Ti Super 16 GB) · ~62 tok/s on 14B Q8 (RTX 4090) |
ASUS TUF Gaming GeForce RTX 4070 Ti Super 16GB GDDR6X OC…
Price moves too often to quote here — check the current one.
View Current Price →
|
| Phi-4 ⚡ Luxury (14B FP16 with 16K context) | 24 GB32 GB DDR5 | ~55 tok/s on 14B FP16 (RTX 4090) · ~78 tok/s (RTX 5090) |
MSI Gaming GeForce RTX 4090 24GB GDRR6X 384-Bit HDMI/DP…
Price moves too often to quote here — check the current one.
View Current Price →
|
Phi-4 mini fits on almost any modern card. Quality is solid for a 4B model — beats Llama 3.2 3B on most benchmarks.
Frequently asked questions
How much VRAM do you need to run a 70B model locally?
About 48 GB resident at Q4_K_M. Q4 weights run roughly 0.55 GB per billion parameters, so 70B is ~39 GB of weights, and the runtime plus a usable context window wants about 2 GB on top — with headroom for longer context that lands at 48 GB. In practice that is two 24 GB cards pooled or one 48 GB workstation card. A single 24 GB card has to offload to system RAM, at which point PCIe bandwidth sets the speed rather than the GPU.
Can you run a 70B model on 12 GB of VRAM?
Not resident. 12 GB comfortably holds the 14B class at Q4 with room for context, and that is the ceiling for a card that size. A 70B model on 12 GB means offloading the majority of the weights to system RAM, which drops throughput by roughly an order of magnitude and turns the figure into a memory-bandwidth measurement rather than a GPU one. If 70B is the requirement, the card is the wrong axis to economise on.
How do you work out the VRAM a model needs?
Multiply the parameter count in billions by about 0.55 GB for Q4_K_M weights, then add roughly 2 GB for the runtime and a usable context window. A 32B model is therefore about 17.6 GB of weights and ~20 GB resident, which is why 24 GB is the practical floor for that class. Longer context costs more: KV-cache grows with context length and with batch size, so a 128K-context session on the same model wants materially more than the same model at 8K.
Is a lower quantisation worth it to fit a bigger model?
Usually down to Q4, rarely below. Published comparisons put Q4_K_M within about 1–2% of FP16 on benchmark averages, which is below what most workloads notice. Q3 starts to show — a 4–6% drop and visible failures on edge cases. Dropping a quantisation level to squeeze a larger parameter count onto the same card is generally a better trade than offloading; dropping two to do it usually is not.
Is unified memory an alternative to a discrete GPU for local LLMs?
For capacity, yes; for throughput, no. A Mac Studio with 192 GB of unified memory or an AMD Ryzen AI Max system loads model sizes no consumer NVIDIA card can hold, silently and at low power. Per-token speed is lower than a discrete card of equivalent tier because memory bandwidth, not capacity, sets throughput once the weights fit. The trade is capacity and quiet against tokens per second — see the per-model tiers below for where each lands.
Where to go next
- Will it run? The model × GPU matrix — one page per exact pair, with cited speeds and a free CSV.
- Rank GPUs by VRAM floor, budget and workload — the same mapping, indexed by what you can spend.
- The local-LLM model-fit table — every card SpecPicks holds runs for, bucketed by what it loads at Q4.
- Best GPUs for local LLMs — the ranked buying guide, per VRAM bracket.
- Benchmark data by card — medians, run counts and source links per SKU.