> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/oscillators/volume-concepts/volatility-bands.md).

# Volatility Bands

The Volume Concepts uses **Elastic Bands** on the price pane to visualize the statistical boundaries used for the oscillator calculation.

<figure><img src="https://3870127617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBVnUk5c5TVytimjy972%2Fuploads%2FkRaIBmvEmX93KOmGJRMU%2Fdocs-volume-matrix-003.png?alt=media&amp;token=96faaafb-b0e3-4b5f-914b-257f141dc974" alt=""><figcaption></figcaption></figure>

### Band Types

There are four bands plotted on the chart:

1. **Outer Bands (±σ x2)**:
   * **Logic**: Based on the Standard Deviation of the volume-weighted mean.
   * **Purpose**: These represent the extreme boundaries of expected volatility. Price wicking out of these bands is a "Breakout".
2. **Inner Bands (±σ x1)**:
   * **Logic**: Based on the **Robust Sigma** (Mean Absolute Deviation).
   * **Purpose**: These are "Robust" measures that are less sensitive to price spikes but more responsive to sustained volume shifts. They define the "Core" range of the asset.

### Using the Bands

* **Band Expansion**: Indicates a high-volatility environment (Trending).
* **Band Contraction**: Indicates low volatility (Consolidation/Squeeze).
* **Mean Line (Gray Line)**: This is the **ePulse μ** (Elastic Pulse Mean). It's the volume-weighted "Fair Value" of the asset.
* **Shadow Fills**: The areas between the Inner and Outer bands are filled to create "Extreme Heatmaps", helping you quickly identify when the price is entering an over-extended state.


---

# 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.candelacharts.com/oscillators/volume-concepts/volatility-bands.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.
