Stable Cascade Configuration Guide

Optimize Stable Cascade stage A/B settings for quality and speed

Guide to Stable Cascade (Würstchen v3) settings. Tune steps and guidance for the Stage C prior and Stage B decoder, pick a latent resolution and balance quality versus speed for your available VRAM. It runs free in your browser on Gera Tools, with nothing uploaded.

Last updated Source: Gera Tools

What are the stages in Stable Cascade?

Stable Cascade has three stages. Stage C is the text-conditioned prior that does most of the creative work in a highly compressed latent space. Stage B decodes that into a larger latent, and Stage A is a lightweight VAE that produces the final pixels. You mainly tune Stage C and Stage B.

Stable Cascade configuration

Stable Cascade (the Würstchen v3 architecture) splits generation across three stages working in a heavily compressed latent space. Stage C is the text-conditioned prior doing the creative work, Stage B decodes it into a larger latent, and Stage A is a tiny VAE producing pixels. Most of your tuning happens on Stage C and Stage B, and this guide picks sensible values for your quality target and VRAM.

Why Stable Cascade is different

Most diffusion models (SD 1.5, SDXL, Flux) operate in a latent space compressed 8x relative to pixel resolution. Stable Cascade uses a 42x-compressed latent for Stage C. This is the core architectural difference: the prior operates on far smaller tensors, which means:

  • Fewer steps needed. Stage C produces strong results in 20 steps rather than the 30–50 typical of SDXL.
  • Lower CFG needed. The compressed latent is very prompt-sensitive; CFG of 4 is approximately equivalent to CFG 7 in a standard 8x model.
  • Lower VRAM at high resolution. Because Stage C tensors are tiny, you can generate at 1024×1024 with less VRAM than an equivalent SDXL run.
TargetStage C stepsStage C CFGStage B stepsStage B CFG
Draft (fast)104.041.1
Balanced204.0101.1
Maximum quality30–404.0–4.5101.1

Stage B step count changes almost nothing beyond 10. All additional quality investment should go into Stage C step count.

VRAM requirements (approximate, bf16)

ConfigurationVRAM
Stage C only (lite variant)~4 GB
Full pipeline 1024×1024~8 GB
Full pipeline 1536×1536~12–14 GB

The lite Stage C variant trades some quality for a dramatically smaller footprint. If you are on 6–8 GB, use the lite prior and full Stage B.

Applying the config in ComfyUI

In a ComfyUI Stable Cascade workflow:

  • StableCascade_StageC_VAEDecode node controls Stage C. Set steps and cfg here.
  • StableCascade_StageB_VAEDecode node controls Stage B. Use 10 steps, CFG 1.1.
  • KSampler for Stage C: sampler euler_ancestral, scheduler simple or karras.
  • Load the Stage C prior and Stage B decoder as separate model checkpoints.

Tips for quality improvement

  • Add detail to the positive prompt. Unlike SDXL, Stable Cascade responds well to explicit lighting and material descriptors in the positive prompt rather than relying on a style embedding.
  • Avoid high CFG. Above CFG 5 in Stage C, colour saturation spikes and fine details start to burn out. Stay at 4–4.5.
  • Use varied seeds. Stage C generation has notable seed variance; run 4–6 seeds and pick the best composition before spending steps on Stage B.
  • bf16 throughout. Running any stage in fp32 doubles VRAM and provides no visible quality benefit for this architecture.