Can the RTX 2060 6 GB run FLUX.1 [dev]?
Nothing fits entirely, but Q3_K_S (5.2 GB) overflows by only about 1.5 GB. ComfyUI keeps that part in system RAM automatically: slower than a full fit, but usable.
Worth trying on this GPU: with an up-to-date ComfyUI, Dynamic VRAM (on by default for NVIDIA since March 2026) streams whatever does not fit from system RAM, and ComfyUI's own start-up message recommends native FP8/INT8 files over GGUF, saying they “will be faster even if they are larger than your memory”. So before settling for a heavily compressed GGUF, try the native FP8 file (11.9 GB). The file recommended above is the best one that fits entirely — the safe choice on older ComfyUI versions, AMD and Intel. Comfy blog: Dynamic VRAM →
01What to download
| Part | File | Folder | Size | |
|---|---|---|---|---|
| Model | flux1-dev-Q3_K_S.gguf Q3_K_S · city96/FLUX.1-dev-gguf | models/unet | 5.2 GB | Download → |
| Text encoder | t5xxl_fp8_e4m3fn.safetensors T5-XXL FP8 · comfyanonymous/flux_text_encoders | models/text_encoders | 4.9 GB | Download → |
| Text encoder | clip_l.safetensors CLIP-L · comfyanonymous/flux_text_encoders | models/text_encoders | 0.2 GB | Download → |
| VAE | ae.safetensors FLUX.1 VAE (ae) · Comfy-Org/Lumina_Image_2.0_Repackaged | models/vae | 0.3 GB | Download → |
| Total download · keep about the same free on disk | 10.7 GB | |||
Alternatives: T5-XXL FP16 (9.8 GB). The 16-bit text encoder is a little more faithful; the smaller one is chosen here because it loads faster and needs less RAM. Sizes read from Hugging Face (2026-09-25). “Download” links start the file directly; the file name links are the same files the official ComfyUI workflows use.
System RAM: 32 GB or more. ComfyUI keeps the model file, the text encoder and the VAE in system RAM and moves them to the GPU as needed. With this set of files that is about 10.7 GB, plus roughly 6 GB for Windows, ComfyUI and a browser: 16.7 GB in total. With less RAM it still runs, but Windows starts swapping to disk and loading gets very slow. calculated
02Every FLUX.1 dev file on 6 GB
| File | Size | Needed | On this card | Quality | Download |
|---|---|---|---|---|---|
| 16-bit SAFETENSORS · black-forest-labs | 23.8 GB | 26.1 GB | 20.1 GB too big | the original weights | Hugging Face → |
| Q8_0 GGUF · city96 | 12.7 GB | 15.0 GB | 9.0 GB too big | practically identical to the original | Hugging Face → |
| FP8 SAFETENSORS · Kijai | 11.9 GB | 14.2 GB | 8.2 GB too big | practically identical to the original | Hugging Face → |
| Q6_K GGUF · city96 | 9.9 GB | 12.2 GB | 6.2 GB too big | very close to the original | Hugging Face → |
| Q5_K_S GGUF · city96 | 8.3 GB | 10.6 GB | 4.6 GB too big | close; small differences in fine detail | Hugging Face → |
| Q4_K_S GGUF · city96 | 6.8 GB | 9.1 GB | 3.1 GB too big | good; some loss in fine detail and text | Hugging Face → |
| Q3_K_S ← GGUF · city96 | 5.2 GB | 7.5 GB | spills 1.5 GB | noticeable loss of detail | Hugging Face → |
| Q2_K GGUF · city96 | 4.0 GB | 6.3 GB | spills 0.3 GB | heavy loss; a last resort | Hugging Face → |
Sizes from the Hugging Face file listing, read 2026-09-25. “Needed” = file + 1.5 GB working memory for this model + 0.8 GB kept free for the system.
03The text encoder
T5-XXL: 9.8 GB as 16-bit, 4.9 GB as FP8, 2.9 GB as GGUF Q4_K_M (plus CLIP-L (0.25 GB)). ComfyUI encodes the prompt first and can push the encoder out of VRAM before sampling, so it does not have to fit together with the model. On 6 GB the FP8 encoder fits on its own, so prompt encoding stays fast.
04About this GPU
The RTX 2060 6 GB (Turing) has no FP8 compute. FP8 files still load and save memory, but ComfyUI converts them back before the maths, so there is no speed gain — Q8_0 GGUF is the closer-to-original 8-bit choice. ComfyUI can compute INT8 files natively on NVIDIA, which is worth a try where a model offers one.
RTX 2060 6 GB: 6 GB GDDR6 · 192-bit · 336 GB/s · Turing. Everything that runs on the RTX 2060 6 GB →
05What more VRAM would change
With 16 GB you could run FLUX.1 dev at 8-bit or better (Q8_0, 12.7 GB) with no offloading: for example on the RTX 5080 16 GB, RTX 5070 Ti 16 GB, RTX 5060 Ti 16 GB.
What changes from the RTX 2060 6 GB to the RTX 3060 12 GB → · What changes from the RTX 2060 6 GB to the RTX 5060 Ti 16 GB →
06Measured and reported results
Nobody has sent measured numbers for this pair yet. If you run FLUX.1 dev on a RTX 2060 6 GB, send your time per image and peak VRAM and it will appear here, credited.
07Questions
How much VRAM does FLUX.1 dev need?
Around 6.3 GB with the smallest file (Q2_K) and 14.2 GB with an 8-bit file (FP8), counting working memory and a small system reserve. The full 16-bit file needs about 26.1 GB.
Which FLUX.1 dev file should I download for the RTX 2060 6 GB?
Q3_K_S (5.2 GB) from city96/FLUX.1-dev-gguf. Load it with Unet Loader (GGUF) from the ComfyUI-GGUF node pack.
Is FP8 faster than GGUF on the RTX 2060 6 GB?
No. This GPU has no FP8 compute, so ComfyUI converts FP8 weights back before the maths. FP8 only saves memory here; Q8_0 GGUF is the closer-to-original 8-bit pick.
How much do I need to download for FLUX.1 dev on the RTX 2060 6 GB?
About 10.7 GB for the model file, text encoder and VAE listed on this page, and the same again free on disk. With a 6 GB card, 32 GB of system RAM or more is recommended.