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
• saved AI edit instructions for photo angles, including whether each edit is on
• 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.

AI edits in a template

Create and refine an image in an angle’s AI editor, then choose Use on future renders… to save instructions for that angle. The template captures those instructions when you save a version. The saved example shows the source project’s result; new products receive newly generated results.

Open View contents on a template version to inspect which photo angles include AI edits, their instructions and settings, and any example or reference image. Edits that are off remain saved but do not run.

Applying a template copies the instructions into the new project. Enabled instructions run when you render photo angles in the background. Preview renders skip them. Changes made in that project do not change the saved template version. Save a new template version to share revised instructions.

AI edits from another workspace are not included when you use its public template. The template details identify these unavailable edits. Linked AI styles currently use the style’s current settings, so review a fresh result if that style changes.

Create a template from approved work

1. Finish and review a representative project.
2. Open Templates.
3. Choose Save from project.
4. Choose a source project by its preview and saved setup details.
5. Review the source, name the template, and optionally choose an industry. Back lets you review the project list and return to the same source without losing your draft.
6. Choose Save template. The saved template opens when it is ready.

This uses the last scene saved in Studio. Save your latest Studio changes before starting. The source project links to the new template; later changes do not automatically update that saved version. Finished renders remain in the project rather than becoming template examples.

If the project already has a saved template, the dialog shows its name and offers View template. If the scene has not been saved completely, the dialog keeps your draft and offers Open Studio so you can finish saving it.

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.

1. Apply the template to a second prepared model.
2. Render its required views.
3. Inspect scale, framing, contact, material mapping, and product-specific exceptions. Check each included AI edit against the original render, especially when the new product has different proportions or colors.
4. 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.

Know the boundary

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