Qwen-Image-Edit 2511 on NVIDIA GeForce RTX 5080
Can the NVIDIA GeForce RTX 5080 run Qwen-Image-Edit 2511?
Yes, but slowly (CPU offload)
Slow (CPU offload). At FP8 it needs about 10.7 GB of 16.0 GB usable, with an estimated speed of 2.1 min.
- Best precision
FP8- Memory mode
- Sequential CPU offload
- Time per image
- 2.1 min
- Output
- 1024×1024, 40 steps
Best app to run it on the NVIDIA GeForce RTX 5080
On Windows
- Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.
On Linux
- Runs this model with built-in or popular custom nodes; GGUF files load with ComfyUI-GGUF.
Download Qwen-Image-Edit 2511
Quantized files · GGUF for ComfyUI
Smaller GGUF versions for ComfyUI (with the ComfyUI-GGUF node). No sign-in needed; the model’s license still applies.
huggingface.co/unsloth/Qwen-Image-Edit-2511-GGUF (opens in a new tab)
Original weights · Hugging Face
Full-precision files from Alibaba, for fine-tuning, vLLM, Transformers, Diffusers or ComfyUI.
huggingface.co/Qwen/Qwen-Image-Edit-2511 (opens in a new tab)
Official repo · GitHub
Reference code, inference scripts and docs from Alibaba. The weights themselves download from Hugging Face.
github.com/QwenLM/Qwen-Image (opens in a new tab)
git clone https://github.com/QwenLM/Qwen-ImageHow it’s rated
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 quality | 37.9 / 45 | |
|---|---|---|
| Memory fit | 12.0 / 25 | |
| Speed | 4.2 / 15 | |
| Memory use | 15.0 / 15 | |
| Match score | 69.2 / 100 |
Every precision on the NVIDIA GeForce RTX 5080
| Quant | Memory needed | Available | Speed | Memory mode | Runs | Quality | Download |
|---|---|---|---|---|---|---|---|
FP16 | 17.8 GB | 16.0 GB | — | — | Won't run | 86Excellent quality (A+) · 86 of 100: how capable the model is at FP16, whatever it runs on. Match score 11/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
FP8 | 10.7 GB | 16.0 GB | 2.1 min | Sequential CPU offload | SlowCPU offload | 84Great quality (A) · 84 of 100: how capable the model is at FP8, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. | Original weights (opens in a new tab) |
Q8 GGUF | 11.2 GB | 16.0 GB | 2.7 min | Sequential CPU offload | Very slowCPU offload | 85Excellent quality (A+) · 85 of 100: how capable the model is at Q8 GGUF, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Q4 GGUF | 7.8 GB | 16.0 GB | 2.8 min | Sequential CPU offload | Very slowCPU offload | 79Great quality (A) · 79 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 62/100 (quality, fit, speed and memory use) sets the ranking. | GGUF (opens in a new tab) |
Other hardware that runs it
-
86Excellent quality (A+) · 86 of 100: how capable the model is at FP16, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA RTX PRO 6000 Blackwell
-
79Great quality (A) · 79 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 5090
-
79Great quality (A) · 79 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 4090
-
79Great quality (A) · 79 of 100: how capable the model is at Q4 GGUF, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking.
AMD Radeon RX 7900 XTX
-
84Great quality (A) · 84 of 100: how capable the model is at FP8, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking.
AMD Radeon RX 9070 XT
-
84Great quality (A) · 84 of 100: how capable the model is at FP8, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking.
NVIDIA GeForce RTX 4080 SUPER
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.