TradingView chart workflows

TradingView tick charts: data and script limits

TradingView tick charts group successive ticks into bars instead of dividing activity into fixed time periods. Available intervals are 1T, 10T, 100T, and 1000T. The current plan comparison includes tick intervals with Ultimate. Before using a tick chart for research, check the exact symbol, available history, and script behavior. A tick candle alone does not identify which side initiated each trade.

See the decision guide

Tick bars and time bars answer different questions

A time chart groups observations by clock interval. A tick chart groups them by count, so its bars arrive faster during active trading and more slowly when activity falls. This changes the observations supplied to an indicator even when you leave its settings unchanged.

  • Illustrative example: suppose 100 ticks arrive in 10 seconds, then the next 100 take two minutes. Both groups fill one 100T bar, despite their different durations. This is hypothetical data, not an observed market test.
  • For a hypothetical 20-bar average on 100T, twenty full bars contain 2,000 ticks. Twenty one-minute bars cover twenty minutes. Equal lengths therefore do not create equivalent signals.
  • Tick bars reset at a new trading session, so the prior session can end with a partial group. Keep session boundaries in the comparison record.
QuestionTime chartTick chart
What defines a bar?A fixed time intervalA chosen count of successive ticks
What varies?Activity within each intervalElapsed time within each bar
What does a 20-bar lookback represent?Twenty time intervalsTwenty groups of ticks
What should a comparison preserve?Symbol, session, inputs, and datesThe same context, plus the tick interval

Check access and coverage for your exact symbol

The current TradingView pricing page marks tick intervals as included in Ultimate and excluded from Basic, Essential, Plus, and Premium. The May 2025 announcement also mentioned Expert, but that older plan name is not a promise about present purchases or legacy accounts. Check your account entitlement separately. This page was checked against official documentation on October 16, 2026; no signed-in chart test was performed.

  • On a supported chart, open the interval menu and select a tick preset. A grayed-out tick option can indicate that the symbol has no tick data.
  • A chart-bar ceiling is not a calendar-history guarantee. Record dates instead of assuming that 40,000 bars means a fixed number of days.
CheckDocumented boundaryWhat to record
InstrumentMost symbols; exclusions include options, indices without volume, TVC government bonds/yields, and EOD symbolsThe full exchange-prefixed ticker, not just its short name
IntervalFour presets; custom tick counts are unavailableThe selected interval shown on the chart
HistoryUp to 40,000 bars; continuous futures cover only the current and previous contractsEarliest loaded timestamp and contract identity
Platform and chartWeb/desktop; mobile and tick-based Renko, Kagi, Line Break, and Point & Figure are listed as unsupportedPlatform and chart type
AutomationServer-side tick alerts and Deep Backtesting are listed as unavailableWhether your intended workflow needs either feature

Replay: check the dedicated documentation and your account

TradingView documentation is inconsistent here. Its tick-interval overview still says Bar Replay is unavailable. Its dedicated Bar Replay history article says Ultimate users can replay individual ticks from the most recent seven days, for symbols that support tick intervals. The current pricing page also lists seven days of historical tick data. Use the dedicated replay guidance for this feature, then verify the exact symbol in your account before relying on it.

  • Open Replay, use Select date, and inspect Select the first available day. Record the returned date and any availability message.
  • Keep ordinary chart history, replay history, and strategy backtest coverage as separate records. Access to one does not establish access to the others.
  • If the replay option or expected history is absent, retain the result as an unresolved platform restriction. Do not replace missing ticks with a fabricated historical sequence.

Pine Script timing needs a separate check

Pine supports tick-chart context, but a script written around fixed-duration bars may make assumptions that fail there. The current Chart information manual documents timeframe.isticks for detecting tick intervals and bid/ask values on 1T charts. Those features do not establish compatibility for every indicator, data request, or strategy.

  • Test your exact script on the target chart. Include external-symbol requests, timeframe inputs, session filters, and timestamp-based drawings in that check.
  • Compare a condition while its bar is open, after it closes, and after a reload. Record differences rather than treating a successful compile as proof of identical behavior.
Script assumptionWhy it mattersReview action
The open bar has a known closing timeOn an open realtime tick bar, time_close is na; its closing timestamp becomes available after confirmationHandle missing values; do not build a countdown from an unknown close
A bar length is a durationTen bars need not represent ten minutesState whether a rule uses elapsed time, sessions, or a bar count
A chart signal is an executable alertA displayed condition does not remove the documented server-side alert restrictionVerify the delivery path before building automation
Changing chart interval preserves the experimentDifferent aggregation changes the input seriesSave separate configurations and compare by timestamp

Tick aggregation is not an order-flow classification

Grouping 100 observations into an OHLC bar does not preserve a label for the initiating side of every transaction. A green tick candle says its close exceeds its open; it does not say every trade was buyer-initiated. Volume totals also do not describe resting orders at each price.

  • If your rule needs bid/ask quotes, specify those fields and their availability. Pine documents bid and ask on 1T; that is a different requirement from selecting 100T candles.
  • If your rule needs trade-side volume or order-book depth, verify the relevant data product and its classification method separately. Do not infer either from candle color.

Build a repeatable time-chart baseline

After checking the target tick chart, write down the signal rule before comparing it with a time-based version. Pineify AI Coding Agent can help draft that baseline from a written specification. It does not supply tick history, change TradingView permissions, or make two aggregation methods equivalent.

  • Specify the exact symbol, session, time interval, indicator inputs, and whether signals require a closed bar.
  • Ask for visible signal markers and timestamps so you can compare observations without assuming simulated fills.
  • Use the same overlapping dates for both views. Record unmatched signals, missing history, and differences in confirmation time.
  • If you later add strategy orders, define entry timing, exits, fees, and slippage separately. Treat the time-chart results as their own experiment.
Where Pineify fits

Pine Script AI Coding Agent

Describe a time-chart baseline with explicit session, inputs, and confirmation rules. Review the generated Pine Script and test it in TradingView before comparing signals.

Draft a baseline script

Frequently asked questions

This guide explains chart data and research workflows, not investment advice. Examples are hypothetical. No account-level tick-chart test or trading-performance claim is presented.

Sources and verification

Published by Pineify. Pineify is an independent product and is not affiliated with TradingView. Sources support the technical explanations; examples do not establish trading performance.