All compatibility checks

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.

ModelParamsPrecisionTotal VRAM% of 141 GB
Qwen2.5 32B Instruct32.8BFP16 / BF1676.4 GB54%Details
Qwen2.5 Coder 32B Instruct32.76BFP16 / BF1676.3 GB54%Details
Qwen3 32B32.76BFP16 / BF1676.3 GB54%Details
DeepSeek R1 Distill Qwen 32B32.76BFP16 / BF1676.3 GB54%Details
QwQ 32B32.76BFP16 / BF1676.3 GB54%Details
Gemma 2 27B Instruct27.2BFP16 / BF1664 GB45%Details
Mistral Small 24B Instruct23.57BFP16 / BF1654.8 GB39%Details
Qwen2.5 14B Instruct14.77BFP16 / BF1634.8 GB25%Details
Qwen3 14B14.77BFP16 / BF1634.6 GB25%Details
DeepSeek R1 Distill Qwen 14B14.77BFP16 / BF1634.8 GB25%Details
Qwen2.5 Coder 14B Instruct14.77BFP16 / BF1634.8 GB25%Details
Phi-414.66BFP16 / BF1634.5 GB24%Details
Mistral Nemo Instruct12.25BFP16 / BF1628.8 GB20%Details
Gemma 2 9B Instruct9.24BFP16 / BF1622.6 GB16%Details
Qwen3 8B8.19BFP16 / BF1619.4 GB14%Details
Granite 3.1 8B Instruct8.17BFP16 / BF1619.4 GB14%Details
Llama 3.1 8B Instruct8.03BFP16 / BF1619 GB13%Details
DeepSeek R1 Distill Llama 8B8.03BFP16 / BF1619 GB13%Details
Qwen2.5 7B Instruct7.62BFP16 / BF1617.7 GB13%Details
Qwen2.5 Coder 7B Instruct7.62BFP16 / BF1617.7 GB13%Details
DeepSeek R1 Distill Qwen 7B7.62BFP16 / BF1617.7 GB13%Details
OLMo 2 7B Instruct7.3BFP16 / BF1618.8 GB13%Details
Mistral 7B Instruct v0.37.25BFP16 / BF1617.2 GB12%Details
Qwen3 4B4.02BFP16 / BF169.8 GB7%Details
Phi-3.5 Mini Instruct3.82BFP16 / BF1610.3 GB7%Details
Llama 3.2 3B Instruct3.21BFP16 / BF167.8 GB6%Details
Qwen2.5 3B Instruct3.09BFP16 / BF167.2 GB5%Details
Qwen3 1.7B2.03BFP16 / BF165.1 GB4%Details
DeepSeek R1 Distill Qwen 1.5B1.78BFP16 / BF164.2 GB3%Details
SmolLM2 1.7B Instruct1.71BFP16 / BF164.7 GB3%Details
Qwen2.5 1.5B Instruct1.54BFP16 / BF163.6 GB3%Details
Qwen2.5 Coder 1.5B Instruct1.54BFP16 / BF163.6 GB3%Details
Qwen3 0.6B0.75BFP16 / BF162.1 GB1%Details
Qwen2.5 0.5B Instruct0.49BFP16 / BF161.1 GB1%Details
SmolLM2 360M Instruct0.36BFP16 / BF161 GB1%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.

ModelParamsPrecisionTotal VRAM% of 141 GB
Qwen2.5 72B Instruct72.71BINT8 (8-bit)84.8 GB60%Details
Llama 3.1 70B Instruct70.6BINT8 (8-bit)82.5 GB59%Details
DeepSeek R1 Distill Llama 70B70.55BINT8 (8-bit)82.3 GB58%Details

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.