> For the complete documentation index, see [llms.txt](https://help.brickspacelab.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.brickspacelab.com/slab/getting-started/global-settings/favicon-settings.md).

# Favicon

Favicon settings in **Theme settings > Favicon** set the small icon shown in browser tabs, bookmarks, and some search and sharing surfaces.

## How to change theme favicon

{% stepper %}
{% step %}

#### Upload an image

* Open **Theme settings > Favicon**.
* Under **Favicon image**, select or upload your icon.
  {% endstep %}

{% step %}

#### Save and verify

* Save theme settings.
* Open the storefront in a new tab and confirm the tab icon updates (try a hard refresh or private window).
  {% endstep %}
  {% endstepper %}

### Notes on favicons

* Shopify scales the favicon to about 32×32 px; a square source around 400×400 px stays sharp.
* Simple marks read better than detailed artwork at small sizes.

## Favicon settings

| Setting       | What it controls                                                                          |
| ------------- | ----------------------------------------------------------------------------------------- |
| Favicon image | Image used as the site favicon. Recommended about 400×400 px square; shown near 32×32 px. |


---

# 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://help.brickspacelab.com/slab/getting-started/global-settings/favicon-settings.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.