> 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.

<figure><img src="/files/WkeqzQqagJmIm09YS5FY" alt=""><figcaption><p><em>Using Range Widget to filter retail stores</em></p></figcaption></figure>

### 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.

<figure><img src="/files/2DyGrvfI6OrUMEJBujjZ" alt=""><figcaption><p><em>Defining the minimum and maximum value to filter data</em></p></figcaption></figure>

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.

Additionally, you can make your widgets **collapsible**, allowing you to hide them when needed.

{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.carto.com/carto-user-manual/maps/widgets/range-widget.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.