> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/theme-settings/filter-swatches.md).
# Filter Swatches
Set up filter display on Volume collection pages: checkbox, pill, color swatch, or thumbnail styles with two layout options. Requires Search & Discovery.
Before setting up the display options, first configure your filters. To do this, download the free **Search & Discovery** app from Shopify and follow the manual instructions.
The interface element display settings in filters work similarly to the [**Variant Picker**](/docs/volume-themes/theme-settings/variant-picker.md).
***
### Option Display Types
The default display style is checkboxes in a single column.
{% columns %}
{% column %}
There are four display types for filter options:
* Checkbox
* Pill
* Color swatch
* Thumbnail image
{% endcolumn %}
{% column %}
Additionally, there are two layout options:
* Two columns
* In a row
{% endcolumn %}
{% endcolumns %}
You can find detailed guidance on setting up [**Color Swatches**](/docs/volume-themes/products/color-swatches.md) through the provided link.
***
### Setup Example
The example below illustrates different display settings. Pay attention to the fields under the **Layout** heading.
---
# 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://staylime.com/docs/volume-themes/theme-settings/filter-swatches.md?ask=&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.
