Text to image
The basic graph: a prompt in, a picture out. Seven nodes.
In plain words
Text to image starts from an empty latent full of noise and lets the model remove the noise step by step, guided by your prompt. Every other kind of graph is a variation of this one.
<!-- diagram: Load Checkpoint (MODEL, CLIP, VAE) → CLIP Text Encode positive and negative → KSampler ← Empty Latent Image; KSampler → VAE Decode (with VAE from the checkpoint) → Save Image -->The graph
- Load Checkpoint: the model. Outputs
MODEL,CLIP,VAE. - CLIP Text Encode (Prompt) twice: the prompt and the negative prompt, both fed by
CLIP. - Empty Latent Image: the blank, with
width,height,batch_size. - KSampler:
model,positive,negative,latent_imagein;steps,cfg,seed,sampler_name,scheduler,denoise1.0. - VAE Decode: the sampler's
LATENTand the checkpoint'sVAEin,IMAGEout. - Save Image: the picture goes to the
outputfolder.
For families with separate loaders step 1 becomes three nodes (Load Diffusion Model, Load CLIP or DualCLIPLoader, Load VAE), step 3 uses the family's empty latent node, and Flux dev adds FluxGuidance. The shape stays the same.
Values to start with
SD 1.5: 512×512, 25 steps, cfg 7, euler or dpmpp_2m with karras. SDXL: 1024×1024, 25 steps, cfg 6. Flux dev: 1024×1024, 20 steps, cfg 1 with guidance 3.5. See Model families for the rest.
Typical mistakes
- positive and negative swapped; a missing Save Image; a size far from the family's;
denoiseleft below 1.
How the app helps
The lesson A first picture from text builds exactly this graph with you, step by step, and checks each link.