RTX PRO 5000 Blackwell
An RTX PRO 5000 Blackwell runs 28 of the 34 open models tracked here at Q4_K_M with 8k context, computed on 16 October 2026. The largest is Qwen3.6 35B-A3B (MoE), needing 22.4 GB and generating at most 541 tokens per second.
- Memory
- 48 GB VRAM
- Bandwidth
- 1,344 GB/s
- Board power
- 300 W
- Released
- 2025
- Availability
- Workstation card
Open the RTX PRO 5000 Blackwell in the LLM checker
What an RTX PRO 5000 Blackwell runs, model by model
RTX PRO 5000 Blackwell (48 GB) addresses 48 GB at 1,344 GB/s. Every model below is at Q4_K_M with 8k of context, the setting most people actually use. Once the 5% safety margin comes off, the card has 45.6 GB to spend: memory decides what loads, bandwidth how fast it answers. Both are estimates from stated formulas, and the VRAM calculator shows the working.
On this card a model fits at or under 45.6 GB, and above 40.8 GB it is tight: it loads, but there is little left for the conversation, and a desktop on the same 48 GB can push it over. Tokens per second are single-stream estimates from memory bandwidth; ≤ marks a ceiling real runtimes fall well below.
Computed 16 October 2026The model to actually run on it
Muse Glimmer 30B is the best use of this card: 18.7 GB of the 48 GB available, an estimated 54 tokens per second, comfortable for chat, and 131,072 tokens of context still available.
How this is chosen, since no benchmark is quoted: models are compared by size, a mixture-of-experts model counting at the geometric mean of its total and active parameters (a rule of thumb, not a measurement). The pick is the biggest class that fits with memory to spare and answers at 25 tokens per second or better, and within that class the most recent general-purpose release; coding and reasoning specialists are listed above but not recommended by default.
Qwen3.6 35B-A3B (MoE) is the largest model the card will hold, at 22.4 GB, with room for 131,072 tokens of context. It is a mixture-of-experts model reading only 3B parameters per token, so it is the faster of the two at an estimated 541 tokens per second; what it gives up is the depth of a dense model that reads all of its weights for every token.
It also fits at Q8_0, in about 33.5 GB, which is worth taking whenever the memory allows: Q8 is near-lossless where Q4 costs a little accuracy.
How much context actually fits
Model size is the question people ask; context is the one that bites. The KV cache grows linearly with the conversation, so a model that loads comfortably can still run out of memory halfway through a long document. On 48 GB, the context you get is whatever the weights leave behind, which is why two cards that run the same model can feel completely different in use. These are the largest contexts this card holds, at Q4_K_M weights.
| Model | Max context, FP16 KV | With Q8 KV cache |
|---|---|---|
| Muse Glimmer 30B | 131,072 tokens | 131,072 tokens |
| Qwen3 32B | 40,960 tokens · model limit | 40,960 tokens · model limit |
| Gemma 4 31B | 131,072 tokens | 131,072 tokens |
| Granite 4.2 30B | 104,448 tokens | 131,072 tokens |
Quantising the KV cache to Q8 roughly doubles what you can hold, at a quality cost most people never notice: Granite 4.2 30B on this card goes from 104,448 to 131,072 tokens. Capped at 128k tokens, or at the model's own native window where that is smaller, marked "model limit": free memory beyond that point buys nothing. Rows that hold far more context than their size suggests are hybrid, sliding-window or latent-attention models, which cache only a fraction of what a standard transformer does; each model page shows the working.
Where this card stops
The first model out of reach is Llama 3.3 70B: about 45.8 GB at Q4_K_M and 8k context, against 48 GB of usable memory. That is close enough to be worth a caveat: it is inside the raw 48 GB and only misses the 95% line this site uses for a fit. On a card with a display attached, treat it as no. On a headless card, with a shorter context, it runs. Dropping to Q3_K_M would need about 37.7 GB, which fits, though Q3 loses enough quality that a smaller model at Q4 is usually the better trade. Offloading the remainder to system RAM works and is ten to fifty times slower; it is a way to see a model run, not a way to use one.
Buy or rent
Worth it when you need 48 GB or more, every day, in a quiet two-slot card. For models that fit in 32 GB a 5090 is faster, and for the occasional large run, renting a 48 GB or larger card for the hours you need it costs far less than owning one.
Workstation cards are sold on quotes rather than shelf prices, so there is no single number to publish. Put the figure you are actually looking at, with your electricity rate and your real monthly hours, into the build vs rent calculator, which already knows this card draws 300 W under load. It returns the month owning becomes cheaper, or tells you it never does. Hours per month decides it far more often than the price does.
The honest take
Forty-eight gigabytes at 1,344 GB/s in a two-slot, 300 W card, with a 72 GB version at the same speed.
It holds what any 48 GB card holds and reads it 40% faster than the RTX 6000 Ada (1,344 GB/s against 960 GB/s), which makes it the quickest 48 GB card on this site. It is still three quarters of a 5090's bandwidth, so on any model that fits a 5090, the consumer card is faster. A 72 GB version reads memory at the same 1,344 GB/s and draws the same 300 W.
What it is good at
- 1,344 GB/s: 40% faster than an RTX 6000 Ada and three quarters faster than an RTX A6000, at the same 48 GB.
- Two slots and 300 W, with ECC memory.
- Blackwell generation: FP4 weight formats run natively, and MIG can split the card into two isolated instances.
What it is not
- Three quarters of a 5090's bandwidth: on any model that fits in 32 GB, a 5090 generates faster.
- Blackwell needs CUDA 12.8 or newer builds of PyTorch and llama.cpp; an old install will not use the card.
- Priced as professional hardware: the money buys capacity, ECC and the power figure, not speed.
The thing people get wrong: There are two RTX PRO 5000 Blackwell cards, 48 GB and 72 GB, and NVIDIA prints one bandwidth and one power figure for both: 1,344 GB/s and 300 W. The 72 GB card holds half as much again at the same speed ceiling. This page computes the 48 GB card; a listing that says only "RTX PRO 5000" does not tell you which.
Compared with the alternatives
- RTX PRO 6000 Blackwell: 96 GB · 1,792 GB/s · best fit Llama 3.3 70B at ~31 tok/s. Ninety-six gigabytes and 5090-class bandwidth on one card.
- RTX 5090: 32 GB · 1,792 GB/s · best fit Muse Glimmer 30B at ~73 tok/s. The first consumer card whose memory bandwidth changes what is comfortable.
- RTX 6000 Ada: 48 GB · 960 GB/s · best fit Muse Glimmer 30B at ~39 tok/s. Forty-eight gigabytes in a normal computer, at 300 watts, without the noise.
All 39 cards are compared side by side on the GPU index, and the same numbers from the model's point of view are on each model fit table. To check one specific pairing rather than read a table, use the can-I-run-it checker.
Questions
- Can an RTX PRO 5000 Blackwell run a 70B model?
- Not at Q4_K_M in one card. Llama 3.3 70B needs about 45.8 GB at 8k context and this card can address 48 GB. Your options are a smaller model, a harsher quantisation with very little context, splitting across two cards, or renting a larger one for the hours you need it.
- What is the best model to run on an RTX PRO 5000 Blackwell?
- Muse Glimmer 30B. At Q4_K_M and 8k context it needs about 18.7 GB of the 48 GB available and generates an estimated 54 tokens per second, which is comfortable for chat. It also fits at Q8, at about 33.5 GB, which is worth taking when it fits.
- How many tokens per second does an RTX PRO 5000 Blackwell generate?
- It depends entirely on the size of the model, because generating a token means reading every active weight out of memory. At 1,344 GB/s and 70% efficiency, this card produces an estimated 203 tokens per second on an 8B model at Q4, and about 541 on the largest model it holds, Qwen3.6 35B-A3B (MoE). Reading speed is roughly 5 to 8 words per second, so anything above 25 feels immediate. Treat 203 as a ceiling on 1,344 GB/s rather than a measurement; the higher a figure, the further real runtimes fall below it.
- Is 48 GB enough for running LLMs locally?
- It runs 28 of the 34 models tracked here at Q4_K_M with 8k of context, up to 36B parameters. The honest test is not the model list but the context: Muse Glimmer 30B on this card holds about 131,072 tokens before memory runs out.
- RTX PRO 5000 Blackwell or RTX PRO 6000 Blackwell for local models?
- The RTX PRO 6000 Blackwell holds more: 96 GB against 48 GB, so it runs 34 of these models to this card's 28. On speed, the RTX PRO 6000 Blackwell is faster: 1,792 GB/s against 1,344 GB/s, and bandwidth is what sets chat speed.
- RTX PRO 5000 or RTX 5090 for AI?
- The 5090 reads memory a third faster, 1,792 GB/s against 1,344 GB/s, so on any model that fits both it generates faster. The PRO 5000 holds 48 GB against 32 GB, or 72 GB in the larger version, draws 300 W against 575 W and has ECC memory. Choose by capacity: if your models fit in 32 GB, the 5090; if not, the PRO 5000.
- What is the memory bandwidth of the RTX PRO 5000 72 GB?
- 1,344 GB/s, the same as the 48 GB version: NVIDIA's specification table prints a single bandwidth and a single 300 W power figure across both. The 72 GB card holds half as much again, so it fits larger models at the same speed ceiling.
- Memory: weights (parameters × bytes per parameter) + KV cache (2 × layers × KV heads × head dim × context × bytes for a standard transformer; sliding-window, hybrid and latent-attention models counted as they actually cache) + 0.5 GB runtime + 4% of weights. Full derivation in the VRAM calculator.
- Speed: 70% × bandwidth ÷ active weight bytes, single stream, no batching, prompt processing excluded. A ceiling, not a measurement: the 17 of 28 figures marked ≤ are where real runtimes fall furthest below the number, because so few weights are read per token. See the tokens-per-second estimator.
- Card specification (manufacturer figures): 48 GB, 1,344 GB/s, 300 W; see NVIDIA's own page for this card.
- Model architecture values come from each model's published config; the self-hosted LLM guide explains what each one changes.