> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/flatredball/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/flatredball/glue-reference/entities/glue-reference-export-entity.md).

# Export Entity

### Introduction

Screens and Entities can be exported through the FlatRedBall Editor to be imported later. For importing, see the [Importing Entity page](https://docs.flatredball.com/flatredball/glue-reference/entities/glue-reference-import-entity.md).

### Exporting a Screen/Entity

Once you have a Screen/Entity that you are ready to export, you can:

1. Right-click on the Screen/Entity and select **Export Screen** or **Export Entity**

   <figure><img src="https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2FZZUQogsmApJ6kUATW1MN%2F12_09%2044%2007.png?alt=media&amp;token=db9d3b5d-c94a-499a-b45a-0c653be132ae" alt=""><figcaption><p>Export Entity right click option</p></figcaption></figure>
2. Navigate to the folder where you would like to save the exported element and click OK
3. An Explorer window appears showing you your exported file

### What does an Exported Screen/Entity contain?

Exported Screens and Entities create .scrz (Screen zip) or .entz (Entity zip) files, respectively. These files are standard zip files which can be unzipped with any unzipper. Exported Screens and Entities contain the following:

* An XML file containing the information set in Glue
* A C# code file containing custom code
* All referenced files (such as .pngs) and any files that the referenced files include, recursively


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.flatredball.com/flatredball/glue-reference/entities/glue-reference-export-entity.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
