Unsloth Slashes Qwen-Image-2.1 Weight Storage in Half for Consumer GPUs
Unsloth released FP8/INT8 quants of Qwen-Image-2.1, cutting the transformer from 14.23GB to ~7GB Same-seed LPIPS vs bf16 is 0.064 (INT8) and 0.112 (FP8), with INT8 as the default shipped scheme Dynamic FP8 variant runs on 6GB VRAM via CPU offloading, under 2x slower Base Qwen-Image-2.1 is a 7B
Takeaways
- Unsloth released FP8/INT8 quants of Qwen-Image-2.1, cutting the transformer from 14.23GB to ~7GB
- Same-seed LPIPS vs bf16 is 0.064 (INT8) and 0.112 (FP8), with INT8 as the default shipped scheme
- Dynamic FP8 variant runs on 6GB VRAM via CPU offloading, under 2x slower
- Base Qwen-Image-2.1 is a 7B unified text-to-image and editing model with native RGBA and 2K output
- Supports up to 10 reference images and region edits via circles, paint, or masks
- Licensed under Qwen Research License: open weights but non-commercial use only
Unsloth has published FP8 and INT8 builds of Alibaba’s Qwen-Image-2.1 , reducing the storage required for its largest components from 31.73 GB to about 16.5 GB. The smaller weights make local generation and editing more practical on consumer GPUs, particularly when paired with CPU offloading.
Quantization stores model weights with lower-precision numbers. FP8 and INT8 use 8 bits per value instead of the 16 bits used by BF16, cutting storage and weight memory while introducing some approximation.
At publication time, Unsloth’s model repository showed more than 850,000 downloads. Hugging Face counts file fetches rather than unique users, so the figure indicates distribution activity rather than adoption by 850,000 people.
Two components get the 8-bit treatment
The release provides quantized replacements for the pipeline’s two largest components: the diffusion transformer, or DiT, and the Qwen3-VL text encoder. Both use the safetensors format, which avoids executable pickle payloads during checkpoint loading.
| Component | 8-bit size | BF16 size | Reduction |
|---|---|---|---|
| INT8 transformer | 7.26 GB | 14.23 GB | 49% |
| FP8 transformer | 7.12 GB | 14.23 GB | 50% |
| FP8 text encoder | 9.39 GB | 17.50 GB | 46% |
The FP8 transformer and text encoder total 16.51 GB, compared with 31.73 GB for their BF16 equivalents. These figures cover checkpoint storage for the listed components. They exclude runtime activations, caches, other pipeline files, and framework overhead.
Quality trade-offs, in numbers
Unsloth compared same-seed outputs with the BF16 reference using LPIPS, a metric that measures perceptual differences between images. Lower scores indicate closer outputs. The company reports 0.064 for INT8 and 0.112 for FP8 , which led it to select INT8 as the default in Unsloth Desktop.
LPIPS measures visual similarity rather than prompt adherence, text accuracy, or editing precision, so application-specific testing remains necessary. Unsloth also offers a Dynamic FP8 variant that reportedly runs with 6 GB of VRAM through CPU offloading, with a slowdown below 2x in its tests.
Reporting is indexed from AlphaSignal. Rights remain with the original publisher and cited sources.
Read original report
