> For the complete documentation index, see [llms.txt](https://developers.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.felt.com/felt-style-language/zoom-based-styling.md).
# Zoom-based styling
{% hint style="info" %}
Zoom-based styling is useful to change how features and labels are shown at different zoom levels.
{% endhint %}
Most of the properties used on the [`paint`](/felt-style-language/style-definition-blocks/the-paint-block.md) and [`label`](/felt-style-language/style-definition-blocks/the-label-block.md) blocks can be defined using interpolators to enable zoom-based styling — the property tables on those pages mark which ones accept an Interpolator.
We support multiple types of interpolators: Step functions, linear, exponential and cubic bezier to enable your map looking like you want at each zoom level. See the [*Interpolators*](/felt-style-language/zoom-based-styling/interpolators.md) page.
An example of a layer changing feature colors depending on the zoom level can be found below
```json
"paint": {
"color": {"linear": [[14, "red"], [20, "blue"]]}
}
```
On zoom levels lower than `14`, features of this layer will be rendered in `red` color. On zoom levels higher than `20`, features of this layer will be rendered in `blue` color.
In zooms between `14` and `20`, color will be linearly interpolated between `red` and `blue.`
Features at zoom level 14
Features at zoom level 17
Features at zoom level 20
---
# 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://developers.felt.com/felt-style-language/zoom-based-styling.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.
