Preserve a setup as a template

A template preserves the work behind an accepted result. Instead of documenting the lighting, scene, and camera views in a brief, save the project state that produced them and apply it again.

What a template can carry

A template can preserve supported project state including:

scene and backdrop
light rig and light settings
camera behavior and output intent
saved image angles
saved video clips
the relationship between the product and the scene

The product model remains a separate reusable asset. Applying the template stages another prepared model inside the saved setup.

Create a template from approved work

Finish and review a representative project.
Open Templates.
Choose Create Template.
Name the setup for its intended use.
Select the source project.
Save the template.

Name the visual system, not the first product that used it. Studio White / Core PDP is more useful than Samba Test when the template will serve a category.

Verify it with another product

Do not treat template creation as proof that the setup generalizes.

Apply the template to a second prepared model.
Render its required views.
Inspect scale, framing, contact, material mapping, and product-specific exceptions.
Adjust the source setup when the same issue would affect future products.

This is where the template earns its value.

Update and version

When the source project changes, update the template only after reviewing the new direction. Template versions protect existing work from silent changes and make a production run reproducible.

Where available:

create a new version for an intentional visual change
pin a project or run to the version it was approved against
lock a shared template to protect the accepted state
document the reason for a version change in the name or team convention

Apply a template

Choose Create Project from a template when you want to enter Studio with that setup.
Use Quick Render when the setup is already approved and should render its saved views across prepared models.
Use a Render automation node when an ongoing workflow should apply the template from a folder, event, or manual run.
Use the API when another system should select the template or version programmatically.

A template preserves shared direction. It cannot guarantee that every product will frame, contact, or respond identically. Products with different proportions, modeled options, pivots, or material structures still need review.

Repeat the setup with Quick Render or work with templates in the asset library