Home › Guides › Platforms

Pine Script higher-timeframe trend: see the bigger chart on any chart

We check the bigger chart before every trade, and trade with it. This script does that check for you, on whatever chart you're looking at, using only daily candles that have already closed.

Beginner guide · 8-minute read · Updated 2026-10-21

Why a bigger-chart filter?

A 15-minute chart shows the waves. The daily chart shows the tide.

A buy setup on the 15-minute chart is swimming with the tide when the daily trend is up, and against it when the daily trend is down. Our method is simple about this: check the bigger chart first, and trade with it. More in multiple timeframe analysis.

Switching charts back and forth is easy to skip. A small script puts the answer on the chart you trade from.

This page builds on Pine Script request.security, which explains how bigger-timeframe data works and why it can repaint. Read that first if the terms are new.

What "trend up" means here

We need a rule a script can check. This one uses the daily chart and a 50-day EMA (an average that leans toward recent days):

• Up: the last finished daily close is above the 50-day average, and the average is rising.
• Down: the close is below the average, and the average is falling.
• Unclear: anything else.

"Unclear" is an answer too. It often means sit tight.

The script

//@version=6
indicator("Bigger-chart trend", overlay=true)
tf = input.timeframe("D", "Bigger timeframe")
len = input.int(50, "Average length", minval=2)
if timeframe.in_seconds(tf) <= timeframe.in_seconds(timeframe.period)
    runtime.error("Pick a bigger timeframe than the chart's.")
[bigClose, bigAvg, bigAvgPrev] = request.security(syminfo.tickerid, tf, [close[1], ta.ema(close, len)[1], ta.ema(close, len)[2]], lookahead=barmerge.lookahead_on)
trendUp = bigClose > bigAvg and bigAvg > bigAvgPrev
trendDown = bigClose < bigAvg and bigAvg < bigAvgPrev
bgcolor(trendUp ? color.new(color.green, 92) : trendDown ? color.new(color.red, 92) : na)
plot(bigAvg, "Bigger average", color=color.purple, linewidth=2)
var label tag = label.new(bar_index, close, "", style=label.style_label_left, textcolor=color.white)
if barstate.islast
    word = trendUp ? "Up" : trendDown ? "Down" : "Unclear"
    label.set_xy(tag, bar_index + 2, close)
    label.set_text(tag, tf + " trend: " + word)
    label.set_color(tag, trendUp ? color.green : trendDown ? color.red : color.gray)

Every line, in plain words

• Line 1 says this is Pine Script version 6.
• Line 2 names the script and puts it on the price chart.
• Line 3 makes the bigger timeframe a setting. "D" is daily.
• Line 4 makes the average length a setting.
• Lines 5 and 6 stop the script with a clear message if the "bigger" timeframe isn't bigger. timeframe.in_seconds turns a timeframe into a number of seconds, so they can be compared.
• Line 7 does the main work. It asks the daily chart for 3 values at once, in square brackets: yesterday's close, yesterday's average, and the day before's average. [1] means one daily candle back. [2] means two.
• Line 8 is true when the trend is up by our rule.
• Line 9 is true when it's down.
• Line 10 shades the background faint green for up, faint red for down, and leaves it clear when unclear.
• Line 11 draws the daily average as a thick purple line. On a small chart it looks like steps, because it changes once a day.
• Line 12 makes one label, once. var keeps it.
• Lines 13 to 17 update it on the newest candle: move it to the right of price, write "D trend: Up" (or Down or Unclear), and color it.

Why [1] with lookahead_on?

This is the part that keeps the script honest.

Line 7 only uses finished daily candles: [1] and [2]. lookahead_on lines each finished value up with the start of the next day, instead of a day late.

Together, they mean: what you see live is what history shows later. Nothing changes after it's drawn.

The cost is that the trend is always one day behind. On a daily trend check, that's a fair trade. A full explanation is in Pine Script request.security.

Picking the bigger timeframe

A common habit is about 4 to 6 times bigger than the chart you trade:

Too close, and the "bigger" trend is just noise. Too far, and it changes so rarely it says little.

A better trend rule

An average is a simple way to read direction. It's also late. A more direct read is the one we teach: higher highs and higher lows for up, lower highs and lower lows for down. See higher highs and higher lows and how to identify a trend.

You can code that too, with turning points from Pine Script swing highs and lows, and pull it from the bigger timeframe the same way.

Use it as a filter, not a trigger

The bigger-chart trend answers one question: which way should I be looking? It doesn't say when to act.

• Trend up: only look for buy setups on your chart.
• Trend down: only look for sell setups.
• Unclear: wait, or trade smaller.

Combine it with a setup rule, like a candle body closing past a level. Pair it with the crossover in Pine Script moving average crossover, or put the answer in a Pine Script table with your other checks.

Then every trade still needs a stop from the chart and a size from the math.

Try it today

1. Paste the script into the Pine Editor on a computer. Save and add it to a 15-minute chart.
2. Scroll back a few weeks. Notice the shading changes only at the start of a day.
3. Change the timeframe setting to "W" (weekly) and look again. Fewer changes.
4. On bar replay, step through a week. Check that the color never changes after it's drawn.

Learning from a real script

Our course includes the full source code of the StructureX chart tool to learn from and customize, for example adding your own bigger-chart filter. It's source code, not a ready-made trading bot.

Common mistakes

• lookahead_on without [1]. The past peeks at the future.
• A "bigger" timeframe that isn't bigger. Lines 5 and 6 catch this.
• Treating the filter as a buy signal. It only tells you which way to look.
• Forgetting it's a day behind. It's honest, but it's late by design.

Questions