NVIDIA RTX 5080
The NVIDIA RTX 5080 has 16 GB VRAM and 960 GB/s memory bandwidth. It can run 46 of our 99 tracked models natively in VRAM at 8k context.
With 16 GB GDDR7, the NVIDIA RTX 5080 is a consumer-tier GPU that can run 46 models natively. This site's calculator puts Qwen3 14B at 60.3 tok/s at Q4_K_M (11.6 GB, fits natively) and Llama 3.1 8B at 104.9 tok/s at Q4_K_M (6.66 GB), both comfortably inside the 16GB budget with headroom for context. The 16GB ceiling isn't a hard wall at 14B, either: dense models up to 22-31B (Mistral Small 22B, Qwen 3.6 27B, Gemma 3 27B, Gemma 4 31B) and MoE models up to 35B total parameters (Qwen3.5 35B-A3B) still fit natively at more aggressive Q2_K-Q3_K_M quantization, decoding anywhere from 46 to 157 tok/s depending on how many parameters actually activate per token. Above that range, CPU offload becomes the only option.
The NVIDIA RTX 5080 is the second-tier Blackwell GPU, built on the full GB203 die with 16GB GDDR7 on a 256-bit bus at 960 GB/s. Its 10,752 CUDA cores and 336 5th-gen Tensor Cores make it a strong 1440p–4K gaming card. For local LLM inference, 7B–14B dense models fit comfortably at Q4–Q8 with room for context; dense models up to roughly 27B and MoE models up to roughly 35B total parameters still fit natively at more aggressive Q2–Q3 quantization, with CPU offload only needed above that.
NVIDIA RTX 5080: Announced at CES on January 6, 2025 and released January 30, 2025 alongside the flagship RTX 5090, the RTX 5080 uses the full GB203-400-A1 die (84 SMs, 10,752 CUDA cores, 336 5th-gen Tensor Cores) with 16GB of GDDR7 on a 256-bit bus, at $999 MSRP for the Founders Edition (confirmed on NVIDIA's own newsroom announcement). Total board power is 360W. GamersNexus's launch review measured the generational gaming uplift over the RTX 4080 Super at just 7-20% depending on the game, called the value proposition "hard to get excited" about when the FPS gap over the same-price 4080 Super sometimes came to just 10 frames, and flagged the repeated 16GB VRAM ceiling, unchanged for a second straight generation, as a real limitation for creative workloads like Premiere and Blender rendering, not just a gaming nitpick.
This site's calculator puts Qwen3 14B at 60.3 tok/s at Q4_K_M (11.6 GB, fits natively) and Llama 3.1 8B at 104.9 tok/s at Q4_K_M (6.66 GB), both comfortably inside the 16GB budget with headroom for context. The 16GB ceiling isn't a hard wall at 14B, either: dense models up to 22-31B (Mistral Small 22B, Qwen 3.6 27B, Gemma 3 27B, Gemma 4 31B) and MoE models up to 35B total parameters (Qwen3.5 35B-A3B) still fit natively at more aggressive Q2_K-Q3_K_M quantization, decoding anywhere from 46 to 157 tok/s depending on how many parameters actually activate per token. Above that range, CPU offload becomes the only option.
Full CUDA support out of the box, but Blackwell's compute capability 12.0 (sm_120) was genuinely new hardware at launch and needs CUDA 12.8+ and an open-kernel driver from the 570 branch; an older llama.cpp, Ollama, or PyTorch build may not recognize this GPU's architecture at all. NVIDIA's own engineering blog measured that gap closing directly on this card: upgrading LM Studio to its CUDA-12.8 llama.cpp backend produced a real ~27% speedup decoding DeepSeek-R1-Distill-Llama-8B at Q4_K_M, benchmarked on an RTX 5080. The bigger long-run constraint is capacity, not compute: this card and the RTX 5070 Ti share the exact same 16GB ceiling and fit exactly the same models, so it's VRAM, not raw compute and not the price gap between them, that actually decides what runs.
| Vendor | NVIDIA |
| Architecture | Blackwell |
| VRAM | 16 GB |
| Memory type | GDDR7 |
| Memory bandwidth | 960 GB/s |
| Compute backend | CUDA |
| Tier | Consumer |
| Released | 2025 |
| Models (native) | 46 / 99 |
| Models (offload) | 12 / 99 |
The 5080 shares its VRAM ceiling with the card below it, and trails the one above it by a lot
Plotting every desktop Blackwell GPU this site tracks by VRAM and bandwidth together shows exactly where the RTX 5080 sits: pinned to the same 16GB as the cheaper card just below it, and a full tier behind the 5090 above it on both axes:
The RTX 5080 (this page) and RTX 5070 Ti share the exact same 16GB VRAM ceiling; the only real difference on this chart is bandwidth, where the 5080's 960 GB/s beats the 5070 Ti's 896 GB/s by 7.1%. That's a far smaller gap than the one above it: the RTX 5090 has 2x this card's VRAM (32GB vs 16GB) and 86.7% more bandwidth (1,792 vs 960 GB/s), putting the 5080 much closer, on both axes, to the 5070 Ti below it than to the 5090 above it. A third card, the RTX 5060 Ti 16GB, shares this same 16GB ceiling too, but at less than half the bandwidth (448 GB/s), proof that VRAM capacity alone says nothing about how fast a model that fits will actually decode.
960 GB/s is a real generational jump: the 16GB ceiling isn't
The RTX 5080 and its direct predecessor, the RTX 4080, ship the exact same 16GB capacity on the same 256-bit bus; only the memory technology changed:
GDDR6X to GDDR7 is a real jump: 717 GB/s to 960 GB/s, up 33.9%, on the identical 256-bit bus and identical 16GB capacity. Since decode is bandwidth-bound, that shows up almost exactly in this site's calculator at a fixed quant: Qwen3 14B at Q4_K_M (11.6 GB) decodes at 45.0 tok/s on the RTX 4080 and 60.3 tok/s on the RTX 5080 (this page), a 34.0% gain, within a rounding error of the bandwidth increase itself. VRAM capacity is the one number that didn't move: buying the two-generations-newer card gets a faster memory subsystem and Blackwell's new NVFP4 quant format (which the RTX 4080's Ada Lovelace architecture can't run at all), but the same 16GB ceiling reviewers already called disappointing at this card's own launch.
Same 16GB ceiling, same models: a real but modest speed edge
The RTX 5080 and RTX 5070 Ti fit exactly the same models, since both cap out at the same 16GB. The real question is how much faster the 5080 actually decodes for it; this site's calculator answers that directly, on a 14B-class model both cards fit at the same widely-used Q4_K_M quant:
At Q4_K_M, Qwen3 14B decodes at 56.2 tok/s on the RTX 5070 Ti and 60.3 tok/s on the RTX 5080 (this page), a 7.3% gain, tracking the two cards' 7.1% bandwidth difference (896 vs 960 GB/s) almost exactly. That's the whole story: since both cards hit the identical 16GB ceiling, nothing about VRAM capacity changes between them, and the roughly $250 MSRP gap between the two ($999 vs $749 at launch, per NVIDIA's own pricing, not a figure this site's calculator tracks) buys a real but modest ~7% speedup, not access to any model the cheaper card can't already run.
Popular models for this GPU
Models this GPU runs natively in VRAM (46)
- Qwen 3.5 35B-A3B (MoE)35B · MMLU-Pro 85.3Q2_K · ~156.9 t/s
- Ornith 1.5 35B-A3B (MoE)35B · MMLU-Pro N/AQ2_K · ~156.9 t/s
- Nemotron 3 Nano 30B32B · MMLU-Pro 78.3Q2_K · ~147 t/s
- Gemma 4 31B30.7B · MMLU-Pro 85.2Q2_K · ~47.2 t/s
- Qwen3 30B-A3B (MoE)30B · MMLU-Pro 61.5Q2_K · ~135.2 t/s
Show 41 more
- Nemotron 3.5 Lightning 30B-A3B30B · MMLU-Pro 81.6Q2_K · ~161.6 t/s
- Muse Glimmer 30B27.8B · MMLU-Pro N/AQ3_K_M · ~46 t/s
- Gemma 2 27B Instruct27.2B · MMLU-Pro 38.0Q2_K · ~46.4 t/s
- Gemma 3 27B Instruct27B · MMLU-Pro 67.5Q2_K · ~52.7 t/s
- Qwen 3.6 27B27B · MMLU-Pro 86.2Q3_K_M · ~46.1 t/s
- UI-Mate 27B27B · MMLU-Pro ~86.2Q3_K_M · ~46.1 t/s
- Bonsai 27B27B · MMLU-Pro ~81.5Ternary (Q2_0) · ~80.7 t/s
- Bonsai 2 27B27B · MMLU-Pro N/ATernary (Q2_0) · ~96.9 t/s
- Qwen 3.8 27B27B · MMLU-Pro N/AQ3_K_M · ~46.1 t/s
- Gemma 4 26B (MoE)25.2B · MMLU-Pro 82.6NVFP4 · ~93 t/s
- Mistral Small 3.1 24B Instruct24B · MMLU-Pro 66.8NVFP4 · ~46.8 t/s
- Mistral Small 22B22.2B · MMLU-Pro 49.2NVFP4 · ~48.1 t/s
- GPT-OSS 20B21B · MMLU-Pro 67.9NVFP4 · ~100.6 t/s
- Qwen3 14B14.8B · MMLU-Pro 61.0NVFP4 · ~71.4 t/s
- Qwen 2.5 14B Instruct14.7B · MMLU-Pro 63.7NVFP4 · ~69.6 t/s
- Phi-4 14B Instruct14B · MMLU-Pro 70.4NVFP4 · ~74.8 t/s
- Mistral Nemo 12B Instruct12.2B · MMLU-Pro 35.6NVFP4 · ~83.8 t/s
- Gemma 3 12B Instruct12.2B · MMLU-Pro 60.6NVFP4 · ~87.2 t/s
- Gemma 4 12B (Unified)12B · MMLU-Pro 77.2NVFP4 · ~67.7 t/s
- Gemma 2 9B Instruct9.2B · MMLU-Pro 32.0NVFP4 · ~84.1 t/s
- Qwen 3.5 9B9B · MMLU-Pro 82.5NVFP4 · ~130.9 t/s
- Ornith 1.5 9B9B · MMLU-Pro N/ANVFP4 · ~130.9 t/s
- Llama 3.1 8B Instruct8B · MMLU-Pro 48.3NVFP4 · ~123 t/s
- DeepSeek R1 Distill Llama 8B8B · MMLU-Pro 41.0NVFP4 · ~123 t/s
- Qwen3 8B8B · MMLU-Pro 56.7NVFP4 · ~119.8 t/s
- Qwen 2.5 7B Instruct7.6B · MMLU-Pro 56.3NVFP4 · ~146.1 t/s
- Mistral 7B Instruct v0.37.25B · MMLU-Pro 30.0NVFP4 · ~132.8 t/s
- Gemma 3 4B Instruct4B · MMLU-Pro 43.6BF16 · ~73.4 t/s
- Gemma 4 E4B4B · MMLU-Pro 69.4BF16 · ~69.3 t/s
- Phi-3.5 Mini Instruct3.8B · MMLU-Pro 47.4BF16 · ~57.7 t/s
- Phi-4-mini Instruct3.8B · MMLU-Pro 67.3BF16 · ~71.9 t/s
- Llama 3.2 3B Instruct3.2B · MMLU-Pro 24.0BF16 · ~85 t/s
- Qwen 2.5 3B Instruct3.1B · MMLU-Pro 32.4BF16 · ~96 t/s
- Gemma 2 2B Instruct2.6B · MMLU-Pro 17.8BF16 · ~102.8 t/s
- Gemma 4 E2B2B · MMLU-Pro 60.0BF16 · ~141.7 t/s
- SmolLM2 1.7B Instruct1.7B · MMLU-Pro 19.0BF16 · ~124.5 t/s
- Qwen 2.5 1.5B Instruct1.5B · MMLU-Pro 16.8BF16 · ~192.9 t/s
- Llama 3.2 1B Instruct1.24B · MMLU-Pro 12.5BF16 · ~227 t/s
- Gemma 3 1B Instruct1B · MMLU-Pro 14.7BF16 · ~268.1 t/s
- Qwen 2.5 0.5B Instruct0.5B · MMLU-Pro 10.0BF16 · ~566.9 t/s
- SmolLM2 360M Instruct0.36B · MMLU-Pro 8.0BF16 · ~591.2 t/s
Models that fit with CPU offload (12)
These use system RAM for layers that don't fit in VRAM, so expect much slower inference.
- Qwen 2.5 72B Instruct72B · MMLU-Pro 71.1Q2_K · ~1.6 t/s
- Llama 3.3 70B Instruct70B · MMLU-Pro 68.9Q3_K_M · ~1.1 t/s
- DeepSeek R1 Distill Llama 70B70B · MMLU-Pro 70.0Q3_K_M · ~1.1 t/s
- Llama 3.1 70B Instruct70B · MMLU-Pro 66.4Q3_K_M · ~1.1 t/s
- Mixtral 8x7B Instruct v0.146.7B · MMLU-Pro 29.7NVFP4 · ~2.8 t/s
- Command-R 35B35B · MMLU-Pro 33.0NVFP4 · ~1.8 t/s
- Qwen 3.6 35B35B · MMLU-Pro 85.2NVFP4 · ~4.9 t/s
- Yi 1.5 34B Chat34.4B · MMLU-Pro 37.0NVFP4 · ~5.4 t/s
- Qwen3 32B32.8B · MMLU-Pro 65.5NVFP4 · ~7.9 t/s
- Qwen 2.5 32B Instruct32.5B · MMLU-Pro 69.0NVFP4 · ~6.6 t/s
- Qwen 2.5 Coder 32B Instruct32.5B · MMLU-Pro 62.3NVFP4 · ~6.6 t/s
- DeepSeek R1 Distill Qwen 32B32.5B · MMLU-Pro 65.0NVFP4 · ~6.6 t/s
Too large for this GPU (41)
- Mixtral 8x22B Instruct v0.1
- Llama 3.1 405B Instruct
- DeepSeek V3 671B
- DeepSeek R1 671B
- Llama 4 Scout 109B
- Llama 4 Maverick 400B
- Qwen3 235B-A22B (MoE)
- MiniMax M1 456B
- GPT-OSS 120B
- GLM-4.5 355B
- GLM-4.5 Air 106B
- GLM-4.6 355B
- GLM-4.6V 106B
- GLM-4.7 358B
- Qwen 3.5 122B-A10B (MoE)
- MiniMax M2.5 229B
- GLM-5 744B
- MiniMax M2.7 229B
- Nemotron 3 Super 120B
- Kimi K2.6
- GLM-5.1 754B
- DeepSeek V4 Pro 1.6T
- DeepSeek V4 Flash 284B
- Mistral Medium 3.5 128B
- GLM-5.2 753B
- Nemotron 3 Ultra 550B-A55B
- Step 3.5 Flash
- Step 3.7 Flash
- MiMo V2.5 Pro
- Kimi K2.5
- MiniMax M3
- Inkling
- Kimi K3
- DeepSeek V4 Flash 0731 284B
- Qwen3.8 2.4T-A95B
- Qwen3.8-Flash-Next
- DeepSeek V4 Pro 0813 1.6T
- Ornith 1.5 397B (MoE)
- GLM-5.3 753B
- GLM-5.3-Flash 320B
- DeepSeek V4.1 Flash 552B
Frequently asked questions
- How much VRAM does the NVIDIA RTX 5080 have?
- The NVIDIA RTX 5080 has 16 GB of GDDR7 with 960 GB/s memory bandwidth.
- What is the NVIDIA RTX 5080 best for?
- With 16 GB of VRAM, the NVIDIA RTX 5080 handles smaller models (7B–14B) at Q4–Q5 quantization, ideal for entry-level local LLM experimentation and lightweight inference.
- What LLMs can the NVIDIA RTX 5080 run locally?
- The NVIDIA RTX 5080 can run 46 of the 99 open-weight models tracked by CanItRun natively in VRAM at 8k context. Top options include: Qwen 3.8 27B at Q3_K_M, Ornith 1.5 35B-A3B (MoE) at Q2_K, Ornith 1.5 9B at NVFP4.
- Can the NVIDIA RTX 5080 run Gemma 4 31B?
- Yes. The NVIDIA RTX 5080 runs Gemma 4 31B natively in VRAM at Q2_K quantization, achieving approximately 47.2 tokens per second.
- Can the NVIDIA RTX 5080 run Qwen 3.6 27B?
- Yes. The NVIDIA RTX 5080 runs Qwen 3.6 27B natively in VRAM at Q3_K_M quantization, achieving approximately 46.1 tokens per second.
- Can the NVIDIA RTX 5080 run Qwen3 8B?
- Yes. The NVIDIA RTX 5080 runs Qwen3 8B natively in VRAM at NVFP4 quantization, achieving approximately 119.8 tokens per second.