> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/gum/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/gum/gum-tool/importing-elements.md).
# Importing Elements
## Introduction
Gum supports importing elements into your project, making it easier to reuse existing work. Elements can be imported from your project's folder structure, from a different project on disk, or from projects located on the internet.
{% hint style="info" %}
Importing from projects requires Gum February 2026 or newer.
{% endhint %}
## Importing Elements in Project Subfolder
Files which are already added to a subfolder of your project can be directly imported. To do this:
1. Save a Screen or Component to your project's Screens or Components folder, or a contained subfolder
2. Right click on your Screens or Components folder and select the Import item
3. Select the component in the list, or click Browse... to locate a component
4. Click the Import button
## Importing from Project (.gumj/.gumx)
Gum supports importing one or more elements from an existing Gum project (.gumj or .gumx). When importing elements, Gum also imports:
* Elements referenced by instances or through inheritance
* Referenced behaviors
* Referenced files, such as .png or .ganx (Gum Animation Xml)
This option is useful if you would like to import a set of components, such as a restyled set of Forms controls.
To import from a project:
1. Click the Content -> Import -> .gumx... menu item (it opens both .gumj and .gumx projects)
2. Select either Local File or URL depending on the location of the project file
3. Browser or enter the location of the project
4. Select the desired objects to import. You can click entire folders to select all contained objects. Note that dependencies (such as behaviors) are automatically checked.
5. Click the Import button
### Importing Standard Elements
An imported Standard element replaces the Standard of the same name in your project entirely, including its animations. Your project's own values, variables, categories, and animations on that Standard are gone after the import. The **Skip Existing** choice for elements that already exist applies only to components, screens, and behaviors, never to Standards.
When a selected component or screen uses a Standard that differs from yours, Gum always imports that Standard with it. Its check box is disabled, and hovering over it shows which elements use it.
{% hint style="warning" %}
Avoid editing Standard elements in a project you plan to import into. Put your customizations in components instead.
{% endhint %}
---
# 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/gum/gum-tool/importing-elements.md?ask=&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.
