Variants and Variations both create multiple possible results. They happen at different times.

Composer Variants

Set the Composer count from 1 to 8 before sending. One message then creates that many parallel Variants.

Variants create several outputs from one send. The popover shows the total cost.

Each Variant has its own:

Render
Render job
Progress stream
Output tile
Per-image credit charge

The images share the message's prompt, mode, model, render settings, source, references, and Composition snapshot. Provider sampling can still produce different results.

The Feed keeps all Variants in one card. One failed or cancelled tile does not stop its siblings.

Use the stop control on one active tile to cancel that job. Cancel all appears when more than one job in the card remains active. Cancellation is accepted while a job is queued or generating. A job already uploading finishes instead.

The total cost is the per-image rate multiplied by the Variant count.

Feed Variations

Open a finished Render's actions and select Create variations. Then choose from 1 to 8 new images. You can also change the model and its supported output settings.

Variations starts with the original:

Prompt
Mode
Source and mask, when present
Composer reference images

The original model and render settings stay selected when both are still valid. If the settings are no longer valid, Variations uses that model's current defaults. If the original model has retired, Variations selects the current default model and its defaults.

Before generating, you can choose the model, its available settings, and a count from 1 to 8. Each Variation is a new render charged at the selected model and settings. Missing original attachments disable the action.

For an ordinary finished Render, the new submission snapshots the project's current Composition. It does not restore that Render's five-field snapshot.

For a Modify, Relight, or Effects result, Create variations routes through operation replay. It resolves the original source Render and reuses that source Render's immutable Composition snapshot instead of current project fields. See Modify, Relight, and Effects.

Variants and Variations compared

Use Composer Variants when you know before sending that you want several parallel takes. They use the model and settings currently selected in Composer.

Use Create variations after reviewing a finished Render. The resulting Variations repeat its original inputs. The popover preserves a valid original model and settings, applies current defaults when needed, and lets you change the model, settings, and count.

Interactive example

Create Variants and Variations calculator. The surrounding article includes the same guidance in static text.

This Create example calculates job counts and credits locally. Enhance and Edit take framing from their source.

This interactive calculator is a Create example. Its displayed aspect ratio applies only to Create. Enhance and Edit take framing from the source.

The calculator uses the same capability, default-setting, and pricing helpers as render submission. It shows the current settings summary, per-image cost, total cost, and one independent job for every selected image. It does not submit a render.

Static comparison: Composer Variants split one Send into the chosen number of independent jobs. Variations start later from one finished result and create a new set of jobs with the selection shown in the Create variations popover. Both charge once per new image.

Both choices create a new Feed card with independent jobs. Neither duplicates an existing output file.

Render again and Retry are different

Render again creates one new image. It preserves the original prompt, mode, and available attachments. You choose the model and its model-specific output settings. The project's current Composition is snapshotted for an ordinary new Render. For a Modify, Relight, or Effects result, Render again routes through operation replay. It resolves the original source Render and reuses that source Render's immutable Composition snapshot instead of current project fields.

Retry appears on a failed tile. It preserves the original prompt, attachments, model, and settings when that selection is still valid. Invalid settings use that model's current defaults. A retired model falls back to the current default model and its defaults.

Retry with model is the failed-tile configured retry. It lets you choose the model and its supported output settings before the new submission.

All three are charged new render submissions. The failed original is refunded separately.