> For the complete documentation index, see [llms.txt](https://docs.thunkable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thunkable.com/app-design/screen/save-and-reuse-screens.md).

# Save and Reuse Screens

## Overview

Streamline your workflow and maximize your efficiency across diverse projects with the Thunkable save screen feature, which allows you to save a screen from one app project and reuse it in another app project!&#x20;

{% hint style="info" %}
This feature may only be available for Creators on certain Thunkable plans. Please refer to our pricing page for more information: [Thunkable pricing](https://thunkable.com/pricing).
{% endhint %}

## Video Tutorial

### How to Save and Reuse Thunkable Screens

In this tutorial, we’ll show you how to streamline your workflow and maximize your efficiency across diverse projects by saving a screen from one app project and reusing it in another!

{% embed url="<https://youtu.be/-gIH6tV7Yfs>" %}

## Save Screen

1. Select the screen in the Designer.
2. Click the vertical ellipsis at the top of the screen's properties pane.
3. Click **Save Screen**.\
   ![](/files/mITeNH3WC3AezcxisCca)
4. Give your screen a descriptive name.&#x20;
5. Click **Save**.

## Add Screen to Another Project

1. Open the project in which you'd like to add the saved screen.
2. Click the upside-down arrow at the top of the Designer's component tree.<br>

   <div align="left"><figure><img src="/files/fUp4CfFyCzHYkjZ46GIK" alt="" width="563"><figcaption></figcaption></figure></div>
3. Click **Add From Saved Screens**.
4. Select the screen you want to add.
5. Click **Copy**.<br>

   ![](/files/-M1DR8RXZK6x_jcdGnGF)

### Errors&#x20;

When a saved screen is added to a new project, you may notice some errors in the blocks that you’ll need to address. This is because the app you have added the screen to doesn’t necessarily have the same features. For example, the blocks may navigate the user to a screen that doesn’t exist in the new app. Another example of an error that would need to be addressed is if the screen had a data viewer, but the data source wasn’t connected to this project.

## View All Saved Screens

1. Navigate to your Projects Page.
2. Click **Saved Screens** in the left sidebar.&#x20;

   <div align="left"><figure><img src="/files/2wnKnNg9znAlYfUC5XD1" alt="" width="310"><figcaption></figcaption></figure></div>
3. On your Saved Screens page, you can view your screens, rename them, and delete screens you no longer need.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.thunkable.com/app-design/screen/save-and-reuse-screens.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
