Models / Qwen-Image-2.1

Image generation and editing in one 7B model. Qwen-Image-2.1 is a 32-layer single-stream DiT (7B parameters in the visual generation component) with a Qwen3-VL 8B text encoder and a 64-channel RGBA VAE at 16x spatial compression. It generates and edits transparent RGBA images natively (the Layered lineage folded in), takes up to 10 reference images per edit, supports local edits via circles, painted marks, or separate masks with identity preservation for people and products, and outputs up to 2752x1536 natively (default 2048x2048, 40 inference steps). Efficiency comes from mixed-granularity attention (token-level causal masking for text, chunk-level for image) plus prefix KV cache reuse across denoising steps.

License is the catch. Qwen-Image 1 shipped under Apache 2.0; this release drops to the Qwen Research License: non-commercial use only, and any commercial purpose requires a separate license from Qwen ([email protected]). The site open-weights classification counts it as open, but research and evaluation are the only permitted uses out of the box. Budget for the commercial license before building a product on it.

Ecosystem, day one. diffusers QwenImage21Pipeline, native ComfyUI with official workflows, vLLM-Omni (FP8, CUDA graphs), SGLang, LightX2V, and stable-diffusion.cpp; AMD ROCm and FlagOS multi-chip support are noted in the README.

What to treat as claims. The Qwen-Image-Bench score (60.28, rank 6, behind GPT Image 2.5 at 67.01 and ahead of Nano Banana 2 at 59.83) is Qwen own benchmark - self-scored, no independent eval yet. The memory figure is community-reported, not official: a Q8 runtime at 15.6 GB VRAM total (7.3 DiT + 7.7 text encoder + 0.6 VAE) on RTX 3090-class cards, with diffusers enable_model_cpu_offload() path for smaller ones. Community reports of a periodic dot pattern in midtones exist but are unverified; treat content marking as unknown until confirmed.

image-generation image-editing
Parameters
7.0B
License
qwen research
Developer
Alibaba
Origin
🇨🇳 China
Released
Sep 2026

Save your hardware and every model page answers the real question: will it run on your machine, and how fast?

Join free - save your rig →

Run it locally

Per-quant memory needs and a static "can you run it?" reference - no rig entry required

Q8_0
15.6GB 16.0GB min 20.0GB rec
Near-lossless

The reference hardware

Schematic of the NVIDIA Jetson Orin NX 16GB reference rig - 16GB unified memory, 102 GB/s aggregate bandwidth
Schematic of the Single GTX 1080 Ti (11GB) reference rig - 11GB VRAM, 484 GB/s aggregate bandwidth
Schematic of the 4x H100 80GB (320GB) reference rig - 320GB VRAM, 13400 GB/s aggregate bandwidth
Schematic of the NVIDIA DGX Station 748GB reference rig - 748GB unified memory, 8000 GB/s aggregate bandwidth
Schematic of the 8x RTX 3090 rack (192GB) reference rig - 192GB VRAM, 7489 GB/s aggregate bandwidth
Schematic of the 4x RTX 5090 (128GB) reference rig - 128GB VRAM, 7168 GB/s aggregate bandwidth
Schematic of the AMD Instinct MI300X (192GB) reference rig - 192GB VRAM, 5324 GB/s aggregate bandwidth
Schematic of the 4x RTX 4090 (96GB) reference rig - 96GB VRAM, 4032 GB/s aggregate bandwidth
Schematic of the 2x RTX 5090 (64GB) reference rig - 64GB VRAM, 3584 GB/s aggregate bandwidth
Schematic of the 2x RTX 3090 (48GB) reference rig - 48GB VRAM, 1872 GB/s aggregate bandwidth
Schematic of the Single RTX 5090 (32GB) reference rig - 32GB VRAM, 1792 GB/s aggregate bandwidth
Schematic of the RTX PRO 6000 Blackwell (96GB) reference rig - 96GB VRAM, 1792 GB/s aggregate bandwidth
Schematic of the Mac Studio M4 Ultra 192GB reference rig - 192GB unified memory, 1092 GB/s aggregate bandwidth
Schematic of the Mac Studio M4 Ultra 512GB reference rig - 512GB unified memory, 1092 GB/s aggregate bandwidth
Schematic of the Single RTX 4090 (24GB) reference rig - 24GB VRAM, 1008 GB/s aggregate bandwidth
Schematic of the MacBook Pro M5 Max 128GB reference rig - 128GB unified memory, 614 GB/s aggregate bandwidth
Schematic of the Dual EPYC 9004 + 768GB DDR5-4800 reference rig - 768GB unified memory, 460 GB/s aggregate bandwidth
Schematic of the DGX Spark 128GB unified reference rig - 128GB unified memory, 273 GB/s aggregate bandwidth
Schematic of the Ryzen AI Max+ 395 128GB reference rig - 128GB unified memory, 256 GB/s aggregate bandwidth
Schematic of the Jetson AGX Orin 64GB reference rig - 64GB unified memory, 204 GB/s aggregate bandwidth
Schematic of the Epyc + 512GB DDR4-3200 + 2x RTX 3090 reference rig - 560GB unified memory, 204 GB/s aggregate bandwidth
Schematic of the Epyc + 512GB DDR4-2400 + 2x RTX 3090 reference rig - 560GB unified memory, 153 GB/s aggregate bandwidth

22 reference configs, drawn in-house. Scroll for more.

Can you run it? - reference rigs

Rig Q8_0
NVIDIA Jetson Orin NX 16GB tight
Single GTX 1080 Ti (11GB) offload
4x H100 80GB (320GB) fast 472.4t/s
NVIDIA DGX Station 748GB fast 282.1t/s
8x RTX 3090 rack (192GB) fast 264.1t/s
4x RTX 5090 (128GB) fast 252.7t/s
AMD Instinct MI300X (192GB) fast 187.7t/s
4x RTX 4090 (96GB) fast 142.2t/s
2x RTX 5090 (64GB) fast 126.4t/s
2x RTX 3090 (48GB) fast 66.0t/s
Single RTX 5090 (32GB) fast 63.2t/s
RTX PRO 6000 Blackwell (96GB) fast 63.2t/s
Mac Studio M4 Ultra 192GB fast 42.0t/s
Mac Studio M4 Ultra 512GB fast 42.0t/s
Single RTX 4090 (24GB) fast 35.5t/s
MacBook Pro M5 Max 128GB fast 23.6t/s
Dual EPYC 9004 + 768GB DDR5-4800 ok 16.3t/s
DGX Spark 128GB unified ok 9.6t/s
Ryzen AI Max+ 395 128GB ok 9.0t/s
Jetson AGX Orin 64GB slow 7.2t/s
Epyc + 512GB DDR4-3200 + 2x RTX 3090 slow 7.2t/s
Epyc + 512GB DDR4-2400 + 2x RTX 3090 slow 5.4t/s

Fit tiers use the same will-it-run logic as the rig finder. For comfortable fits, the badge reflects decode speed: fast >=20 t/s, ok 8-20 t/s, slow <8 t/s. t/s is a bandwidth estimate, not a measured benchmark.

Download options

Q8_0 community
15.6GB dl 16.0GB min 20.0GB rec
REC RAM vs largest quant

Or run it in the cloud

No per-token API provider pricing tracked for Qwen-Image-2.1 yet. For flagship list prices, see the calculator.

See who runs Alibaba in production →

PRICE HISTORY

Inference cost over time

Data accumulates from the first daily sync - longer ranges populate over time. Prices come from OpenRouter snapshots, not a historical API.

Loading price history...