> For the complete documentation index, see [llms.txt](https://docs.tradingalert.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradingalert.net/indicator-alert-feature/how-mtf-multi-timeframe-work.md).

# How "MTF (Multi-Timeframe)" work ?

{% embed url="<https://www.youtube.com/watch?index=7&list=PLbIN3JoRtARU&v=AMHtXqLXsKk>" %}

By default every condition of an indicator alert uses the **same timeframe** — the one you pick in **Time Frame** at the top of the alert.

**MTF** lets **each condition use its own timeframe** inside one alert. A classic use: confirm the trend on a big timeframe, and take the entry signal on a small one.

> Example: *"Alert me when RSI on **M15** crosses up 30, but only while EMA 50 is above EMA 200 on **H4**."*

<figure><img src="https://1752735084-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLEg9b9dcLWBfThsXevkl%2Fuploads%2F78V36euhJ1EYDOqcd7Wm%2Fhow-mtf-work-1-setup.png?alt=media&amp;token=43182c81-27df-48df-b48e-473fb3315b3b" alt=""><figcaption></figcaption></figure>

*One alert, two timeframes: H4 decides the trend, M15 gives the signal.*

### Where to find it

Open **Add Indicator Alert** (or edit an existing one):

1. Pick the **Market | Broker** and the **pair** as usual.
2. Tap **Time Frame** and choose **MTF** — it is the **last item** of the list.
3. Tap **Add Condition** and set up the indicator.
4. Every condition row now shows two extra selectors:
   * **TF** — the timeframe of this condition.
   * **Data Use** — **Closed Candle** or **Every Minute** (see below).
5. Set the **TF** of each row, choose how many conditions must be met, then tap **Add Alert**.

{% hint style="info" %}
The **TF** and **Data Use** selectors on the condition rows can only be changed when the alert's Time Frame is **MTF**. With any other Time Frame, all conditions simply follow that Time Frame.
{% endhint %}

### What it means

* Each condition is calculated on the candles of **its own TF**. An RSI condition on M15 reads M15 candles, an EMA condition on H4 reads H4 candles — even though they are in the same alert.
* The alert is checked on the **shortest timeframe** used by its conditions. In the example above (H4 + M15) the alert is checked every M15 candle, and the H4 condition is read from the latest H4 data at that moment.
* The conditions are then combined exactly like a normal alert: **Must Meet**, the number of conditions to reach, or the groups of Advanced mode.
* The notification shows **MTF** instead of a single timeframe, e.g. `EURUSD-MTF: your note`.

| Condition                                         | TF  | Role                                                |
| ------------------------------------------------- | --- | --------------------------------------------------- |
| EMA(50) Over EMA(200)                             | H4  | Trend filter — stays true for many M15 candles      |
| RSI(14) Cross Over 30                             | M15 | Entry signal — the moment to be alerted             |
| Trigger when at least 2/2 conditions reach target |     | Alert only when **both** are true at the same check |

### Data Use: Closed Candle or Every Minute

Each MTF condition chooses which data it uses:

* **Closed Candle** — uses the last **closed** candle of its TF. The value does not change until that candle closes.
* **Every Minute** — the condition is checked **every minute** with the real-time price, on the candle that is still forming. It can trigger before the candle closes, which also means the value may change afterwards.

When Time Frame is **MTF**, the **Calculation Mode** selector at the top is **locked**: it follows your conditions. If at least one condition uses **Every Minute**, it shows **Every Minute**, otherwise **At End of Candle** (the same thing as *Closed Candle* on a condition row). See also How "Candle To Check" work ?

### Rules and limits

* The timeframes you can pick depend on the market. For example **Binance** has no M2, M10, M20.
* MTF works with everything else on the condition: **Candle To Check**, Multi-Candle, Distance limit, and with both **Basic** and **Advanced** mode.
* **Careful when leaving MTF:** if you switch Time Frame from MTF back to a single timeframe (e.g. H1), **every condition is reset to H1** and to the Calculation Mode at the top. Your per-condition TF choices are not kept.

### Good to know

* Put the **slow** condition (trend, big TF) and the **fast** condition (signal, small TF) in the same alert and require **both** (Must Meet, or *Trigger when at least 2/2*) — that is the most common MTF setup.
* A Closed Candle condition on a big TF keeps the same result for the whole length of that candle (up to 4 hours on H4). During that time the small-TF condition can trigger the alert several times — that is expected.
* If an MTF alert never triggers, check that the **TF of each row** is really the one you want: a row left on the wrong TF is the most common mistake.

[<img src="https://tracking.avapartner.com/imp/?affid=214848&#x26;bannerid=35546&#x26;adTheme=768&#x26;campaign=221449&#x26;campaignName=Default%20Campaign&#x26;tag=214848&#x26;source=general_setting" alt="" data-size="line">](https://tracking.avapartner.com/click/?affid=214848\&bannerid=35546\&adTheme=768\&campaign=221449\&campaignName=Default%20Campaign\&tag=214848\&source=about_indi_alert)[![](https://d3dpet1g0ty5ed.cloudfront.net/EN_Spreads_Pay_less_keep_more_2-4_Google_300x250.jpg)](https://one.exnessonelink.com/intl/en/a/t7p3v7p3)
