What LLMs can an H200 run?

Models that fit on one H200

The most precise weights that still fit with 8K tokens of context and one request, the memory that takes, the longest context at that precision and the writing speed. Bigger models come first. gpt-oss-120b (67.7 GB, 270–548 tokens/s on the H200) and gpt-oss-20b (14.8 GB, 303–633 tokens/s on the H200) are listed at MXFP4 only, as published.

Too big for one H200 at 8K context

How many H200 cards these need at Q4_K_M with 8K context and 0.5 GB to spare, in one tensor-parallel group; some need more than 8.

• MiniMax M3: 2 cards
• Ling 3.1 Flash 560B-A25B: 4 cards
• DeepSeek V3 / R1: 4 cards
• DeepSeek V3.2: 4 cards
• GLM-5.3: 4 cards
• GLM-5.2: 4 cards
• DeepSeek V4.1 Flash 1017: 4 cards
• DeepSeek V4.1 Flash: 4 cards
• Hy4 Preview 770B-A49B: 4 cards
• MiMo V2.6 Pro: 8 cards
• DeepSeek V4 Pro: 8 cards
• Qwen3.8 2.4T-A95B: more than 8 cards
• Kimi K3: more than 8 cards

Best models for H200 with room for long context

The biggest models that still fit at Q4_K_M with 32,768 tokens of context (or their whole window, if shorter), the memory left over, the longest context the card takes at that precision and the writing speed with that context in the cache, from 4,800 GB/s of bandwidth.

llama-server commands for one H200

GGUF repos checked 2026-09-29; -c is the longest context with 0.5 GB free on the H200. No -ngl: llama.cpp’s -fit, on by default since b7440, places the layers.

Mistral Medium 3.5 128B, Q4_K_M with 160K tokens: 19–26 tokens/s on the H200

llama-server -hf unsloth/Mistral-Medium-3.5-128B-GGUF:Q4_K_M -c 163840

Q4_K_M/Mistral-Medium-3.5-128B-Q4_K_M-00001-of-00003.gguf, 74.9 GB: 140 GB used and 870 MB free of the H200's 141 GB, 19–26 tokens/s once the 160K cache is full.

Step 3.7 Flash 196B-A11B, Q4_K_M with 256K tokens: 66–115 tokens/s on the H200

llama-server -hf unsloth/Step-3.7-Flash-GGUF:Q4_K_M -c 262144 -np 1

UD-Q4_K_M/Step-3.7-Flash-UD-Q4_K_M-00001-of-00004.gguf, 122.1 GB: 139 GB used and 2.08 GB free of the H200's 141 GB, 66–115 tokens/s once the 256K cache is full. -np 1: one slot, one sliding window.

How fast the H200 writes as the context fills

Tokens per second at Q4_K_M (gpt-oss-120b at MXFP4) for the biggest models that fit with 32K tokens, with 8K and 32K tokens in the cache and at the longest context the card holds, and at Q8_0 with 8K where that fits. Each token reads the active weights and the whole cache once, so the speed follows the 4,800 GB/s of bandwidth and falls as the cache grows. The ceiling is that bandwidth divided by the bytes read per token, which no runtime reaches; the reply time is for 1,000 new tokens with 32K (or the longest context) in the cache, prompt processing aside.

Near misses on H200

Models that miss at Q4_K_M with 32,768 tokens of context (or their whole window), or leave under 0.5 GB free there, but fit with a shorter context or 3-bit weights, or are short by at most a quarter of the memory and fit with MoE offload. Smallest shortfall first.

What more cards or MoE offload unlock

One, two and four H200 cards in one tensor-parallel group (vLLM or SGLang), with the models each step adds at Q4_K_M and 8K context and their tokens per second on that group, and the median on-demand rent for that many cards (getdeploying.com, 2026-09-29).

Run locally or rent an H200?

Renting an H200 costs a median of $4.46 an hour on demand, across the providers getdeploying.com tracks (checked 2026-09-29), so every $1,000 of purchase price equals about 224 hours of rent, 9 days around the clock. At that rate Step 3.7 Flash 196B-A11B at Q4_K_M with 32K tokens, the biggest model here that fits with a long context, writes 136–250 tokens/s for one request: about $5.0–9.1 per million generated tokens. Electricity and resale value are left out, and no card prices are listed because 2026 street prices vary widely between sellers; compare current ones before you decide.

Serving with vLLM on the H200

The KV cache pool vLLM builds at its default --gpu-memory-utilization 0.92 and --max-model-len 32768, weights as published, from the vLLM KV cache calculator. The pool is shared by every request; the last column assumes 4,096 tokens each.

How these numbers are worked out

Memory is the weights at each precision plus the KV cache for 8,192 tokens in FP16 and runtime overhead (0.5 GB plus 10%), computed from each model's files on Hugging Face with the LLM VRAM Calculator. Speed is estimated from memory bandwidth and the parameters read per token with the LLM Speed Calculator. Both tools take any other model from Hugging Face.

Nearby GPUs and setups

How many of the tracked models each one holds at Q4_K_M with 8K context, against 50 here.