What Is Pine Script v6?
Pine Script v6 is the latest version of TradingView's proprietary scripting language, released in 2024. If you have indicators written in v4 or v5, they still work — but v6 brings meaningful improvements in performance, readability, and new built-in functions.
If you're commissioning a new custom indicator, you should always request v6. If you have old indicators, it may be worth migrating them.
Key Changes in Pine Script v6
1. Improved Type System
Pine Script v6 introduces stricter typing and better support for user-defined types (UDTs). This means:
- Less ambiguous code
- Fewer runtime errors
- Better IDE support inside TradingView's editor
// v6 user-defined type example
type Signal
int direction
float price
string label
2. Methods on Built-in Types
v6 allows calling methods directly on arrays, maps, and matrices — making code much cleaner:
// v5 style
array.push(myArray, value)
// v6 style
myArray.push(value)
3. New map Collection Type
v6 added a native map type (key-value pairs), which was previously missing. This is useful for building dynamic dashboards and storing multi-symbol data cleanly.
4. matrix Improvements
The matrix type (2D arrays) got new built-in methods for statistical operations — helpful for multi-timeframe analysis and correlation work.
5. Better request.security() Handling
Data requests across timeframes are cleaner in v6, with improved handling of lookahead parameters that affect whether an indicator repaints or not. This is one of the most common sources of bugs in older indicators.
6. indicator() and strategy() Updates
New parameters in indicator() and strategy() declarations give more control over how scripts appear on charts and interact with alerts.
What Broke When Migrating from v5
Most v5 code runs in v6 with minimal changes. The most common migration issues:
| Issue | Fix |
|---|---|
| Deprecated functions | Replace with v6 equivalents (TradingView shows warnings) |
var declarations with incompatible types | Update type declarations |
Old security() syntax | Update to request.security() with explicit lookahead |
TradingView provides a migration guide in their docs, and most indicators can be updated in under an hour.
Why It Matters for Custom Indicators
If you commission a custom Pine Script indicator and it's built in v5, you're not getting the latest capabilities. More importantly:
- v6 indicators run faster — especially complex ones with many calculations
- v6 code is easier to maintain — cleaner syntax means faster bug fixes
- v6 is where TradingView is investing — future features will be v6 only
At TraderOSHQ, all indicators are written in Pine Script v6 by default.
Should You Migrate Your Old Indicators?
It depends:
- Old indicator that works fine → no urgent need to migrate
- Old indicator with bugs or performance issues → migration often fixes them
- Planning to add new features → migrate first, then add features in v6
Summary
Pine Script v6 is a meaningful upgrade — cleaner syntax, better types, improved performance. If you're building new indicators, there's no reason to use anything older. If you have legacy scripts that are working fine, migration is optional but recommended if you plan to extend them.
Need your old indicator migrated to v6, or want a new one built from scratch? Get a quote from TraderOSHQ.