H200 vs MI300X
The MI300X rents for 42% less per hour today — $2.59 against $4.45 — with 192 GB against 141 GB of memory.
Prices collected 2026-09-18 · 6 providers price both
Index median per GPU-hour, on-demand, per snapshot.
Side by side
| H200 | MI300X | |
|---|---|---|
| Median rental, per GPU-hour | $4.45 | $2.59 |
| Cheapest listing | $2.00 | $0.50 |
| Per month at 720 h | $3,204 | $1,865 |
| Providers pricing it | 35 | 7 |
| Memory | 141 GB HBM3e | 192 GB HBM3 |
| Memory bandwidth | 4,800 GB/s | 5,300 GB/s |
| GB of memory per $/hr | 31.7 | 74.1 |
| Architecture | Hopper | CDNA 3 |
| Class | Datacenter | Datacenter |
| Released | 2023-11 | 2023-12 |
Same provider, both GPUs
The cleanest comparison: 6 providers price both cards, so the difference is the GPU and nothing else. The H200 is cheaper at 0 of them.
| Provider | H200 | MI300X | MI300X premium |
|---|---|---|---|
 RunPod Community Cloud | $3.59 | $0.50 | -86% |
 Crusoe | $4.29 | $3.45 | -20% |
 DigitalOcean GPU Droplets | $4.47 | $2.59 | -42% |
 RunPod Secure Cloud | $4.59 | $2.39 | -48% |
| $4.79 | $3.59 | -25% | |
 Oracle Cloud | $10.00 | $6.00 | -40% |
What each one runs, and what a million tokens costs
Weights + KV cache at 8K context + overhead against 90% of each card's memory. Where a model needs more than one card the cell says how many and prices the set at today's median. $/M tokens is the hourly median divided by estimated single-stream output, from memory bandwidth — an estimate for ranking, not a benchmark.
| Model | Bits | H200 | MI300X |
|---|---|---|---|
| Kimi K3 | 4-bit | 13× GPU$57.85/hr | 10× GPU$25.90/hr |
| Kimi K3 | 16-bit | 45× GPU$200.25/hr | 33× GPU$85.47/hr |
| DeepSeek V4.1-Flash | 4-bit | 3× GPU$13.35/hr | 2× GPU$5.18/hr |
| DeepSeek V4.1-Flash | 16-bit | 9× GPU$40.05/hr | 7× GPU$18.13/hr |
| Llama 4 Maverick | 4-bit | 2× GPU$8.90/hr | 2× GPU$5.18/hr |
| Llama 4 Maverick | 16-bit | 7× GPU$31.15/hr | 5× GPU$12.95/hr |
| gpt-oss-120b | 4-bit | ✓ 67.9 GB~1339 tok/s · $0.92/M | ✓ 67.9 GB~1478 tok/s · $0.49/M |
| gpt-oss-120b | 16-bit | 2× GPU$8.90/hr | 2× GPU$5.18/hr |
| Llama 3.1 70B | 4-bit | ✓ 44.5 GB~98 tok/s · $12.61/M | ✓ 44.5 GB~108 tok/s · $6.66/M |
| Llama 3.1 70B | 16-bit | 2× GPU$8.90/hr | ✓ 145.1 GB~30 tok/s · $23.98/M |
| Gemma 4 31B | 4-bit | ✓ 21.2 GB~220 tok/s · $5.62/M | ✓ 21.2 GB~243 tok/s · $2.96/M |
| Gemma 4 31B | 16-bit | ✓ 65.7 GB~62 tok/s · $19.94/M | ✓ 65.7 GB~68 tok/s · $10.58/M |
| Qwen3 Coder 30B-A3B | 4-bit | ✓ 19 GB~2069 tok/s · $0.6/M | ✓ 19 GB~2284 tok/s · $0.31/M |
| Qwen3 Coder 30B-A3B | 16-bit | ✓ 62.9 GB~582 tok/s · $2.12/M | ✓ 62.9 GB~642 tok/s · $1.12/M |
| Qwen3.8 27B | 4-bit | ✓ 18.7 GB~253 tok/s · $4.89/M | ✓ 18.7 GB~279 tok/s · $2.58/M |
| Qwen3.8 27B | 16-bit | ✓ 57.6 GB~71 tok/s · $17.41/M | ✓ 57.6 GB~79 tok/s · $9.11/M |
| gpt-oss-20b | 4-bit | ✓ 13.7 GB~1896 tok/s · $0.65/M | ✓ 13.7 GB~2094 tok/s · $0.34/M |
| gpt-oss-20b | 16-bit | ✓ 43.9 GB~533 tok/s · $2.32/M | ✓ 43.9 GB~589 tok/s · $1.22/M |
| Llama 3.1 8B | 4-bit | ✓ 6.9 GB~853 tok/s · $1.45/M | ✓ 6.9 GB~942 tok/s · $0.76/M |
| Llama 3.1 8B | 16-bit | ✓ 18.4 GB~240 tok/s · $5.15/M | ✓ 18.4 GB~265 tok/s · $2.71/M |
Buy or rent?
Hours of renting at today's median that add up to the card's approximate list price. List prices are typical quoted figures, not tracked, and do not include the server, power or the person to run it — so the break-even is a floor, not a verdict.
Questions
Is the H200 or the MI300X cheaper to rent?
On 2026-09-18 the H200 has a market median of $4.45 per GPU-hour across 35 providers and the MI300X $2.59 across 7, so the MI300X is 42% cheaper per hour. Among the 6 providers that price both, the H200 is cheaper at 0 and the MI300X at 6. Per hour is only half the answer — the table below prices a whole model on each.
Which should I rent for a 70B model?
At 4-bit, Llama 3.1 70B needs about 44.5 GB. On the H200 that is one card at $4.45/hr; on the MI300X one card at $2.59/hr. Estimated single-stream decode is ~98 vs ~108 tokens per second, from memory bandwidth.
What is the real difference between them?
141 GB HBM3e at 4,800 GB/s (Hopper) against 192 GB HBM3 at 5,300 GB/s (CDNA 3). Memory decides what fits; bandwidth decides how fast it generates, because each token streams the active weights once. Compute matters for prompt processing and training, not for how fast text appears.