Naming

Name render outputs without confusing managed work and delivery copies

Last updated: 2026-10-27

Overview

The Output tab's naming settings apply to pipeline render output and its supported destination copies. Render history, sequence frame copies, saved Shots and explicit Export dialogs have their own file choices. Changing a pattern does not rename existing work or every file inside a render folder.

Output Location Structure

Render Folder (Working Directory)

Keep a managed render folder intact: it contains the recipe, history images, metadata and associated assets as well as the finished image. Do not reorganize its internal files to make a delivery folder. Use Exporting Images for a chosen image copy and Storage and Backup for editable work.

Custom Output Directory (Optional)

In Output, choose Default (app output folder), Custom Folder... or Same as Input as appropriate to the task. A custom copy does not replace the managed render's working folder. Use the folder picker for a real writable location; filename tokens are not directory-template tokens. Check the result folder after the render: a failed optional copy can leave the managed result available without the expected delivery copy.

The active Project controls its output root. Settings > Storage shows the resolved global/project locations; changing a naming pattern does not move existing renders between them.

Naming Patterns

Choose File Naming Pattern and inspect Preview. The preview uses sample values (including a sample model/seed/date); it is an illustration, not a reserved future filename. The selected image extension is added automatically.

Available Presets

Preset Pattern or behavior
Auto (Original + Settings) {original}_{template}_{model}_s{seed}
Original Filename Source stem with the selected output extension.
Template + Timestamp {template}_{timestamp}
Custom Pattern Your pattern using the tokens below.

Token Reference

Token Value in pipeline render filenames
{original} Input filename without extension.
{template} Template display name, cleaned for a filename.
{model} Short model name.
{seed} Resolved seed.
{timestamp} Local date/time: YYYYMMDD_HHMMSS.
{date} YYYYMMDD.
{time} HHMMSS.
{index} Padded frame index when supplied; 001 for an ordinary still.

For example, {original}_{date}_s{seed} illustrates a dated source/seed filename. Use only supported tokens. Invalid patterns can fall back to Auto; spaces and unsupported filename characters are removed. Do not put slashes in a pattern to create folders. Check a small run's actual output before a large job.

Sequence Handling

The Output card exposes Index Padding and Start Index under Advanced when sequence input is selected. These are not universal controls for every sequence/export writer. In particular, the normal sequence's completed-frame copies currently preserve the source stem when Original Filename is chosen; otherwise they use frame_ plus a four-digit frame index. Custom token patterns, padding and Start Index do not govern those copied frame names. Do not rely on those fields to renumber a delivery.

For delivery renaming, Exporting Sequences explains the Settings > Render > Rename exported files to sequential names dependency. By default, the export dialog keeps file names/stems regardless of its numbering checkbox. With global renaming enabled, Preserve numbering keeps frame indices; otherwise packing starts at 0000. Choosing Original Filename also requires unique input stems: equal stems with different extensions can target the same copied output name. Use separate destinations for different jobs and inspect frame counts/gaps before handing files to an editor.

Conflict Resolution

Open Advanced > If File Already Exists for pipeline naming/copy behavior:

  • Auto-rename (add hash) keeps the existing file and adds a short hash to the new filename. Expect a suffix such as -a1b2c3, not a sequential version count.
  • Overwrite existing file replaces the target. Back it up first if it matters.
  • Skip (don't save) retains the existing file. It does not necessarily skip rendering, and the old file must not be mistaken for newly written pixels.

These settings do not control every later writer. Sequence frame copies and explicit Export destinations have their own behavior. Prefer a fresh delivery folder/name for each version rather than deleting previous files to prevent renaming.

Troubleshooting

If a copy is missing, inspect the render's own output, the resolved destination, write permissions and the reported error. If a name differs from the preview, check the actual input/template/model, token validity, selected extension and conflict setting. For sequence numbers, use the sequence export options rather than assuming still-render tokens apply.

See Output to choose a delivery path and Rendering and Recovery before resubmitting work after an uncertain result.

Esc
Searching...
No results found.
Type to search the documentation
↑↓ Navigate ↵ Select Esc Close

We use cookies for analytics to understand how visitors use our site. Privacy Policy