QW

Qwen Image Edit Rapid AIO

QwenGGUF by Phil2SatUpdated 2025-11-07
Download on Hugging Face
Parameters7.62B
Context125K
Layers28
Architectureqwen2vl
Smallest quant4.7 GB
Quick answer

Qwen Image Edit Rapid AIO needs about 5.7 GB of memory at Q4_K_M (a 4.7 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 72 quants, from 4.7 GB (Q4_K_M) to 40.9 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 1.9 GB.

Qwen Image Edit Rapid AIO – 7.62B vision‑enabled model

Qwen Image Edit Rapid AIO is a 7.62B parameter model that supports vision tasks. It is built on the qwen2vl architecture and includes accelerators, VAE, and CLIP for fast image editing and text‑to‑image generation. The model is released under the apache‑2.0 license.

Good at

  • Fast image editing with up to 4 input images
  • Text‑to‑image generation
  • Supports both NSFW and SFW workflows

Limits

  • Requires separate VAE and text_encoder files
  • No native vision support in GGUF alone
  • Large memory footprint for higher precision quants

Best for

  • Rapid prototyping of image edits
  • Generating images from text prompts
  • Fine‑tuning with custom LORAs

Who it’s for. Developers and researchers who need a quick, versatile image editing model. The model is suitable for users who can supply the required VAE and text_encoder files and are comfortable managing separate components.

Quants & memory

QuantFileEst. memoryvs VRAMResultDownload
Q4_K_M4.7 GB 5.7 GB
Fits Get file →
Q2_K7.4 GB 8.4 GB
Too big Get file →
Q2_K7.4 GB 8.4 GB
Too big Get file →
Q2_K7.4 GB 8.4 GB
Too big Get file →
Q2_K7.4 GB 8.4 GB
Too big Get file →
Q2_K7.4 GB 8.4 GB
Too big Get file →
Q8_08.1 GB 9.1 GB
Too big Get file →
Q3_K_S9.3 GB 10.3 GB
Too big Get file →
Q3_K_S9.3 GB 10.3 GB
Too big Get file →
Q3_K_S9.3 GB 10.3 GB
Too big Get file →
Q3_K_S9.3 GB 10.3 GB
Too big Get file →
Q3_K_S9.3 GB 10.3 GB
Too big Get file →
Q3_K_M10.0 GB 11.0 GB
Too big Get file →
Q3_K_M10.0 GB 11.0 GB
Too big Get file →
Q3_K_M10.0 GB 11.0 GB
Too big Get file →
Q3_K_M10.0 GB 11.0 GB
Too big Get file →
Q3_K_M10.0 GB 11.0 GB
Too big Get file →
Q4_012.2 GB 13.2 GB
Too big Get file →
Q4_012.2 GB 13.2 GB
Too big Get file →
Q4_012.2 GB 13.2 GB
Too big Get file →
Q4_012.2 GB 13.2 GB
Too big Get file →
Q4_012.2 GB 13.2 GB
Too big Get file →
Q4_K_S12.5 GB 13.5 GB
Too big Get file →
Q4_K_S12.5 GB 13.5 GB
Too big Get file →
Q4_K_S12.5 GB 13.5 GB
Too big Get file →
Q4_K_S12.5 GB 13.5 GB
Too big Get file →
Q4_K_S12.5 GB 13.5 GB
Too big Get file →
Q4_113.2 GB 14.1 GB
Too big Get file →
Q4_113.2 GB 14.1 GB
Too big Get file →
Q4_113.2 GB 14.1 GB
Too big Get file →
Q4_113.2 GB 14.1 GB
Too big Get file →
Q4_113.2 GB 14.1 GB
Too big Get file →
Q4_K_M13.3 GB 14.3 GB
Too big Get file →
Q4_K_M13.3 GB 14.3 GB
Too big Get file →
Q4_K_M13.3 GB 14.3 GB
Too big Get file →
Q4_K_M13.3 GB 14.3 GB
Too big Get file →
Q4_K_M13.3 GB 14.3 GB
Too big Get file →
Q5_K_S14.4 GB 15.4 GB
Too big Get file →
Q5_K_S14.4 GB 15.4 GB
Too big Get file →
Q5_K_S14.4 GB 15.4 GB
Too big Get file →
Q5_K_S14.4 GB 15.4 GB
Too big Get file →
Q5_K_S14.4 GB 15.4 GB
Too big Get file →
Q5_014.7 GB 15.6 GB
Too big Get file →
Q5_014.7 GB 15.6 GB
Too big Get file →
Q5_014.7 GB 15.6 GB
Too big Get file →
Q5_014.7 GB 15.6 GB
Too big Get file →
Q5_014.7 GB 15.6 GB
Too big Get file →
Q5_K_M15.1 GB 16.1 GB
Too big Get file →
Q5_K_M15.1 GB 16.1 GB
Too big Get file →
Q5_K_M15.1 GB 16.1 GB
Too big Get file →
Q5_K_M15.1 GB 16.1 GB
Too big Get file →
Q5_K_M15.1 GB 16.1 GB
Too big Get file →
Q5_115.6 GB 16.6 GB
Too big Get file →
Q5_115.6 GB 16.6 GB
Too big Get file →
Q5_115.6 GB 16.6 GB
Too big Get file →
Q5_115.6 GB 16.6 GB
Too big Get file →
Q5_115.6 GB 16.6 GB
Too big Get file →
Q6_K17.0 GB 18.0 GB
Too big Get file →
Q6_K17.0 GB 18.0 GB
Too big Get file →
Q6_K17.0 GB 18.0 GB
Too big Get file →
Q6_K17.0 GB 18.0 GB
Too big Get file →
Q6_K17.0 GB 18.0 GB
Too big Get file →
Q8_021.8 GB 22.7 GB
Too big Get file →
Q8_021.8 GB 22.7 GB
Too big Get file →
Q8_021.8 GB 22.7 GB
Too big Get file →
Q8_021.8 GB 22.7 GB
Too big Get file →
Q8_021.8 GB 22.7 GB
Too big Get file →
F1640.9 GB 41.8 GB
Too big Get file →
F1640.9 GB 41.8 GB
Too big Get file →
F1640.9 GB 41.8 GB
Too big Get file →
F1640.9 GB 41.8 GB
Too big Get file →
F1640.9 GB 41.8 GB
Too big Get file →

For 8 GB VRAM use Q4_K_M (4.68 GB, ~5.7 GB memory). For 12 GB VRAM use Q8_0 (8.1 GB, ~9.1 GB memory). For 24 GB VRAM use F16 (40.86 GB, ~41.8 GB memory). Estimates are approximate.

What GPU do you need for Qwen Image Edit Rapid AIO?

These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.

  • 4 GB VRAM: no quant fits at an 8K context.
  • 6 GB VRAM: the best quant that fits is Q4_K_M (4.7 GB file, about 5.7 GB in use).
  • 8 GB VRAM: the best quant that fits is Q4_K_M (4.7 GB file, about 5.7 GB in use).
  • 12 GB VRAM: the best quant that fits is Q3_K_M (10.0 GB file, about 11.0 GB in use).
  • 16 GB VRAM: the best quant that fits is Q5_0 (14.7 GB file, about 15.6 GB in use).
  • 24 GB VRAM: the best quant that fits is Q8_0 (21.8 GB file, about 22.7 GB in use).
  • 32 GB VRAM: the best quant that fits is Q8_0 (21.8 GB file, about 22.7 GB in use).
  • 48 GB VRAM: the best quant that fits is F16 (40.9 GB file, about 41.8 GB in use).

Which Qwen Image Edit Rapid AIO quant should you choose?

Q4_K_M is the usual starting point for Qwen Image Edit Rapid AIO: it balances file size and quality well. Here it is a 4.7 GB file.

The Q8_0 file is 8.1 GB, about 1.7 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.

New to quant names? Read GGUF quantization explained.

Specifications

Architecture from the GGUF header

Architectureqwen2vl
Parameters7.62B
Layers28
Trained context128,000 tokens
KV cache (fp16)56 KB per token

Source

Quantized byPhil2Sat
FamilyQwen
Licenseapache-2.0
Downloads (HF)26,969
Last updated2025-11-07

Frequently asked questions about Qwen Image Edit Rapid AIO

How much VRAM does Qwen Image Edit Rapid AIO need?

About 5.7 GB at Q4_K_M with an 8K context window. That is the 4.7 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.

Can I run Qwen Image Edit Rapid AIO on an 8 GB GPU?

Yes, with Q4_K_M: the 4.7 GB file needs about 5.7 GB at 8K context. Larger quants in this repository do not fit in 8 GB.

What is the file size of Qwen Image Edit Rapid AIO GGUF?

It depends on the quant: Q4_K_M is 4.7 GB, Q2_K is 7.4 GB, Q2_K is 7.4 GB, Q2_K is 7.4 GB, Q2_K is 7.4 GB, Q2_K is 7.4 GB and 66 more.

What context length does Qwen Image Edit Rapid AIO support?

The GGUF header lists a trained context length of 128,000 tokens (125K). The KV cache grows with the context you use: about 0.5 GB at 8K and 1.9 GB at 32K.

Where can I download Qwen Image Edit Rapid AIO GGUF?

The files are on Hugging Face in the Phil2Sat/Qwen-Image-Edit-Rapid-AIO-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.

What license does Qwen Image Edit Rapid AIO use?

Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.

Can I run Qwen Image Edit Rapid AIO on 8 GB VRAM?

Yes, using the Q4_K_M quant which is 4.68 GB and requires about 5.7 GB of VRAM at 8k context.

Do I need additional files to use this model?

Yes, the model requires a separate VAE and text_encoder mmproj file to function correctly.

Is the model suitable for NSFW content?

Both NSFW and SFW versions are available; choose the version that matches your use case.

Other GGUFs of Qwen-Image-Edit-Rapid-AIO

Similar models

Browse all →

More from Phil2Sat

All by Phil2Sat →

More Qwen models

All Qwen →

Other small models

All small models →