You must be an Editor, Admin, or Account Owner to access this feature. 🔑
Overview
Importing screens from an existing template is a fast way to build new demo experiences without starting from scratch.
This is especially useful when your team already has strong screens in use across other templates and wants to reuse them while keeping edits, structure, and storytelling more consistent.
In This Guide:
This guide walks through how to import screens from another template and what to review before completing the import.
- How to import screens from another template
- What gets included during import in Important to Know
- A practical naming tip for keeping templates organized
Import Screens
To import screens, start from the template you want to import screens into.
- Open the destination template.
- From the template overview page, click Import Screens in the top-right corner.
The import window opens. From there:
- Select the template you want to import screens from.
- Choose the specific screens you want to bring into the current template.
- Decide whether to include existing guides and edits with those screens.
Important to Know
- By default, Walnut imports all edits already applied to the selected screen, including text changes, images, variables, smart objects, and other screen-level edits.
- If you do not want guides or edits included, uncheck the relevant import options before completing the import.
- There is no limit to how many screens you can import in one workflow.
- You can import screens from multiple templates as needed.
- Once imported, the new screens are added to the bottom of the destination template and are immediately available for editing, reordering, and linking.
Walnut Tip
Best practice: Name screens clearly before reusing them across templates. Strong screen names make it much easier to identify the right content during import and keep larger template libraries organized over time.
Importing screens is one of the fastest ways to reuse high-value template content in Walnut. It helps teams build more efficiently, keep edits consistent, and extend strong screens across multiple demo experiences.