---
title: "Import screens from the screens library"
slug: "/help/demos/capture/screens-library"
last_updated: "2026-04-15T11:33:36Z"
zendesk_id: 11516281030547
zendesk_url: "https://help.walnut.io/hc/en-us/articles/11516281030547-Importing-Screens-With-the-Screens-Library"
locale: "en-us"
category: "Getting Started"
section: "Capturing & Importing Content"
product: "demos"
topic: "capture"
displayed_sidebar: "demosSidebar"
sidebar_position: 4
tags: ["blog link","insert screen","import screens","import screen","add screen"]
---

You must be an **Editor**, **Admin,** or **Account Owner** to access this feature. 🔑

[Learn more about Roles & Permissions](/help/account/users/roles-and-permissions).

## **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.

:::note

Importing existing screens can help teams move faster, reduce repetitive work, and keep shared template elements more consistent across demos.

:::

---

## **Import Screens**

To import screens, start from the template you want to import screens **into**.

1.  Open the destination template.
2.  From the template overview page, click **Import Screens** in the top-right corner.

![Screenshot showing the Import Screens button on the Walnut template overview page.](pathname:///images/4d5aff8d618e23ad.png)

The import window opens. From there:

1.  Select the template you want to import screens **from**.
2.  Choose the specific screens you want to bring into the current template.
3.  Decide whether to include existing guides and edits with those screens.

![Screenshot showing the template selection step when importing screens in Walnut.](pathname:///images/473defdaf812beb1.png)

![Screenshot showing selected screens and import options in Walnut.](pathname:///images/dfcdf42a77b02ba0.png)

---

## **Important to Know**

:::note

-   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.

:::

![Screenshot showing import options for including or excluding existing guides and edits in Walnut.](pathname:///images/34ae3522c243191e.png)

---

## **Walnut Tip**

:::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.

:::

:::note[Summary]

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.

:::