Qwen Image 2.1

GGUF & COMFYUI

Qwen Image 2.1 GGUF files and ComfyUI setup

GGUF quantizations shrink the Qwen-Image-2.1 transformer from about 13 GiB to between 2 and 7 GiB so it fits on consumer graphics cards. Here is what the files are, how the quant levels compare in size, and how to load one in ComfyUI.

What a GGUF contains
The diffusion transformer only
Also required
Qwen3-VL 8B text encoder and the 2.1 VAE
Q6_K file size
About 5.5 to 5.9 GiB by repository
Published by
Community quantizers, not the Qwen team

What a Qwen Image 2.1 GGUF is

GGUF is a single-file container for quantized model weights. For Qwen-Image-2.1 it holds the denoising transformer at reduced precision. It does not include the text encoder or the VAE, so those are downloaded separately.

The Qwen team publishes full-precision weights; GGUF conversions are made by community members such as unsloth, leejet and Abiray on Hugging Face. They are derivatives of the original model and their repositories declare the same Qwen Research License.

GGUF quantization sizes compared

File sizes from the unsloth/Qwen-Image-2.1-GGUF repository, read on 4 October 2026. Other repositories differ by a few hundred megabytes for the same level because they keep different layers at higher precision.

Qwen-Image-2.1 GGUF files (unsloth)
Quant levelFile sizeNotes
Q2_K2.30 GiBSmallest file; fine detail and lettering may suffer
Q3_K_S / Q3_K_M2.54 / 2.95 GiBVery low memory budgets
Q4_K_S / Q4_K_M3.64 / 3.91 GiBCommon starting point on mid-range cards
Q5_K_S / Q5_K_M4.19 / 5.02 GiBMiddle ground
Q6_K5.84 GiBPopular high-precision choice
Q8_07.12 GiBNearest to full precision among the quantized files
F1613.25 GiBUnquantized 16-bit, same size class as the BF16 original

The same Q6_K level is 5.59 GiB in leejet/Qwen-Image-2.1-GGUF and 5.47 GiB in Abiray/Qwen-Image-2.1-GGUF. Whichever repository you choose, add the text encoder to your memory budget: the INT8 Qwen3-VL 8B encoder in the ComfyUI repack is about 9.35 GB and the W4A8 variant about 6.3 GB.

Which quant to choose: Q4_K_M, Q6_K or Q8_0

There is no official quality table for these files, so treat the following as community guidance rather than benchmarks. Higher numbers keep more bits per weight and stay closer to the original model; lower numbers trade fidelity for memory.

  • Q6_K is the most searched level for a reason: it is about 1.3 GiB smaller than Q8_0 while staying in the high-precision group. One quantizer's model card calls it the high-quality sweet spot and suggests 10 to 12 GB of VRAM.
  • Q4_K_M is the usual choice when VRAM is limited; the same card suggests 6 to 8 GB.
  • Q8_0 is the safest pick if it fits, because it changes the weights least.
  • Q2 and Q3 files load on very small cards, but community guides warn that fine detail, anatomy, typography and prompt adherence can suffer.

If you have the memory for it, the INT8 file from Comfy-Org (about 7.3 GB) runs in the stock ComfyUI templates with no custom node at all.

Set up a Qwen Image 2.1 GGUF in ComfyUI

  1. Update ComfyUI. Qwen-Image-2.1 support relies on recent core nodes; the documentation notes that missing nodes usually mean an outdated build.
  2. Install the ComfyUI-GGUF custom node by city96 through ComfyUI Manager, then restart.
  3. Download one .gguf file, for example the Q6_K, and place it in ComfyUI/models/unet (ComfyUI/models/diffusion_models also works).
  4. Download a Qwen3-VL 8B text encoder from Comfy-Org/Qwen-Image-2.1, such as qwen3vl_8b_int8_convrot.safetensors, into ComfyUI/models/text_encoders.
  5. Download qwen_image_2.1_vae_bf16.safetensors into ComfyUI/models/vae.
  6. Open a GGUF workflow (several GGUF repositories include one), or take the official Qwen-Image-2.1 text-to-image template and swap its diffusion model loader for the Unet Loader (GGUF) node pointing at your file.
  7. Queue a prompt. Start with the template defaults before changing anything.
ComfyUI template defaults for Qwen-Image-2.1
SettingValueNote
Steps25The published pipeline uses about 40 to 50; raise steps only if detail fails to resolve
CFG1Negative prompts have no effect at CFG 1; CFG 2 follows dense prompts more closely
Sampler / schedulereuler / simpleSame for all three official templates
Resolution1.0 MP is about 1024 x 1024Set about 4.0 MP for native 2048 x 2048

Running a GGUF without ComfyUI

GGUF files are not tied to ComfyUI. The unsloth model card documents running them with stable-diffusion.cpp, passing the GGUF as the diffusion model together with the VAE and a GGUF build of the Qwen3-VL 8B text encoder.

stable-diffusion.cpp example from the unsloth model card
sd-cli --diffusion-model qwen-image-2.1-Q4_K_M.gguf \
  --vae qwen_image_2.1_vae_bf16.safetensors \
  --llm Qwen3-VL-8B-Instruct-UD-Q4_K_XL.gguf \
  -p "a cartoon sloth mascot waving, flat vector illustration" \
  --steps 20 --cfg-scale 6.0 --sampling-method euler -W 1024 -H 1024 \
  -o out.png

Before you install anything

A working GGUF setup still means 10 GB or more of downloads, a custom node and some troubleshooting. If you only want to see how Qwen Image 2.1 responds to your prompt, generate in this studio first. This studio uses a hosted API rather than your hardware, at 1 credit per image.

qwenimage21.pro is an independently operated workspace. It is not affiliated with or endorsed by Alibaba or the Qwen team, and it does not host or redistribute model weights.

Sources

FROM READING TO MAKING

See the model before you set up ComfyUI

Run your Qwen Image 2.1 prompts in the browser for 1 credit per image, and keep the local install for when you know you need it.

Generate an image

QUESTIONS AND ANSWERS

Frequently asked questions

What is the Qwen Image 2.1 Q6_K GGUF?

It is a 6-bit quantized copy of the Qwen-Image-2.1 diffusion transformer in GGUF format. Depending on the repository it is about 5.5 to 5.9 GiB, compared with roughly 13 GiB for the 16-bit file.

Do I need a text encoder and VAE with the GGUF?

Yes. A GGUF holds only the diffusion model. You also need a Qwen3-VL 8B text encoder and the qwen_image_2.1_vae_bf16.safetensors VAE, both available in the Comfy-Org/Qwen-Image-2.1 repository.

Where do GGUF files go in ComfyUI?

Place the .gguf in ComfyUI/models/unet or ComfyUI/models/diffusion_models and load it with the Unet Loader (GGUF) node from the ComfyUI-GGUF custom node. Text encoders go in models/text_encoders and the VAE in models/vae.

Are Qwen Image 2.1 GGUF files official?

No. They are community quantizations of the official weights. The Qwen team publishes the full Diffusers-format model, and Comfy-Org publishes BF16 and INT8 files for ComfyUI.

Can I use a Qwen Image 2.1 GGUF commercially?

Quantized files are derivatives of the original model, and their repositories carry the same Qwen Research License, which limits use to research and evaluation unless you obtain a commercial license from the Qwen team. This is not legal advice.

How many steps and what CFG should I use?

The official ComfyUI templates use 25 steps, CFG 1, the euler sampler and the simple scheduler. The published Diffusers pipeline uses about 40 to 50 steps.