FLUX.1 schnell needs about 8.2 GB of memory at Q4_0 (a 6.9 GB file) with an 8K context window, so it fits on a 12 GB GPU. This repository has 5 quants, from 4.1 GB (Q2_K) to 12.8 GB (Q8_0).
FLUX.1 schnell – 11.9B parameter text‑to‑image model in GGUF format
FLUX.1 schnell is a 11.9 billion parameter text‑to‑image model released under apache‑2.0. The GGUF quantized files enable running on GPUs with 4–6 GB VRAM. The model is part of the Flux family and was quantized by leejet.
Good at
- Fast inference on modest GPUs
- High‑quality image generation
- Supports 8 k context tokens
Limits
- No vision support in this quantized version
- Requires 4 GB or more VRAM for Q2_K
- No explicit language support listed
Best for
- Rapid prototyping of image generation
- Low‑budget GPU inference
- Educational demos
Who it’s for. Developers and researchers who need a lightweight, open‑source text‑to‑image model that can run on consumer GPUs. The model is suitable for experimentation and small‑scale deployment.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q2_K | 4.1 GB | 5.1 GB | Fits | Get file → | |
| Q3_K | 5.3 GB | 6.5 GB | Fits | Get file → | |
| Q4_0 | 6.9 GB | 8.2 GB | Too big | Get file → | |
| Q4_K | 6.9 GB | 8.2 GB | Too big | Get file → | |
| Q8_0 | 12.8 GB | 14.8 GB | Too big | Get file → |
For 4 GB VRAM, use Q2_K (4.11 GB file, ~5.1 GB memory). For 6 GB VRAM, Q3_K (5.31 GB file, ~6.5 GB memory) is recommended. If more VRAM is available, Q4_0 or Q4_K (6.88 GB file, ~8.2 GB memory) provide better quality.
What GPU do you need for FLUX.1 schnell?
These figures add the file size, an fp16 KV cache at an 8K context window 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 Q2_K (4.1 GB file, about 5.1 GB in use).
- 8 GB VRAM: the best quant that fits is Q3_K (5.3 GB file, about 6.5 GB in use).
- 12 GB VRAM: the best quant that fits is Q4_0 (6.9 GB file, about 8.2 GB in use).
- 16 GB VRAM: the best quant that fits is Q8_0 (12.8 GB file, about 14.8 GB in use).
Which FLUX.1 schnell quant should you choose?
Q4_0 (6.9 GB) is the middle option in this repository. The usual sweet spot between file size and quality, and the quant most people start with.
If memory is tight, the smallest file is Q2_K at 4.1 GB, with the quality trade-offs that come with fewer bits. Use it only when memory is very tight. Expect a clear drop in quality, which is usually worse on small models and easier to live with on large ones.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about FLUX.1 schnell
How much VRAM does FLUX.1 schnell need?
About 8.2 GB at Q4_0 with an 8K context window. That is the 6.9 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 FLUX.1 schnell on an 8 GB GPU?
Yes, with Q3_K: the 5.3 GB file needs about 6.5 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of FLUX.1 schnell GGUF?
It depends on the quant: Q2_K is 4.1 GB, Q3_K is 5.3 GB, Q4_0 is 6.9 GB, Q4_K is 6.9 GB, Q8_0 is 12.8 GB.
Where can I download FLUX.1 schnell GGUF?
The files are on Hugging Face in the leejet/FLUX.1-schnell-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 FLUX.1 schnell 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 FLUX.1 schnell on a GPU with 4 GB VRAM?
Yes, the Q2_K quantized file is 4.11 GB and requires about 5.1 GB of VRAM at 8 k context.
Is the model licensed for commercial use?
The model is licensed under apache‑2.0, which allows commercial use with attribution.
Does the model support multiple languages?
No language information is provided; the model is primarily for text‑to‑image generation.