Pine Script v6: Every Change Since Launch, and What It Means for Alerts

Everything TradingView has added to Pine Script v6 since launch, month by month through August 2026, and the handful of changes that matter if your strategy sends alerts to a broker.

Pine Script v6: Every Change Since Launch, and What It Means for Alerts

TradingView released Pine Script v6 at the end of 2024, and it has not stood still since. Almost every month has added something: new functions, new types, and in July 2026 a redesign of how strategies are tested.

Most changelogs list everything and leave you to work out what matters. This one lists every notable change from TradingView's release notes, then picks out the ones that change how an automated strategy behaves or what its alerts send. If your script places orders through a webhook, those are the ones to read.

The launch: what v6 changed

Dynamic requests. request.security() and the other request.*() functions can take a symbol or timeframe that changes from bar to bar, and can be called inside loops, conditions and library functions. In v6 this is on by default.

Booleans are never na, and logic is lazy. A bool is always true or false. and and or stop evaluating as soon as the answer is known, so the second half of a condition may never run.

Strategies no longer stop at 9,000 trades. Outside Deep Backtesting, a long backtest now drops its oldest trades instead of halting.

Negative array indices. array.get(a, -1) returns the last element.

Text formatting. Integer text sizes and bold or italic text in labels, boxes and tables.

Breaking changes when converting a v5 strategy: the when argument is gone from order functions, timeframe.period always includes a number ("1D", not "D"), transp is removed, and the default margin for strategies changed from 0 to 100. That last one can make a converted strategy show margin calls it never showed in v5. The Pine Editor can convert a v5 script for you, but check these by hand afterwards.

Every change since, month by month

December 2024. strategy.exit() now looks at both halves of a pair, such as limit and profit, and uses whichever price the market is expected to reach first. Before, the absolute price always won.

February 2025. The limit of 550 scopes per script is gone. New bid and ask values, available on the one-tick timeframe only.

March 2025. for loops re-check their end boundary on every pass. New box.set_xloc().

April 2025. Renko, point and figure and Kagi requests accept a percentage-of-price box size.

May 2025. time_close keeps working on past real-time bars of tick and price-based charts.

June 2025. Libraries can export constant variables.

July 2025. Inputs gain an active parameter, to grey out settings that do not apply. New syminfo.current_contract, which names the actual futures contract behind a continuous symbol like ES1!.

August 2025. Strings can now be up to 40,960 characters, up from 4,096. The Pine Editor moved to the side panel.

September 2025. plot() gets dashed and dotted line styles.

October 2025. time() and time_close() gain timeframe_bars_back.

November 2025. New syminfo.isin.

December 2025. Lines wrapped inside parentheses can use any indentation.

January 2026. Footprint requests: request.footprint() with new footprint and volume_row types, on Premium and Ultimate plans.

April 2026. Multiline strings with triple quotes. Sorting arrays of your own types by a chosen field.

July 2026. A redesign of strategy testing. The Strategy Tester is now called the strategy report. Bar Magnifier is replaced by a Bar detalization menu. New settings replace old checkboxes for Heikin Ashi fills, limit order fills, order execution delay and leverage, while the old strategy() arguments still set their defaults. A new calc_on_every_history_tick option runs a strategy on every tick of historical bars, on Premium and Ultimate.

August 2026. A new once keyword, whose block runs only the first time its condition is true on a closed bar. Improvements to the Pine Screener, and binary search on sorted arrays of your own types.

What matters if your strategy sends alerts

Multiline strings make webhook messages readable. A CrossTrade order with brackets and sync fields no longer has to be a single long line of + joins. Write it as one block with triple quotes and insert the values you calculate.

Longer strings mean richer messages. The jump to 40,960 characters matches the size TradingView accepts for a message built in Pine with alert() or alert_message. A message typed into the alert dialog is still limited to 4,000.

Check the exit change on old backtests. If your strategy passes both a price and a distance to strategy.exit(), results from before December 2024 may not match a backtest run today.

Converted strategies need a margin check. The margin default moving from 0 to 100 changes backtest results for any v5 strategy converted to v6 without setting margin explicitly.

Bar detalization changes fills, not signals. It makes the strategy report's fills more realistic by looking inside each bar. It does not change when your live alerts fire.

syminfo.current_contract tells you what you are really trading. On a continuous chart it names the contract month behind the symbol, which helps when you log trades or debug a fill around a roll.

once is a clean one-shot. Use it for anything that should happen a single time, such as a daily flatten signal, rather than a flag variable you reset by hand.

To build the whole order inside your script, see Using Pine Script Variables in Alerts, and for working strategy code, Pine Script v6 Strategy Code Examples.

Frequently asked questions

When was Pine Script v6 released?

At the end of 2024. TradingView's release notes list it as November 2024, and it was announced publicly in December.

What is the biggest change in Pine Script v6?

Dynamic requests, which let request.security() use symbols and timeframes that change from bar to bar. For strategies, the removal of the when argument and the new default margin matter most when converting.

Does a v5 script need to be converted to v6?

No, v5 scripts keep running. New features only arrive in v6, and the Pine Editor can convert a script for you. Recheck strategy results afterwards.

What happened to Bar Magnifier?

In July 2026 TradingView replaced it with a Bar detalization menu in the strategy report. The use_bar_magnifier argument still sets its default.

Are enums a Pine Script v6 feature?

No. Enums arrived in June 2024, in Pine Script v5, before v6 launched.

Sources

Automate your v6 strategy

When your strategy is ready to trade, start a free 7-day trial to send its alerts to NinjaTrader 8 or Tradovate, and bring Pine questions to the CrossTrade Discord.

CrossTrade is execution and automation software, not a broker, financial adviser, or trading strategy. Pine Script features and plan requirements are set by TradingView and change. Futures trading involves substantial risk. Test every automated workflow in simulation and verify orders at your broker.

Start your free trial

Try CrossTrade for 7 days.

Sign Up