Multi-Timeframe EMA Alignment
Compares a fast and slow EMA on three selected timeframes without reading an unfinished higher-timeframe candle.
Start with the input, not the story.
Whether the fast EMA is above, below or equal to the slow EMA on each selected timeframe; it measures shared trend state, not three independent signals.
The price overlay uses exact EMA calculations. The panel compares H1, H4 and D1 fast-minus-slow readings from each timeframe's previous completed candle. Above zero means the fast EMA is above the slow EMA; below zero means the opposite.
All three rows come from the same underlying market. Three positive readings are useful context, but they are not three independent confirmations.How traders commonly use Multi-Timeframe EMA Alignment
Traders use alignment as an eligibility filter, then look for a separately defined lower-timeframe location or setup.
Make higher- and lower-timeframe EMA states explicit using only candles that were complete at the decision time.
Keep this job separate from entry timing, stop placement and position size.
A useful counterexample
Three aligned rows are not three independent confirmations: every row is derived from the same price series and may turn late.
EMA alignment for context, structure for timing, calendar for event risk
Each part has a different job. If two tools answer the same question, remove one and compare the result.
Defines the closed-bar top-down trend state.
Provides a lower-timeframe location and invalidation point.
Flags scheduled events that can distort the sample.
Follow the same order every time
- Choose the three timeframes and both EMA periods before reviewing any examples.
- Advance one lower-timeframe candle and read only the preceding completed candle on each higher timeframe.
- Record aligned, mixed or neutral rather than counting each row as a separate vote.
- Add a confirmed swing rule for location and define where that structure would fail.
- Tag scheduled-event windows so they can be analysed separately.
The indicator is one part of the method
These strategy pages show the market conditions, entry, stop and exit around the indicator.
Multi-timeframe continuation
Aligns a higher-timeframe state with a lower-timeframe trigger without peeking into unfinished bars.
- ENTRY
- Enter at the next M15 open after a candle closes back across EMA(20) in the H4 direction and beyond the prior M15 candle high/low.
- STOP
- Place stop 0.25 × M15 ATR(14) beyond the pullback extreme; risk 0.35% of equity and round down to 0.01 lot.
- EXIT
- Take profit at 2R. Exit early only when a completed M15 candle closes through the stop-side pullback extreme; close unresolved trades after 24 M15 bars.
Trend pullback
Research whether shallow retracements inside an objective trend resume in its direction.
- ENTRY
- After eligibility is true, place a market order at the next H1 open when the signal candle closes beyond the highest high of the previous two pullback bars for a long, or below their lowest low for a short.
- STOP
- Place the stop 0.25 × ATR(14) beyond the pullback extreme. Size so entry-to-stop risk equals 0.50% of demo equity, rounded down to 0.01 lot; never widen the stop.
- EXIT
- Place a fixed target at 2R immediately after entry. If neither stop nor target trades first, exit at market after 24 completed H1 bars.
EMA and ADX trend filter
Combines direction from an EMA with a non-directional trend-strength filter.
- ENTRY
- Enter at the next H4 open after the eligible boundary close.
- STOP
- Stop 1.5 × ATR(14) from fill. Risk 0.50% equity and round down to 0.01 lot.
- EXIT
- Take profit at 2R. Exit early at next open after a completed close crosses EMA(50) against the position.
Set up Multi-Timeframe EMA Alignment on your platform
Match the lesson's period, price input, smoothing and candle timing. Similar names can still produce different values across feeds and platforms.
MT4
Custom code neededA faithful on-chart version needs an MQL4 implementation. Check the source note below when WickAtlas provides one.
MT5
Custom code neededA faithful on-chart version needs an MQL5 implementation. Check the download note below before assuming WickAtlas provides one.
TradingView
Custom code neededA faithful on-chart version needs a Pine Script implementation. Check the source note below when WickAtlas provides one, or review third-party code before use.
“Built in” means the standard platform library contains the underlying indicator. It does not mean its defaults or calculation match every third-party version. Compare the platforms.
Plain-language formula
The same indicator can look slightly different across platforms because the price input, smoothing and rounding may change. Note your settings before comparing two charts.
Where it may help
Making top-down trend eligibility explicit and auditing exactly when higher-timeframe context became available.
Where it struggles
Lagging turns, sideways markets, missing higher-timeframe history and charts whose timeframe is above one of the selected inputs.
What to pair it with
Pair it with something that answers a different question, such as volatility or market direction. Try the indicator on its own before adding more tools.
The shortcut to avoid
Counting three green rows as three independent confirmations even though all rows transform the same price series.
Try this on a chart
Freeze the EMA periods and timeframes, then compare a closed-bar alignment rule with a single-timeframe EMA control across trend and range regimes; include delayed entry, spread and an untouched out-of-sample period.
Use the version made for your platform
The MT4, MT5 and TradingView files are separate source implementations—not renamed copies. Read the code, compile or add it on the intended platform, and compare its output with the lesson before relying on it in practice.
Read platform notes, permissions and checksums →