> 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/statistics/ohlc-expansion-map/sessions.md).

# Timeframes

<figure><img src="/files/D7hMeolC1Wh9zft7etqp" alt=""><figcaption></figcaption></figure>

The **OHLC Expansion Map** is built on the principle of market fractality. Institutional algorithmic price delivery follows the same behavioral patterns whether you are looking at a Yearly, Monthly, Daily, or 15-minute timeframe.

### Multi-Timeframe

The indicator provides four dedicated timeframe slots (**TF1 through TF4**) that can be enabled and configured independently. This allows you to project Higher Timeframe (HTF) behavioral levels directly onto your trading timeframe.

#### Available Timeframe Inputs

You can select from any of the standard TradingView timeframes, including:

* **12M** (Yearly)
* **3M / 1M** (Quarterly / Monthly)
* **1W** (Weekly)
* **1D** (Daily)
* **240 / 60** (4-Hour / 1-Hour)
* **15 / 5 / 1** (Intraday minutes)

{% hint style="info" %}
You are not limited to these defaults. You can manually type in **any custom timeframe** supported by TradingView (e.g., `2D`, `3H`, `90m`, `2W`) into the timeframe input field.
{% endhint %}

### Common Configurations

* **The Swing Trader:** TF1: 1M | TF2: 1W | TF3: 1D
* **The Day Trader:** TF1: 1W | TF2: 1D | TF3: 4H | TF4: 1H
* **The Scalper:** TF1: 1D | TF2: 4H | TF3: 1H | TF4: 15m

### Visual Abbreviation

To keep your chart clean while using all 4 TF slots, enable the **"Abbreviate Labels"** setting. This will change long labels like `[1D] Distribution` to shorter codes like `[1D] +D`, providing more room for price action analysis.


---

# 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.candelacharts.com/statistics/ohlc-expansion-map/sessions.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.