Managing outputs
The gallery to the right of the viewport – favorite, download, delete, and find your renders later.
Every render lands in the gallery to the right of the viewport. The gallery is the working set for that shot's renders: hover for actions, click to enlarge, favorite to keep, download to save, delete when done.
Watch
What it does
A typical project produces dozens of renders per shot during iteration. Without organization, finding the one good render from yesterday becomes a slow scroll. The gallery's actions are how you keep what's worth keeping and clear what isn't.
How to use it
Each render in the gallery shows a thumbnail. Hover for the action row:
Heart (favorite) – marks the render. Favoriting flags it so you can find it later.
Download – saves a full-resolution copy to your machine.
Edit (pencil) – opens Edit images on this render.
Delete – removes from the gallery. Confirms before removing.
To use a render as the first frame of a video, select it and switch the visualizer dropdown from Image to Video. The selected render auto-populates as the first frame. See First and last frame.
Click a thumbnail to open the larger view.
Cross-shot persistence
The gallery is per-shot. Switching shots reveals a different gallery; the previous shot's renders are still there, just not visible until you switch back.
To browse renders across shots, use the Publish flow – its content selector lets you pick shots from any scene in the project and review them in one place. Otherwise, use favorites consistently and the per-shot galleries stay manageable.
Downloading
Downloads are full-resolution. Filenames are generic (image (#).jpg, scene-reference.jpg, canny-image.png, depth-image.png) – rename in your file system if you need scene / shot / model context preserved on disk.
Downloads happen one render at a time; there's no multi-select or batch-download flow today.
The gallery isn't a permanent archive. Past several hundred renders, older results may roll off the visible history. Anything you want for the long term should be downloaded.
Deleting renders
Hover the thumbnail, click delete. Confirms once. Gone. Bulk delete isn't exposed today – delete renders one at a time.
Deleted renders don't refund credits. The credit was spent at generate time.
Common patterns
Favorite as you go. A render you like, favorite immediately. Doing it later is harder than doing it now.
Delete obvious failures. A render that's clearly wrong (model artifacts, the cop-car problem) – delete it. Reduces gallery noise on the next pass.
Download milestones. When a render is the new "best of" for a shot, download it. The gallery is short-term memory; your file system is long-term memory.
Limits and known issues
Renders are project-scoped. A render generated in Project A doesn't appear in Project B's gallery, even if you used the same scene template. Re-render or download and re-upload as needed.
Audio tracks on video renders aren't extractable separately. Download a video, the audio comes baked in. To remix, do it in your editor.
Related
Last updated
Was this helpful?