Pine ScriptJun 2, 20269 min read416 views

Pine Script v6 Syntax Changes: Everything That Breaks Coming from v5

Upgrading a Pine Script v5 strategy to v6 or starting fresh? Here are every breaking change, renamed function, and new requirement in Pine Script v6 — with before/after examples for each.

Why v5 scripts break in v6

Pine Script v6 is not backwards compatible with v5 in several important ways. TradingView made the type system stricter, removed deprecated functions, renamed namespaces, and changed how inputs work. A script that compiled fine in v5 can produce 5-10 errors the moment you change //@version=5 to //@version=6.

This guide goes through every breaking change with concrete before/after examples. If you are upgrading an existing script or building something new in v6 and hitting unexplained errors, this is where to start.

1. Function namespaces: ta., strategy., request.*

The single most common source of v6 errors. In v5 and earlier, many indicator functions were global. In v6, they must be accessed through their namespace.

sma() → ta.sma()
ema() → ta.ema()
rsi() → ta.rsi()
macd() → ta.macd()
atr() → ta.atr()
stoch() → ta.stoch()
crossover() → ta.crossover()
crossunder() → ta.crossunder()
highest() → ta.highest()
lowest() → ta.lowest()
security() → request.security()
study() → indicator()

Tip

If you see 'Undeclared identifier' on a function that obviously exists, it almost certainly needs a namespace prefix. Add ta. before indicator functions and request. before security().

2. Input functions: input.int(), input.float(), input.bool()

The old input() function with a type argument is gone in v6. Each input type now has its own dedicated function, and the parameter names changed too.

// v5 (broken in v6)
fastLen = input(9,    type=input.integer, title="Fast EMA")
stopPct = input(1.5,  type=input.float,   title="Stop %")
showMa  = input(true, type=input.bool,    title="Show MA")

// v6 (correct)
fastLen = input.int(defval=9,    title="Fast EMA",  minval=1)
stopPct = input.float(defval=1.5, title="Stop %",   minval=0.1, step=0.1)
showMa  = input.bool(defval=true, title="Show MA")

3. Explicit type declarations

v6 enforces stricter type rules. Variables used in certain contexts must be explicitly typed. The most common case: variables that could be na on the first bar need a typed na declaration.

// v5 — works
myStop = na

// v6 — fails: cannot determine type of na
float myStop = na  // correct in v6

4. strategy.risk.* functions removed

Pine Script v6 removed the entire strategy.risk.* namespace. If your v5 script used strategy.risk.max_drawdown(), strategy.risk.max_intraday_loss(), or strategy.risk.allow_entry_in(), those calls will fail silently or throw errors.

Risk management in v6 must be implemented manually: track drawdown with a var float variable, calculate intraday high-water marks using bar_index, and gate entries with a boolean condition.

5. bgcolor() and plot() scope rules

In v6, bgcolor(), plot(), plotshape(), hline(), and fill() must be called at the global scope — not inside if blocks or functions. Moving any of these inside a conditional block will throw a scope error.

// v5 — compiled with warnings
if condition
    bgcolor(color.green)  // WRONG in v6

// v6 — correct
bgcolor(condition ? color.new(color.green, 80) : na)

6. request.security() — lookahead and gaps required

In v6, request.security() should always be called with explicit gaps and lookahead arguments. Omitting them works but produces a lookahead bias warning and may fail linting in future versions.

// v6 correct pattern
dailyClose = request.security(syminfo.tickerid, "D", close[1],
    gaps=barmerge.gaps_off,
    lookahead=barmerge.lookahead_off)

Tip

Always use close[1] (not close) for higher-timeframe values to avoid lookahead bias. The [1] shifts the value back one bar so you're using confirmed data.

Migrating a full v5 script to v6

The fastest migration path: paste your v5 script into TradePilot's chat and say 'upgrade this to Pine Script v6 and fix all syntax errors'. TradePilot has the complete v6 reference in context, so it will correctly rename every function, fix the type system issues, and rewrite the input declarations — without changing your strategy logic.

TradePilot Team

Traders and engineers building the fastest way to go from idea to live Pine Script strategy, right inside TradingView.

Technical

Pine Script v6 vs v5: Why It Matters for AI-Generated Code

Read Tutorial

Automatically Sweep Strategy Parameters on TradingView

Read Tutorial

Multi-Timeframe Chart Analysis With an AI Copilot

Read Product

Try an AI Copilot for TradingView Free for 7 Days

Read Beginner

Pine Script AI for People Who Don't Code