Qwen3 30B-A3B Thinking 2507 on AMD Radeon PRO W7800 32GB

Can the AMD Radeon PRO W7800 32GB run Qwen3 30B-A3B Thinking 2507?

Yes, it runs great

Runs great. At Q5_K_M it needs about 24.7 GB of 32.0 GB usable, with an estimated speed of 99.4 tok/s.

Best quant: Q5_K_M
Generation speed: 99.4 tok/s
Prompt processing: 16,984 tok/s
First token (1K prompt): 0.3 s
Largest safe context: 80K

Best app to run it on the AMD Radeon PRO W7800 32GB

On Windows

Lemonade

Desktop app · runs on llama.cpp, ONNX Runtime GenAI (Ryzen AI NPU)

AMD’s own app: llama.cpp tuned for Radeon on Vulkan and ROCm.

lemonade pull unsloth/Qwen3-30B-A3B-Thinking-2507-GGUF:Q5_K_M

LM Studio Point-and-click: search, download and chat in one window.
Ollama One command with Ollama’s own build of this model.

On Linux

Lemonade

Desktop app · runs on llama.cpp, ONNX Runtime GenAI (Ryzen AI NPU)

AMD’s own app: llama.cpp tuned for Radeon on Vulkan and ROCm.

lemonade pull unsloth/Qwen3-30B-A3B-Thinking-2507-GGUF:Q5_K_M

LM Studio Point-and-click: search, download and chat in one window.
Ollama One command with Ollama’s own build of this model.

Want an agent? Qwen3 30B-A3B Thinking 2507 supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download Qwen3 30B-A3B Thinking 2507

Recommended for the AMD Radeon PRO W7800 32GB: Q5_K_M. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run qwen3:30b-thinking

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q5_K_M file (opens in a new tab)

huggingface.co/unsloth/Qwen3-30B-A3B-Thinking-2507-GGUF (opens in a new tab)

ollama run hf.co/unsloth/Qwen3-30B-A3B-Thinking-2507-GGUF:Q5_K_M

Original weights · Hugging Face

Full-precision files from Alibaba, for fine-tuning, vLLM, Transformers.

huggingface.co/Qwen/Qwen3-30B-A3B-Thinking-2507 (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Alibaba. The weights themselves download from Hugging Face.

github.com/QwenLM/Qwen3 (opens in a new tab)

Qwen’s main repo, renamed from Qwen2.5 to Qwen3; it still documents Qwen2.5.

git clone https://github.com/QwenLM/Qwen3

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 75Great quality (A) · 75 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking.: How capable the model itself is at Q5_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs great: How well it runs on the AMD Radeon PRO W7800 32GB: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.	34.0 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.	25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.	15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.	15.0 / 15
Match score	89.0 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the AMD Radeon PRO W7800 32GB

Quant	Memory needed	Available	Speed	Runs	Quality	Download
`Q2_K`	15.2 GB	32.0 GB	156 tok/s	Runs great	54Fair quality (C) · 54 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q3_K_M`	18.0 GB	32.0 GB	135 tok/s	Runs great	65Good quality (B) · 65 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 82/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q4_K_M`	21.6 GB	32.0 GB	114 tok/s	Runs great	74Great quality (A) · 74 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q5_K_M`	24.7 GB	32.0 GB	99.4 tok/s	Runs great	75Great quality (A) · 75 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q6_K`	28.0 GB	32.0 GB	87.6 tok/s	Runs welltight fit	77Great quality (A) · 77 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`Q8_0`	35.4 GB	32.0 GB	46.3 tok/s	Runs welloffloads to RAM	78Great quality (A) · 78 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking.	GGUF (opens in a new tab)
`F16`	64.1 GB	32.0 GB	—	Won't run	78Great quality (A) · 78 of 100: how capable the model is at F16, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking.	GGUF · folder (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

78Great quality (A) · 78 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. Apple M1 Max (64 GB) Q8_0 · 52.3 tok/s · Runs great
78Great quality (A) · 78 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Max (64 GB) Q8_0 · 66.5 tok/s · Runs great
78Great quality (A) · 78 of 100: how capable the model is at F16, whatever it runs on. Match score 90/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA RTX PRO 6000 Blackwell F16 · 92.9 tok/s · Runs great
77Great quality (A) · 77 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. Apple M4 Pro (48 GB) Q6_K · 49.8 tok/s · Runs great
75Great quality (A) · 75 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 89/100 (quality, fit, speed and memory use) sets the ranking. NVIDIA GeForce RTX 5090 Q5_K_M · 188 tok/s · Runs great
74Great quality (A) · 74 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 87/100 (quality, fit, speed and memory use) sets the ranking. AMD Radeon RX 7900 XTX Q4_K_M · 151 tok/s · Runs well (tight fit)

Quick answers

How much memory does Qwen3 30B-A3B Thinking 2507 need on the PRO W7800 32GB?

At Q5_K_M it needs about 24.7 GB. The PRO W7800 32GB has 32.0 GB usable.

How fast is Qwen3 30B-A3B Thinking 2507 on the PRO W7800 32GB?

About 99.4 tok/s at Q5_K_M, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of Qwen3 30B-A3B Thinking 2507 should I use on the PRO W7800 32GB?

Q5_K_M. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.