Data center · NVIDIA · 141 GB VRAM
What can you run on the H200 141GB?
The H200 141GB has 141 GB of VRAM. Of the 38 models we track, 38 run on this card — 35 at full FP16 precision and 3 once quantized. Every figure below counts model weights plus the KV cache at a 4,096-token context.
35
Run in FP16
3
Need quantization
0
Do not fit
Runs at full FP16 precision
These models fit without quantization, so you keep full output quality.
| Model | Params | Precision | Total VRAM | % of 141 GB | |
|---|---|---|---|---|---|
| Qwen2.5 32B Instruct | 32.8B | FP16 / BF16 | 76.4 GB | 54% | Details |
| Qwen2.5 Coder 32B Instruct | 32.76B | FP16 / BF16 | 76.3 GB | 54% | Details |
| Qwen3 32B | 32.76B | FP16 / BF16 | 76.3 GB | 54% | Details |
| DeepSeek R1 Distill Qwen 32B | 32.76B | FP16 / BF16 | 76.3 GB | 54% | Details |
| QwQ 32B | 32.76B | FP16 / BF16 | 76.3 GB | 54% | Details |
| Gemma 2 27B Instruct | 27.2B | FP16 / BF16 | 64 GB | 45% | Details |
| Mistral Small 24B Instruct | 23.57B | FP16 / BF16 | 54.8 GB | 39% | Details |
| Qwen2.5 14B Instruct | 14.77B | FP16 / BF16 | 34.8 GB | 25% | Details |
| Qwen3 14B | 14.77B | FP16 / BF16 | 34.6 GB | 25% | Details |
| DeepSeek R1 Distill Qwen 14B | 14.77B | FP16 / BF16 | 34.8 GB | 25% | Details |
| Qwen2.5 Coder 14B Instruct | 14.77B | FP16 / BF16 | 34.8 GB | 25% | Details |
| Phi-4 | 14.66B | FP16 / BF16 | 34.5 GB | 24% | Details |
| Mistral Nemo Instruct | 12.25B | FP16 / BF16 | 28.8 GB | 20% | Details |
| Gemma 2 9B Instruct | 9.24B | FP16 / BF16 | 22.6 GB | 16% | Details |
| Qwen3 8B | 8.19B | FP16 / BF16 | 19.4 GB | 14% | Details |
| Granite 3.1 8B Instruct | 8.17B | FP16 / BF16 | 19.4 GB | 14% | Details |
| Llama 3.1 8B Instruct | 8.03B | FP16 / BF16 | 19 GB | 13% | Details |
| DeepSeek R1 Distill Llama 8B | 8.03B | FP16 / BF16 | 19 GB | 13% | Details |
| Qwen2.5 7B Instruct | 7.62B | FP16 / BF16 | 17.7 GB | 13% | Details |
| Qwen2.5 Coder 7B Instruct | 7.62B | FP16 / BF16 | 17.7 GB | 13% | Details |
| DeepSeek R1 Distill Qwen 7B | 7.62B | FP16 / BF16 | 17.7 GB | 13% | Details |
| OLMo 2 7B Instruct | 7.3B | FP16 / BF16 | 18.8 GB | 13% | Details |
| Mistral 7B Instruct v0.3 | 7.25B | FP16 / BF16 | 17.2 GB | 12% | Details |
| Qwen3 4B | 4.02B | FP16 / BF16 | 9.8 GB | 7% | Details |
| Phi-3.5 Mini Instruct | 3.82B | FP16 / BF16 | 10.3 GB | 7% | Details |
| Llama 3.2 3B Instruct | 3.21B | FP16 / BF16 | 7.8 GB | 6% | Details |
| Qwen2.5 3B Instruct | 3.09B | FP16 / BF16 | 7.2 GB | 5% | Details |
| Qwen3 1.7B | 2.03B | FP16 / BF16 | 5.1 GB | 4% | Details |
| DeepSeek R1 Distill Qwen 1.5B | 1.78B | FP16 / BF16 | 4.2 GB | 3% | Details |
| SmolLM2 1.7B Instruct | 1.71B | FP16 / BF16 | 4.7 GB | 3% | Details |
| Qwen2.5 1.5B Instruct | 1.54B | FP16 / BF16 | 3.6 GB | 3% | Details |
| Qwen2.5 Coder 1.5B Instruct | 1.54B | FP16 / BF16 | 3.6 GB | 3% | Details |
| Qwen3 0.6B | 0.75B | FP16 / BF16 | 2.1 GB | 1% | Details |
| Qwen2.5 0.5B Instruct | 0.49B | FP16 / BF16 | 1.1 GB | 1% | Details |
| SmolLM2 360M Instruct | 0.36B | FP16 / BF16 | 1 GB | 1% | Details |
Runs with quantization
These need an INT8 or 4-bit build (GPTQ, AWQ, or GGUF). Quality stays close to full precision for most chat work, but re-test structured output and tool calling before shipping.
How to read these numbers
Whether a model runs on the H200 141GB comes down to three memory costs measured against its 141 GB. First the weights: parameter count times bytes per parameter — 2 bytes in FP16, 1 in INT8, roughly 0.5 at 4-bit. Second the KV cache, which holds attention keys and values for every token in the context window and grows linearly with prompt length; it stays in FP16 even when the weights are quantized. Third, an allowance for activations, CUDA context, and fragmentation. A fit is only called comfortable when the total leaves about 10% headroom.
The practical consequence is that the table above is a starting point, not a guarantee. A model listed as fitting at 4,096 tokens can still run out of memory once conversations get long or several requests run at once, because the KV cache term grows with both. If you plan to use long context or serve concurrent users, size with the VRAM Calculator at your real context length before committing.
Compare other data center GPUs
Frequently asked questions
What AI models can the H200 141GB run?
The H200 141GB has 141 GB of VRAM and runs 38 of the 38 models we track: 35 at full FP16 precision and 3 more once quantized to 8-bit or 4-bit.
What is the largest LLM the H200 141GB can run?
Qwen2.5 32B Instruct (32.8B parameters) is the largest model that fits, using about 76.4 GB at FP16 / BF16.
Do I need quantization on the H200 141GB?
For larger models, yes. 35 models run in full FP16, but 3 only fit once you drop to INT8 or 4-bit using a GPTQ, AWQ, or GGUF build.
Why does the VRAM number here differ from the model size?
Model weights are only part of the cost. Every estimate here also adds the KV cache, which stores attention keys and values for each token in the context window and grows as your prompt gets longer. These figures use a 4,096-token context and leave about 10% headroom for activations and fragmentation.