Qwen2.5-VL 72B has 73.4B parameters. In BF16 its weights alone take 137 GiB; quantized to 4-bit, about 43.7 GiB. Each 32K-token request adds 10.0 GiB of KV cache. Cheapest way to run it today: 4 × RTX A4000 (16 GB) at $0.288 per hour. It reads text, images and video.
Read every day from Hugging Face. Split files are added together; vision projectors are left out.
How many GPUs to run Qwen2.5-VL 72B
Fewest GPUs that fit the weights plus one 8K-token request. Data-center GPUs use vLLM (90% of memory usable), the others llama.cpp. Several GPUs split the model with tensor or pipeline parallelism.
GPU
BF16 / FP16
8-bit
4-bit
GeForce RTX 4090 24 GB
7
4
3
GeForce RTX 5090 32 GB
5
3
2
RTX PRO 6000 Blackwell 96 GB
2
1
1
Mac M5 Max 128 GB 96 GB usable
2
1
1
Ryzen AI Max+ 395 128 GB 96 GB usable
2
1
1
DGX Spark (GB10) 128 GB
2
1
1
NVIDIA H100 80 GB
3
2
1
NVIDIA H200 141 GB
2
1
1
NVIDIA B200 (HGX) 180 GB
1
1
1
8-bit: FP8 with vLLM (INT8 on GPUs without FP8), Q8_0 with llama.cpp. 4-bit: AWQ / GPTQ with vLLM, Q4_K_M with llama.cpp, both counted at the Q4_K_M size.
Cheapest way to run Qwen2.5-VL 72B today
For each GPU: the fewest cards that fit Qwen2.5-VL 72B with one 8K-token request, the most faithful weight format at that count, and the cheapest on-demand price (2026-11-06).
On-demand prices from AWS, Google Cloud, Azure, RunPod, Vast.ai, Oracle Cloud, OVHcloud, Scaleway, Verda, Akash and UpCloud, checked every hour. Serving many users needs more KV cache, so more memory: size it in the calculator. Some links are affiliate links: StudioTV may earn a commission, at no extra cost to you.
vLLM and SGLang apply these defaults unless a request sets its own. With llama.cpp, pass them yourself: --temp 0 --repeat-penalty 1.05
KV cache: how memory grows with context
Architecture: 80 layers · 80 full attention (8 KV × 128). Every layer keeps keys and values for every token (grouped-query attention), so the cache grows linearly with context.
Context per request
BF16 cache
FP8 cache
8K tokens
2.50 GiB
1.25 GiB
32K tokens
10.0 GiB
5.00 GiB
Qwen2.5-VL 72B VRAM FAQ
How much VRAM does Qwen2.5-VL 72B need?
In BF16 the weights alone take 137 GiB (147 GB). In FP8 that is 70.7 GiB, and about 43.7 GiB with 4-bit quantization (Q4_K_M). Each request then adds KV cache: 2.50 GiB at 8K tokens and 10.0 GiB at 32K (BF16 cache).
Can Qwen2.5-VL 72B run on a single RTX 4090 (24 GB)?
No. Even in 4-bit it needs 3 RTX 4090s. In 4-bit it fits on a single RTX PRO 6000 Blackwell (96 GB).
Can Qwen2.5-VL 72B run on an RTX 5090 (32 GB)?
No. Even in 4-bit it needs 2 RTX 5090s.
Can Qwen2.5-VL 72B run on a Mac?
Yes. In 4-bit (Q4_K_M with llama.cpp) it needs a Mac with 64 GB of unified memory or more, of which macOS gives the GPU about 48 GB, for one request with an 8K-token context. In 8-bit (Q8_0) it needs 128 GB or more.
Can Qwen2.5-VL 72B run on a DGX Spark or a Ryzen AI Max+ 395 (128 GB)?
Yes. In Q8_0 (73.2 GiB with an 8K-token context) it fits on a DGX Spark (128 GB) and on a Ryzen AI Max+ 395 with 128 GB, whose GPU gets up to 96 GB, with llama.cpp and one request.
What is the cheapest way to run Qwen2.5-VL 72B?
On 2026-11-06, the cheapest on-demand setup is 4 × RTX A4000 (16 GB) with Q4_K_M weights on Vast.ai, at $0.288 per hour (about $210.24 per month). Next: 3 × NVIDIA L4 (24 GB) with 4-bit weights on Vast.ai, at $0.312 per hour. Sized for one 8K-token request; prices are checked every hour.
How many H100 GPUs does Qwen2.5-VL 72B need?
With one request and an 8K-token context: 3 in BF16, 2 in FP8 and 1 in 4-bit (vLLM, 90% of memory usable). Serving many users at once needs more memory for their KV caches: the calculator sizes that for you.
Can Qwen2.5-VL 72B read images?
Yes. Qwen2.5-VL 72B reads text, images and video. Images add tokens to the context, so they also add KV cache.
What temperature should I use with Qwen2.5-VL 72B?
The official defaults are temperature 0, repetition penalty 1.05.
What is Qwen2.5-VL 72B's knowledge cutoff?
June 2024, according to OpenRouter: it knows little about later events.
Qwen2.5-VL 72B VRAM badge
For a model card or a README: the 4-bit size and the smallest GPU it fits on, linked to this page. Data as JSON: /api/models/qwen2-5-vl-72b.json.
Estimates, not guarantees: computed from the official config.json with the same engine as the LLM VRAM Calculator. Real usage depends on your engine version and settings.