Skip to Help content

Render actions, retries, history, cancellation, and refunds

Reuse finished Renders, replay work, manage history, and understand charges.

Updated Aug 11, 2026 · 6 min read

Enter a search term.

Every generated image is a Render. Feed and Gallery organize the same project results for different tasks, and their finished-image actions use the same labels, descriptions, order, and availability.

Render action outcomes

Menu groupActionDescriptionOutcome
DownloadDownloadSave this image to your device.No render submission
Download 4KCreate or reuse a free 4K upscale, then download it.No render submission
Work with imageEditStart an Edit with this image as the source.Prepares the Composer. Charged only after Send
EnhanceStart an Enhance with this image as the source.Prepares the Composer. Charged only after Send
AttachAttach this image as a reference for your next render.Prepares the Composer. Charged only after Send
Create againRender againRender this prompt again with a model and settings you choose.Opens choices before submission
Create variationsCreate more takes with the model, settings, and count you choose.Opens choices before submission
Image operationsModifyMake a focused change while keeping the architecture and visual direction.Submits one Enhance render immediately
RelightChange the lighting while keeping the design, materials, and composition.Submits one Enhance render immediately
EffectsAdd a restrained atmospheric or photographic effect.Submits one Enhance render immediately
ManageUse as compositionUse selected settings from this render in the project Composition.Opens choices before submission
DeleteMove this render to Gallery Trash.No render submission
Edit, Enhance, and Attach prepare the Composer. Image operations submit immediately. Other actions either stay local or open a choice first.

The Feed follows one study. Each message appears as one card with its Variant tiles. Active, failed, cancelled, and finished tiles stay grouped with the message that created them.

Open any finished Feed Render to review every finished image already loaded in the Feed. Arrow buttons, Arrow keys, swipes, and thumbnails follow visible Feed order. The strip shows global position, such as 7 / 24. Cmd/Ctrl+Arrow jumps to the first image in the next or previous loaded card. Navigation stops at the first and last image and does not load older messages.

The Gallery collects finished Renders from every study in the project. You can filter by study, mode, model, and quality, sort the loaded results, and open any image in its lightbox. The Gallery Quality filter is a compatibility filter across old and new rows; it does not mean Gemini exposes a native Quality setting.

Select the model and settings summary on a Feed card to open Generation details. This is a Feed-card affordance, not an action-menu item. It can show:

  • Source and Composer reference images
  • Model, output settings, image count, and total credits
  • Slash-command changes applied by the message
  • The five-field Composition snapshot used for the Render

That snapshot explains an older Render even after project settings change.

The Feed card also shows input images as small thumbnails. Open one from the card rail or Generation details. Its viewer offers Download, Edit, Enhance, and Attach. Edit and Enhance prepare the Composer without sending. Attach adds the image as Composer reference context and keeps the viewer open.

Requested size is the provider target. Output size is the measured finished file. Native Quality, Resolution, Aspect, and Requested size appear only when stored versioned settings validate for that model and mode. Older rows may omit them while retaining safe facts such as Model, Output size, Images, and Cost.

Render clarification history

A completed render clarification appears in a separate thin row immediately before its Render card. Its read more view contains the initial prompt and ordered questions and answers. The final submitted prompt stays on the Render card.

Clear, skipped, failed, and abandoned checks create no clarification history. Render again, Create variations, Retry, and image operations do not copy an older clarification into the new request. Deleting every Render tile in the message also removes its clarification row from the Feed.

Finished Render actions

The tile menu groups the same actions as the lightbox while keeping each root row compact.

The toolbar and tile menu use this order:

  1. Download is a split control. Select its main action to save the original. Open the chevron for Download 4K, which creates or reuses a free Lanczos upscale and downloads it.
  2. Edit, Enhance, and Attach prepare the Composer. Edit and Enhance set this Render as the source. Attach adds it as reference context.
  3. Render again and Create variations open model and supported settings choices before a new submission. Create variations also lets you choose a count.
  4. Modify, Relight, and Effects open preset menus. Selecting a preset immediately submits one Enhance Render.
  5. The ellipsis contains Use as composition and Delete.

Tile menus keep root rows to an icon and label. Hover or focus an action to read its short explanation and open the relevant Help guide. Modify, Relight, and Effects keep that guidance inside their opened preset menus. Edit uses its orchid mode tint, while Enhance uses ember.

Edit and Enhance do not charge when selected. A charge starts only if you send the prepared Composer draft. Attach does not submit a Render.

Image operations use the source Render's model, supported native settings, image, and immutable Composition snapshot. They do not use current project settings. They charge the normal per-image rate for that resolved selection, and failures refund. Results retain the Enhance badge and show Category · Preset with a short public summary in the Feed.

The Modify, Relight, and Effects reference lists every preset, explains illustrative previews and scene requirements, and covers operation replay.

If credits block an operation, verified checkout Continue restores its source, category, and preset without submitting. Select the preset again when ready. The same no-auto-submit rule applies to restored Render again and Create variations controls.

Use as composition

Select Use as composition to generate a new five-field Composition from the finished Render. You choose which fields replace project settings. The dedicated Use as composition guide explains field selection, cost, Preset versions, wait stages, and recovery.

Delete, Trash, and Restore

Delete always opens a confirmation. Confirming moves the Render to Gallery Trash; it does not hard-delete the file. Cancellation or a failed request keeps the Render and focus. A lightbox closes only after deletion succeeds.

Open the Gallery Trash filter and select Restore to return the Render to the Gallery.

Retry and replay

A transient provider error is retried once by the worker before a tile becomes a final failure. Content-policy, invalid-image, and invalid-size errors are not repeated automatically.

After a final failure:

  • Retry keeps the failed job's prompt, mode, attachments, model, and settings when that selection remains valid. Invalid settings use that model's current defaults. A retired model falls back to the current default and its defaults.
  • Retry with model keeps the prompt, mode, and attachments while you choose a model and supported native settings.

Render again and Create variations keep the original prompt, mode, and available attachments. For an ordinary Render, their new submission snapshots the project's current Composition. For an image-operation Render, they also preserve valid operation identity and replay the server-owned preset instruction.

Create offers Aspect. Enhance and Edit preserve source proportions and do not offer Aspect. If an original source, mask, or reference file is unavailable, replay is disabled. Pick or upload a current image instead.

Cancellation and refunds

Credits are charged when a Render message is submitted. Each output tile has its own job and charged amount.

You can stop one job while it is queued or generating. Cancel all requests cancellation for every active sibling in the card. Cancellation can be too late: once a job is uploading, CAD Scene lets it reach a final state to avoid an incomplete stored result.

An accepted cancellation refunds that job. A failed job also refunds its charged credits. Refunds are idempotent, so overlapping worker and cancellation cleanup cannot refund twice. Successful siblings remain charged; failed or successfully cancelled siblings are refunded independently.