Skip to content

Flux.1 Schnell Low-VRAM Settings for ComfyUI

Step-by-step memory tuning for Flux.1 Schnell (8 GB–12 GB) so 8 GB and 12 GB RTX cards render cleanly without CUDA Out of Memory errors.

Updated Oct 17, 2026 · 1 min read

At a glanceGuide
Target Model
Flux.1 Schnell
Baseline VRAM
8 GB–12 GB
Quantization Options
FP8 or GGUF Q4/Q8
VAE Strategy
VAE Decode (Tiled) 512px tiles

Fitting Flux.1 Schnell into 8 GB–12 GB VRAM

Standard full-precision weights for Flux.1 Schnell target 8 GB–12 GB. On 8 GB cards like the RTX 3060 Ti, RTX 4060, or laptop GPUs, loading uncompressed weights alongside the text encoder can trigger a CUDA Out of Memory error.

Switching to quantized weights (FP8 or GGUF Q4/Q8) via ComfyUI-GGUF or native FP8 checkpoints cuts the model footprint roughly in half while keeping prompt adherence intact.

Checklist to prevent OOM spikes at the end of sampling

  1. Replace standard `VAE Decode` with VAE Decode (Tiled) so the final latent-to-pixel conversion runs in 512×512 blocks.
  2. Use `t5xxl_fp8_e4m3fn.safetensors` or a Q4 GGUF text encoder when running dual/triple CLIP architectures.
  3. Keep batch size at 1 and use Queue Count in ComfyUI Studio when generating multiple variations. Grab the latest Windows build from /download.

FAQs

Why does Flux.1 Schnell crash at 95% or 100% in ComfyUI?

A crash right as sampling finishes is almost always the VAE decode step spiking VRAM. Swap in the `VAE Decode (Tiled)` node to solve it immediately.

Does --lowvram slow down Flux.1 Schnell on Windows?

ComfyUI automatically enables smart weight offloading when VRAM is tight; only pass `--lowvram` if a heavy custom node bypasses ComfyUI's native memory manager.

Run on your hardware. Free forever.

The full ComfyUI engine: open source, fast, extensible, and yours to run however you want. Download the desktop app and open this workflow on your own machine.

Sofa split between tweed and snow-leopard fabric, an image edit made in ComfyUI