Controlling Generation with Resolution, Seeds, Steps, Cfg, Samplers, and Denoise

The KSampler and Empty Latent Image nodes determine much of the behavior of a generation. Their settings control the starting noise, output dimensions, number of images, duration of denoising, prompt adherence, sampling algorithm, scheduling strategy, and degree of transformation.

These controls do not operate independently. A model family may be optimized for a particular resolution, a Lightning checkpoint may need far fewer steps, and a fixed seed is only reproducible when the other settings remain unchanged.

Resolution and batch size are configured in the Empty Latent Image node.

For SDXL, the recommended starting size is 1024 by 1024. The image does not have to be square, but SDXL is treated as optimized around that scale. For Stable Diffusion 1.5 or earlier, the recommended size is 512 by 512. Lower dimensions can be used to accelerate an experiment; the ControlNet example uses 768 instead of 1024 to reduce generation time.

Batch size determines how many images are produced in one queue. A batch size of two creates two images. Later, a batch of four is used with an image chooser so that only the preferred candidate proceeds to upscaling.

The seed identifies the starting pattern of random noise. Randomize produces a different starting point for each generation. Fixed preserves the seed. When the seed and every other setting remain identical, the same image is generated again. This is essential when a workflow is paused after the first image and resumed later for upscaling; without a fixed seed, the second queue would generate and upscale a different image.

Steps determine how many rounds of noise removal occur. Too few steps leave the image noisy or incomplete. Increasing the count improves the result only up to a point. Beyond approximately 50 to 100 steps, the image may stop improving and can acquire noise or artifacts because little useful noise remains to remove.

A conventional setup can use 20 steps. A Lightning checkpoint needs far fewer: approximately five to eight steps, with some models capable of a usable image in as few as two. Using 20 steps merely because it is a familiar default ignores the checkpoint's design.

CFG controls how strongly the sampler follows the prompt. A very low value, such as 1, gives the generation more freedom and may not follow the prompt closely. A high value, such as 15, follows the wording very literally. Excessive literalness can create strange results. A value around 7 or 8 is a reliable general starting point.

Sampler name selects the algorithm that removes noise. Euler is a common and fast option. DPM++ 2M and DPM++ 2M SDE are suitable when quality is the priority. Scheduler adds another subtle variation to the sampling process. Karras and Exponential are suggested for higher-quality output, although the visible differences can be subtle and should be tested for the intended use case.

Denoise determines how much of the starting latent content is replaced. In text-to-image, the input is random noise, so denoise is set to 1.0 to remove 100 percent of that starting noise. In image-to-image, the same parameter becomes the main control over similarity to the uploaded image.

Prompt writing alone does not determine the output. A strong prompt can still fail if the resolution is inappropriate for the model, the CFG is too high, the step count is mismatched to a Lightning checkpoint, or the seed changes during a multi-stage comparison.

Understanding each parameter also makes experimentation interpretable. A fixed seed holds the starting noise constant. A change in CFG can then be recognized as a change in prompt adherence rather than a change caused by a new random starting point.

Use the following baseline for an SDXL text-to-image test:

Resolution: 1024 by 1024

Batch size: 1

Seed control: Randomize during exploration; Fixed when an exact image must be regenerated

Steps: 20 for the ordinary example; approximately 5 to 8 for the Lightning example

CFG: 7 or 8

Sampler: Euler for speed, or DPM++ 2M / DPM++ 2M SDE when testing for quality

Scheduler: Karras or Exponential for a quality-oriented test

Denoise: 1.0 for text-to-image from an empty latent

To compare a parameter reliably, fix the seed and leave the remaining settings unchanged. Then alter the setting being evaluated. The workflow's caching behavior will restart execution from the node whose value changed rather than recomputing every unchanged stage.

For rapid exploration, reduce the image dimensions or use a fast sampler. For a Lightning checkpoint, reduce the step count before concluding that the model is slow. For prompt adherence problems, adjust CFG rather than immediately rewriting the entire graph.

Higher CFG is not automatically better. Strong adherence can make the generation unnaturally literal.

More steps are not automatically better. Excessive steps consume computation without guaranteed improvement and may introduce artifacts.

Random seeds produce variety but prevent exact continuation of a staged workflow. Fixed seeds improve reproducibility but reduce variation until the seed is changed.

Lower resolution improves speed but produces less initial detail. Higher resolution is more appropriate for the model's intended scale but increases generation time.

Sampler and scheduler differences can be subtle. No combination is universally superior, so test them against the actual image and model.

Treat resolution, seed, steps, CFG, sampler, scheduler, batch size, and denoise as coordinated controls. Match them to the checkpoint and the workflow goal rather than maximizing every value.