> For the complete documentation index, see [llms.txt](https://docs.carto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carto.com/carto-user-manual/maps/widgets/range-widget.md).
# Range widget
The Range Widget enables precise data filtering, allowing you to define specific numerical ranges.
Using Range Widget to filter retail stores
### Widget Data
In the Data section, select a numeric field from your source dataset that you want to analyze.
### Widget Display
In the Widget Display, the default range corresponds to the minimum and maximum values of the selected numeric field. This provides a starting point for your visualization. However, you have the flexibility to customize these limit values, allowing you to effectively filter specific features within your data.
Defining the minimum and maximum value to filter data
In the display section, you can also use **formatting** to choose the unit of metrics displayed on the y-axis. Additionally, you can add **notes** that support [Markdown syntax](https://www.markdownguide.org/basic-syntax/).
### Widget Behavior
For Range widgets, the cross-filtering toggle appears disabled since filtering is always active. These widgets support filtering over a single source or across multiple sources, as long as they share the same property.
{% hint style="info" %}
Only **one Range widget per map** using a specific property can be configured to cross-filter across multiple sources.
{% endhint %}
Learn more about widget behavior [here](/carto-user-manual/maps/widgets.md#widget-behaviour).
---
# 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.carto.com/carto-user-manual/maps/widgets/range-widget.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.
