Check my GPU →

Can the RTX 5060 Ti 16 GB run Qwen-Image-Edit (2511)?

Timed on my own card, not estimated: 27.2 seconds per 1024x1024 image with the Q4_K_M file, peaking at 15.9 GB.

Image model · 20B16 GB GDDR7 · 128-bit · 448 GB/s · BlackwellData 2026-10-01
Tight
Only just.

Take Q3_K_M (9.9 GB). In use it comes to about 12.9 GB, with 3.1 GB left over on 16 GB. Quality: noticeable loss of detail. For better quality, Q4_K_M (13.2 GB) also runs, with about 0.2 GB spilling into system RAM - a little slower, still practical.

Best fileQ3_K_M
File size9.9 GB
VRAM needed~12.9 GB
System RAM32 GB+
Memory map · RTX 5060 Ti 16 GB12.9 GB / 16 GB
08 GB16 GB
Weights Q3_K_M · 9.9 GBWorking memory · 2.2 GBReserve · 0.8 GBFree · 3.1 GB

Also try the FP8 file (20.5 GB) on this GPU. It does not fit entirely, but a current ComfyUI streams the overflow from RAM and native 8-bit files often beat a small GGUF that does fit. Dynamic VRAM →

01My measurements

LabelSetupResultPeak VRAMDateSource
measuredqwen-image-edit-2511-Q4_K_M.gguf · 1024x1024 · 4 steps
Image editing with the Lightning 4-step LoRA (Qwen-Image-Edit-2511-Lightning-4steps-V1.0-bf16), cfg 1, euler/simple, ModelSamplingAuraFlow 3.1, CFGNorm, index_timestep_zero referen
27.19 s / image15.9 GB2026-10-11

02What to download

PartFileFolderSize
Modelqwen-image-edit-2511-Q3_K_M.gguf
Q3_K_M · unsloth/Qwen-Image-Edit-2511-GGUF
models/unet9.9 GBDownload →
Text encoderqwen_2.5_vl_7b_fp8_scaled.safetensors
Qwen2.5-VL 7B FP8 · Comfy-Org/Qwen-Image_ComfyUI
models/text_encoders9.4 GBDownload →
VAEqwen_image_vae.safetensors
Qwen-Image VAE · Comfy-Org/Qwen-Image_ComfyUI
models/vae0.3 GBDownload →
Total download · keep about the same free on disk19.6 GB

Alternatives: Qwen2.5-VL 7B BF16 (16.6 GB). Sizes from Hugging Face, 2026-10-01.

Free ComfyUI workflow, tested on my RTX 5060 Ti: GGUF Q4_K_M + 4-step LoRA workflow (.json). Drag the file into ComfyUI. All workflows →

03Every Qwen-Image-Edit file on 16 GB

FileSizeNeededOn this cardQualityDownload
16-bit
SAFETENSORS · Comfy-Org
40.9 GB43.9 GB27.9 GB too bigthe original weightsHugging Face →
FP8
SAFETENSORS · Comfy-Org
20.5 GB23.5 GB7.5 GB too bigpractically identical to the originalHugging Face →
Q8_0
GGUF · unsloth
21.8 GB24.8 GB8.8 GB too bigpractically identical to the originalHugging Face →
Q6_K
GGUF · unsloth
16.9 GB19.9 GB3.9 GB too bigvery close to the originalHugging Face →
Q5_K_M
GGUF · unsloth
15.0 GB18.0 GB2.0 GB too bigclose; small differences in fine detailHugging Face →
Q4_K_M
GGUF · unsloth
13.2 GB16.2 GBspills 0.2 GBgood; some loss in fine detail and textHugging Face →
Q3_K_M ←
GGUF · unsloth
9.9 GB12.9 GBfits · 3.1 GB sparenoticeable loss of detailHugging Face →
Q2_K
GGUF · unsloth
7.5 GB10.5 GBfits · 5.5 GB spareheavy loss; a last resortHugging Face →

“Needed” adds 2.2 GB of working memory for Qwen-Image-Edit and a 0.8 GB reserve. Sizes 2026-10-01.

04Questions

How much VRAM does Qwen-Image-Edit need?

Around 10.5 GB with the smallest file (Q2_K) and 23.5 GB with an 8-bit file (FP8). The full 16-bit file needs about 43.9 GB.

Which Qwen-Image-Edit file should I download for the RTX 5060 Ti 16 GB?

Q3_K_M (9.9 GB) from unsloth/Qwen-Image-Edit-2511-GGUF. Load it with Unet Loader (GGUF) from the ComfyUI-GGUF node pack.

FP8 or Q8_0 for Qwen-Image-Edit on the RTX 5060 Ti 16 GB?

FP8 (20.5 GB): the RTX 5060 Ti 16 GB computes it natively, while Q8_0 (21.8 GB) is unpacked on the fly.

How much do I need to download for Qwen-Image-Edit on the RTX 5060 Ti 16 GB?

19.6 GB: qwen-image-edit-2511-Q3_K_M.gguf, qwen_2.5_vl_7b_fp8_scaled.safetensors, qwen_image_vae.safetensors.