> For the complete documentation index, see [llms.txt](https://docs.ultramarinastudios.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ultramarinastudios.com/theme-settings/logo.md).

# Logo

### Logo

Upload the global logo for your site here. For best results, we recommend using an SVG as it ensures your logo will look crisp on all devices. Otherwise, we suggest uploading a transparent PNG at a high resolution (1000x1000px).

You should ensure that your default logo is visible on your header color scheme by default.

#### Alternate logo

If you are using color schemes within your store, it may be possible that your logo is not visible on your alternate color schemes. We suggest uploading an alternate version of your logo here, and in different sections, you can opt into using this alternate version of the logo. The logo should be the exact same as your default logo, but in a different color scheme.

For example, if your logo is black text with a transparent background, your alternate logo could use white text and a transparent background.

#### Logo width

Set a maximum width for your site logo here. This setting affects both the logo and alternate logo. &#x20;

#### Favicon

The favicon shows up in the browser tab next to the page title and potentially is displayed in your search results.


---

# 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.ultramarinastudios.com/theme-settings/logo.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.
