> For the complete documentation index, see [llms.txt](https://docs.santacruzsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.santacruzsoftware.com/bannersui/core-concepts/branding-and-output.md).

# Branding and Output

Understand how brand resources, media, validation, and output work in BannersUI.

BannersUI combines approved brand resources, controlled media, and validation checks. Together, they help packages and jobs stay consistent and ready for production.

***

### Brandkits

A brandkit is a collection of approved colors and fonts. Designers use brandkits to keep packages aligned with brand rules. Users can use those resources only when the package exposes them.

Brandkits can include named colors, uploaded fonts, account fonts, and font mappings. BannersUI can also retain recent colors and fonts used during editing.

### Media

Image and video layers can use uploaded media, connected galleries, or designer-approved alternatives. Alternate media gives users controlled replacement choices while preserving the template’s intended design.

Media may differ between artboards. For example, a package can use alternate crops for a leaderboard and a mobile banner.

BannersUI provides crop, fit, fill, scale, rotation, frame-to-content, content-to-frame, and auto-fit controls. Package rules and locks determine which controls users can access.

### Validation

BannersUI checks packages and jobs for issues that could affect production. Checks can include missing fonts, low-resolution media, hidden text, invalid names, unsupported import features, and overset text.

Resolve warnings before finishing a job or handing off a package. Preview each artboard to confirm content, layout, and media look correct at every required size.

### Output

BannersUI prepares package and job data for downstream production. Static output is commonly generated by the connected backend or DAM.

Animation data can support animated output. GIF output is available when the host configuration supports it. Output is ready only after required validation and preview checks are complete.

Learn more:

* [Brandkits](/bannersui/guides/brandkits.md)
* [Text, Shapes and Media](/bannersui/guides/text-shapes-and-media.md)
* [Animation and GIF Output](/bannersui/guides/animation-and-gif-output.md)
* [Preview, Finish and Troubleshooting](/bannersui/guides/preview-finish-and-troubleshooting.md)


---

# 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.santacruzsoftware.com/bannersui/core-concepts/branding-and-output.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.