> For the complete documentation index, see [llms.txt](https://docs.simplebooth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simplebooth.com/customization-guide/experience-designer/post-capture/edit-tools/filters.md).

# Filters

Editable filters give guests the freedom to choose an aesthetic that best suits their photo, whether it's a classic black and white or a vibrant, high-contrast look.

***

#### How it Works

When enabled as an Edit Tool, participants can browse a list of filters on the editing screen and select one to apply to their full layout.

Filters can also be enabled as a default [**Frame Effect**](https://docs.simplebooth.com/customization-guide/experience-designer/capture/frame-effects.md). The photo will be captured with the default filter initially, and if the edit tool is enabled, the guest can then change it to something else.

***

#### Configuration Settings

1. **Toggle Enable:** Use the switch to turn the Filters tool on or off for your guests.
2. **Filter Selection:** Choose which filters to display from the 19 available options. You can choose to show the entire library or limit the list to a small, curated selection that fits your event aesthetic.
3. **Reordering:** Drag and drop the filters to change the order in which they are presented to guests.

{% hint style="info" %}
Always test your filter selection with your specific event lighting in advance. Some filters may react differently to warm or cool light sources.
{% endhint %}

***

{% hint style="success" %}

## **Plan Availability**

✅ All Plans
{% endhint %}


---

# 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.simplebooth.com/customization-guide/experience-designer/post-capture/edit-tools/filters.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.
