> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/platform/build-forms/design/reuse-styles-and-elements/assets.md).

# Assets

Assets are form elements configured with certain sets of styles and properties. They can then be reused throughout your form.

**Assets** are form elements configured with certain sets of styles and properties. These custom-configured elements can then be reused throughout your form.

For example, you may configure different `Next` and `Back` button styles and want to use them interchangeably in your form. You would then create two assets in your theme, one for each style.

#### How to Create Assets

You can save assets to your form's associated theme for quick access.

1. Start with an element and make desired changes to its styles and properties.
2. Click the `+ Save as Asset` button that appears in the left panel.
3. View your saved asset by selecting the red number badge in grid view or switching to list view.
4. Publish your form to save the new asset to your theme.

![](https://640450274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHAVngDAEk3s8Bw7P6Ntz%2Fuploads%2F64prvVyQEc30TgwlfKpz%2Fdocs_assets-create.gif?alt=media\&token=4939d872-5aa7-4f7d-a469-2bd816d280c6)

#### How to Update Assets

You can update assets in a form or theme. Updates will apply to all assets in all forms using the same theme.

To update in a form:

1. Make desired changes to the asset's styles and properties.
2. Select the ↻`Update Asset` button in the left panel OR the individual style <mark style="background-color:blue;">Override Menu</mark> in the right panel.
3. Publish the form to finalize your asset update.

![](https://640450274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHAVngDAEk3s8Bw7P6Ntz%2Fuploads%2FLhYnLwisrDBC6TtoqKPA%2Fdocs_assets.gif?alt=media\&token=d550a004-fd20-4a23-81ec-73f04df8d1d1)

#### How to Manage Assets

You can manage assets by using the `Overflow Menu` found in the left panel (open via `Right Click`) or in their associated theme. The theme will give you an overview of all your assets.

![](https://640450274-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHAVngDAEk3s8Bw7P6Ntz%2Fuploads%2FCTlG7gdeTb7UkgOlIFll%2Fdocs_theme.png?alt=media\&token=e662c5d6-cd5e-43bc-8373-dc7aa5c8023d)


---

# 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.feathery.io/platform/build-forms/design/reuse-styles-and-elements/assets.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.