SDXL Turbo & Lightning Guide

Configure SDXL Turbo and Lightning models for 1–4 step generation

A practical guide to the distilled SDXL Turbo and Lightning models — the optimal step counts (1, 2, 4, 8), the low CFG scale they require (1.0–2.5), compatible schedulers, and the prompt style that suits near-instant generation. It runs free in your browser on Gera Tools, with nothing uploaded.

Last updated Source: Gera Tools

Why do Turbo and Lightning need so few steps?

They are distilled models — trained to reproduce in 1 to 8 steps what the base SDXL takes 25 or more steps to do. The denoising trajectory is compressed, so running extra steps wastes time and can even degrade the image.

SDXL Turbo & Lightning

SDXL Turbo and the SDXL Lightning checkpoints are distilled versions of Stable Diffusion XL, trained to produce a finished image in just 1 to 8 steps instead of the usual 25–40. They make near-real-time generation possible — but only if you configure them correctly, because their step count, CFG, and scheduler all differ sharply from the base model.

How distillation works

Standard diffusion models learn to denoise step by step, with each step being a small incremental correction. Distillation trains a student model to reproduce the output of many teacher steps in far fewer of its own. Two different distillation approaches produced Turbo and Lightning:

SDXL Turbo uses adversarial diffusion distillation — it was trained not just to minimise the step count but to produce images that a discriminator cannot distinguish from real photographs. This is why it achieves usable output in a single step.

SDXL Lightning (from ByteDance) uses progressive adversarial distillation, producing variants optimised for 2, 4, and 8 steps. Each checkpoint is trained specifically for its target step count, which is why you should not run the 4-step model at 8 steps or the 8-step model at 2 steps.

Both approaches bake the prompt guidance into the distillation rather than applying it at inference time through CFG scaling. This is why high CFG destroys distilled models — you are double-applying guidance that was already baked in.

Configuration table

ModelStepsCFG scaleRecommended scheduler
SDXL Turbo10.0–1.0Euler Ancestral
SDXL Lightning 2-step21.0–2.0Euler, sgm_uniform
SDXL Lightning 4-step41.0–2.0Euler, sgm_uniform
SDXL Lightning 8-step81.5–2.5DPM++ SDE, sgm_uniform

If your results look oversaturated, washed out, or blurry, CFG is almost always the cause — lower it toward 1.0 first before adjusting anything else.

What distilled models trade away

At their target step counts, Turbo and Lightning are remarkably close to base SDXL quality for most subjects. The areas where the base model retains an edge:

  • Very fine texture detail — fabric weave, skin pore detail, hair strand separation — benefits from the refinement that additional steps provide
  • Complex multi-subject compositions — with only a handful of denoising steps, the model has less opportunity to resolve spatial relationships between multiple objects
  • Very long, detailed prompts — fewer steps means less time to integrate all prompt tokens into the output

For rapid exploration and prototyping, distilled models are faster than any other approach short of generating at very low resolution. The common workflow is to use Lightning for idea exploration at speed, identify the compositions and styles worth developing, then re-generate those specific images with base SDXL for final quality.

Tips and examples

  • Low CFG is non-negotiable. If your Turbo or Lightning images look fried or over-saturated, your CFG is too high — drop it toward 1.
  • Match steps to the checkpoint. Use the 4-step Lightning model at 4 steps, not 20. The variant name tells you the target.
  • Draft fast, finalize full. Use Lightning to explore compositions instantly, then re-render the winner with base SDXL for maximum detail.
  • Keep prompts concise. With so few steps, long elaborate prompts have less room to resolve — clear, direct prompts perform best.
  • LoRAs still work with distilled models but may need lower strength values (0.4–0.7) compared to base SDXL runs.