VOOZH about

URL: https://willitrunai.com/can-run/qwen-2.5-vl-72b-on-m3-ultra-96gb


Can Qwen 2.5 VL 72B run on Mac Studio M3 Ultra 96GB?

YES — Tight Fit

S88Excellent
Estimated from fit model

Qwen 2.5 VL 72B needs ~60.1 GB VRAM. Mac Studio M3 Ultra 96GB has 69.1 GB. With Q4_K_M quantization, expect ~13 tok/s.

Runtime: llama.cppCapacity: TightBandwidth: HighStack: StandardBottleneck: Balanced
Share:

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 60.1 GB, 13.8 tok/s, Tight fit
60.1 GB required69.1 GB available
87% VRAM used

Fit status

Tight fit

Decode

13.8 tok/s

TTFT

14039 ms

Safe context

33K

Memory

60.1 GB / 69.1 GB

Memory breakdown

Weights43.9 GB
KV Cache4.9 GB
Runtime0.9 GB
Headroom10.4 GB

See how fast it feels

See how fast it feelsQwen 2.5 VL 72B on Mac Studio M3 Ultra 96GB
1st promptCold start — includes initialization
>Solve: If a train travels at 60 mph for 2.5 hours, how far does it go?
Let me work through this step by step. Given information: - Speed = 60 mph (miles per hour) - Time = 2.5 hours Formula: Distance = Speed x Time Calculation: Distance = 60 mph x 2.5 h = 150 miles The train travels 150 miles. Double-check: at 60 mph the train covers 60 miles each hour. In half an hour it covers 30 miles. So in 2.5 hours: 60 + 60 + 30 = 150 miles. Confirmed.
2nd promptWarm — model ready, no init overhead
>What if the train stops for 20 minutes halfway?
The stop doesn't change the total distance covered while moving, but it affects total trip time. Breakdown: - First half: 1.25 hours at 60 mph = 75 miles - Stop: 20 minutes (no distance) - Second half: 1.25 hours at 60 mph = 75 miles Total distance: 150 miles (same) Total time: 2.5 h + 0.33 h = 2.83 hours Average speed: 150 / 2.83 = 53 mph The distance stays the same but average speed drops to 53 mph because of the stop.
Estimated: 13.8 tok/s decode · 14.0s TTFT (warm) · 35 tok/s prefill

What limits this setup

This setup is broadly balanced for this model.

Shared-memory contention still exists

The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.

Best improvement path

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatSTight fit12.7 tok/s8328 ms33K
CodingSTight fit12.7 tok/s15268 ms33K
Agentic CodingSTight fit12.7 tok/s22208 ms33K
ReasoningSTight fit12.7 tok/s18044 ms33K
RAGSTight fit12.7 tok/s27760 ms33K

Quantization options

How Qwen 2.5 VL 72B (72B params) fits at each quantization level on Mac Studio M3 Ultra 96GB (69.1 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
28.1 GB
LowS86
Q3_K_S
3
35.3 GB
LowS88
NVFP4
4

Get started

Copy-paste commands to run Qwen 2.5 VL 72B on your machine.

Run

lms load Qwen2.5-VL-72B-Instruct && lms server start

Your hardware

More models your Mac Studio M3 Ultra 96GB can run

ModelParamsGradeDecodeCapabilities
👁 Cohere
Command A 111B
111BA6.8 tok/s

Frequently asked questions

See all results for Mac Studio M3 Ultra 96GBSee all hardware for Qwen 2.5 VL 72B
40.3 GB
Medium
S88
Q4_K_M
4
43.9 GB
MediumS88
Q5_K_MBest for your GPU
5
51.8 GB
HighS88
Q6_K
6
59.0 GB
HighF0
Q8_0
8
77.0 GB
Very HighF0
F16
16
147.6 GB
MaximumF0

Not always. Mac Studio M3 Ultra 96GB can often fit larger models thanks to unified memory, but a discrete GPU with dedicated high-bandwidth VRAM may still decode faster once the model fits. For this combination, the important distinction is capacity versus sustained throughput.