Skip to content
TradingLead

Feature

Pine Script v5/v6 Indicators on TradingLead

TradingLead supports a documented Pine v5/v6 indicator subset. Source is validated before execution. Paste a Pine indicator into Indicator Studio's TLScript-Pine mode, see whether it works directly, needs approximations or needs changes, then apply it to NSE/BSE and other charts — without claiming that every TradingView script will run.

What it does

TLScript-Pine is TradingLead's Pine-compatible runtime. It lets you write or paste indicators in Pine Script syntax and run them on TradingLead charts, including Indian stocks and indices.

TradingLead supports a documented Pine v5/v6 indicator subset. Source is validated before execution. That means TradingLead does not pretend to be TradingView's engine: it checks each script against a published compatibility manifest and tells you, line by line, what will run, what will run with visual approximations and what is not available.

How it works

  1. Paste or write a Pine indicator in Indicator Studio with the language set to TLScript-Pine.
  2. Local compatibility check. While you type or paste, Studio classifies the script as one of:
    • Works directly — no known compatibility changes were found.
    • Works with approximations — it can run, with listed differences in rendering, inputs or runtime behaviour.
    • Needs conversion — the script targets a different TradingLead workflow (for example a strategy() that belongs in Backtesting).
    • Unavailable — it needs a Pine capability with no TradingLead equivalent, such as request.financial.
  3. Compile. The source is compiled inside an isolated sandbox worker with no page access, credentials or direct network access. Diagnostics show line and column.
  4. Apply. Apply adds the indicator to the active chart, using the candles of the chart's current symbol, interval and data feed.
  5. Save (optional). Save stores source and input values in your library. Saving and applying are separate on purpose.

Key capabilities

  • Versions: //@version=5 and //@version=6 (v6 preferred). Older and unknown versions, and scripts with no version line, are rejected.
  • Language: user functions, methods, overloads, user-defined types, arrays/maps/matrices, tuples, for/while loops, var/varip, typed declarations and qualifier checks — within the documented subset.
  • Built-ins verified in the manifest include ta.sma, ta.ema, ta.rma, ta.wma, ta.stdev, ta.bb, ta.crossover/crossunder, ta.macd, ta.vwap, ta.valuewhen, ta.barssince, string, colour and math functions.
  • Indian market context: ta.vwap resets on exchange-local trading days, and the built-in Indian cash-equity/index catalogue reports syminfo.currency as INR.
  • Inputs: input.int, float, bool, string, color, source, timeframe, symbol, session, time, price, enum and text_area, with group, inline and tooltip layout. Up to 100 declared inputs.
  • Outputs: plot styles (line, step line, histogram, columns, area, cross, circles) plus chart-only plotcandle, plotbar, plotshape, plotchar, plotarrow, hline, fill, bgcolor, barcolor, label, line, box, table, polyline and linefill.
  • Multi-timeframe and multi-symbol: request.security and request.security_lower_tf on charts, from the same authorized feed. A different exchange or unavailable symbol is never silently substituted.
  • AI help: Copy fix prompt turns the exact problem list into a prompt for the AI you use; Paste AI fix previews and re-validates the returned code before it touches your draft.
  • Strategies: strategy() scripts compile and save in Studio and run through backtesting with Apply & backtest.

What is not supported

Pine featureStatus on TradingLead
request.financial, request.earnings, request.dividends, request.splits, request.economic, request.currency_rate, request.seed, request.quandlRejected — no TradingView-hosted data services
import publisher/library/versionRejected — hosted libraries are not fetched
Server alerts (push, webhook, email) from alert/alertconditionUnavailable — events are local to the chart
request.security in local scansRejected in scanners; works on charts
strategy() as a chart indicatorRuns through Backtesting instead
Interactive confirm=true and chart price pickingValue supported; enter it manually

How to use it

Follow the step-by-step guide Run a Pine Script indicator on TradingLead. For strategies, see Backtest a Pine strategy.

Limitations

  • This is a documented subset. TradingLead makes no claim that all TradingView scripts work, or that values match TradingView to the last decimal or repaint identically.
  • Drawings, tables and markers render as chart-only outputs, and some (marker glyphs, fill gradients, arrow sizing) are visual approximations.
  • Execution is bounded: 30 seconds per operation, 100,000 input bars, 40 secondary data contexts and 20,000 iterations per loop. There is no fixed source-length cap.
  • Indicator results are analysis tools, not investment advice. Backtests are simulations, not guarantees of future results.

Related

Limitations

  • Documented Pine v5/v6 subset only; no full TradingView compatibility, numerical or repainting parity is claimed.
  • TradingView-hosted requests (request.financial, request.economic, request.earnings, request.dividends, request.splits, request.currency_rate, request.seed, request.quandl) and library imports are rejected.
  • Alerts from Pine are local chart events; no push, webhook, email or server-side delivery.
  • Drawings, tables, labels, boxes and polylines are chart-only and some are visual approximations.
  • Execution bounds: 30 seconds per operation, 100,000 input bars, 40 secondary data contexts, 20,000 iterations per loop.

Frequently asked questions

Can I run my TradingView Pine Script on TradingLead?
Often, but not always. TradingLead supports a documented Pine v5/v6 indicator subset and validates source before execution. Indicator Studio tells you whether a script works directly, works with approximations, needs conversion or is unavailable, with the exact lines that need attention.
Which Pine versions are supported?
//@version=5 and //@version=6. Version 6 is preferred for new scripts. Scripts for versions 1 to 4, unknown future versions, or with no //@version line are rejected.
Does request.security work?
Yes on charts, using history from the same authorized data feed as the chart. It is not supported in local provider scans. TradingView-hosted data such as request.financial, request.earnings, request.dividends and request.economic is not available.
Can I import published TradingView Pine libraries?
No. import of publisher libraries is rejected because TradingView-hosted libraries are not fetched or installed. Paste the needed functions into your own script instead.
Do Pine alertcondition alerts send notifications?
No server notifications. alert() and alertcondition() events are local to the chart. An alertcondition can be handed to the Alerts panel as a local rule that is evaluated while the app is open; push, webhook and email delivery for indicator conditions are not available.
Can I backtest a Pine strategy?
Yes, through Backtesting rather than as a chart indicator. Pine strategy() scripts compile and save in Studio and run with Apply & backtest. Results are simulations on TradingLead's broker-emulator model, not TradingView's engine.

Last updated: