Field versions and preset versions
Understand one-field history, five-field Preset history, and restore behavior.
Updated Aug 10, 2026 · 3 min read
Enter a search term.
Field versions and Preset versions record different scopes. They can exist at the same time.
Version scope
Field version
One selected field
- Choose checkpoint
- Go back
- New restore entry
The other four fields stay unchanged.
Preset version
All five fields
- Choose snapshot
- Apply version
- Current Composition
Save as version only if this restored state needs a new checkpoint.
Field versions
A field version records one field in one project. Style, Scene, Lighting, Materials, and Entourage each have a separate timeline.
Open a field and select Versions. History can identify these sources:
- Generated from words
- Generated from reference images
- Generated from the Project reference image
- Applied from a saved Preset
- Applied from a built-in Preset
- Manual save
- Restored from an earlier field version
Some entries also retain the source prompt or image previews. This makes the history useful for tracing why the text changed.
Every successful manual field Save records a version. Generated values and Preset applications also record their result.
Current state and empty history
The field editor always shows the project's current value. The version timeline shows recorded checkpoints only.
No versions yet does not mean the current field is lost. It means no checkpoint has been recorded for that field. Select Save current as version when the current text differs from the latest checkpoint.
Go back to a field version
Select Go back on an earlier entry. CAD Scene copies that text into the current field and appends a new restore entry.
The old entries remain unchanged. Future renders use the restored text. Past renders retain the settings snapshot they were created with.
Preset versions
A Preset version is one immutable snapshot of all five fields under a saved Preset.
Use Save as preset to create a named Preset and version 1. When that Preset is active, use Save as version to append the current Composition.
Open Browse versions to compare any Preset version with the project's current five fields. Applying a Preset version copies all five saved values into the project and keeps that saved Preset active.
Applying an earlier Preset version does not erase newer versions. It also does not create another Preset version by itself. Save a new version if you want the restored state recorded as the latest checkpoint.
Built-in Presets are read-only. They have no Preset version timeline.
Use as composition
Use as composition can append the complete generated Composition to an active saved Preset. This remains a five-field Preset version even when only some generated fields replace the project settings.
See the Use as composition guide for the full procedure, current cost, wait stages, and retry behavior.
