image model · qwen · Linux
Can I run Qwen-Image on Nvidia DGX Spark (128GB)?
Yes. Qwen-Image runs on Nvidia DGX Spark (128GB) at Q4_K_M GGUF (~14 GB of ~112 GB usable).
Runs at Q4_K_M GGUF using ~14 GB of ~112 GB usable.
- Peak VRAM
- ~14 GB
- Usable on device
- ~112 GB
- Device memory
- 128 GB
- Quant
- Q4_K_M GGUF
How to run it
Use ComfyUI or Nunchaku (SVDQuant 4-bit) at Q4_K_M GGUF. The big text encoder is loaded to encode your prompt, then offloaded before generation, which is why peak VRAM stays near the backbone size rather than the sum of every file.
- Type
- image (MMDIT)
- Parameters
- 20B
- Peak VRAM
- ~14 GB at Q4_K_M GGUF
- Resolution
- 1328×1328
- License
- Apache-2.0
- Memory
- 128 GB unified
- Usable for weights
- ~112 GB
- Power draw
- ~140 W
- Best runtime
- llama.cpp (CUDA) / Ollama (CUDA)
You could also run
Run Qwen-Image on other hardware
FAQ
Can Nvidia DGX Spark (128GB) run Qwen-Image?
Yes. Qwen-Image runs on Nvidia DGX Spark (128GB) at Q4_K_M GGUF (~14 GB of ~112 GB usable).
How much VRAM does Qwen-Image need?
Nvidia DGX Spark (128GB) has room to spare. At Q4_K_M GGUF the realistic peak is ~14 GB of VRAM, versus ~57 GB with every component kept resident (no offload). With aggressive CPU offload it drops to ~3 GB, much slower.
What do I use to run Qwen-Image locally?
Qwen-Image runs in ComfyUI or Nunchaku (SVDQuant 4-bit). It loads as a diffusion checkpoint plus its text encoder and VAE, not a single chat command.
Sources
-
docs.comfy.org · 1 source
-
docs.nvidia.com · 2 sources
-
github.com · 2 sources
-
huggingface.co · 2 sources
-
nvidia.com · 1 source
-
nvidianews.nvidia.com · 1 source
-
ollama.com · 1 source
-
sandner.art · 1 source
-
tomshardware.com · 1 source
VRAM figures are sourced peak-usage anchors at the noted quant; catalog updated 2026-11-01. See methodology.