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

# Save and reuse brand styles

Brand styles let you save an aesthetic configuration and apply it to future signatures.

## Availability

Custom brand styles require Pro or Business.

## Style Limits

| Plan     | Saved Style Limit |
| -------- | ----------------- |
| Free     | 1                 |
| Pro      | 10                |
| Business | 50                |

## Save a Style

1. Open **Builder**.
2. Configure the template, colors, font, logo, banner, and element styles.
3. Click **Save style**.
4. Enter a style name.
5. Optionally set it as the default style.
6. Save.

## Apply a Saved Style

1. Open **Templates**.
2. Find the style under **My Styles**.
3. Click **Use this style**.
4. Create the signature using the saved visual configuration.

## Edit or Delete a Saved Style

1. Open **Templates**.
2. Use the star icon to set or remove the default style.
3. Use the delete icon to remove a style.
4. Existing signatures are not changed when a saved style is deleted.


---

# 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.subscripta.app/builder/save-and-reuse-brand-styles.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.