TradingView footprint charts: reading and limits

What the buy and sell labels measure

TradingView assigns intrabar volume by price direction: rising intrabars are buy, falling intrabars are sell. An unchanged intrabar uses the previous close, then the previous classification if needed. This is a price-based classification of supplied volume, not a transaction-by-transaction aggressor-side record.

• A positive delta supports the statement that classified buy volume exceeded classified sell volume. It does not prove that institutions accumulated a position.
• Resting limit orders, cancellations, and queue position are different data. A footprint volume row does not reconstruct the order book.
• If a rule specifically requires trades executed at the bid or ask, verify that data and its trade-side methodology independently. Do not rename an up/down estimate to satisfy that requirement.

Work through one hypothetical footprint

Assume a minimum tick of 0.25, one tick per row, and an imbalance threshold of 300%. The quantities below are invented volume units for a calculation exercise. Rows are shown from highest to lowest price; they are not a market screenshot.

• Bar delta is 230 - 150 = +80. Delta as a share of total volume is 80 / 380 × 100 = 21.05%. The middle row is the point of control (POC) because its total of 180 is the largest.
• For the middle row, compare buy 150 with sell 40 in the row below. The ratio is 3.75, above the chosen 3.00 threshold. Comparing 150 with the same-row sell value of 30 would answer a different question.
• The upper row compares buy 60 with sell 30 below: 2.00, below the threshold. A positive bar delta therefore does not imply a buy imbalance at every row.
• Repeat this calculation with your recorded rows before turning a visual pattern into a condition. Changing row width changes the groups being compared.

Set up the native chart and record the configuration

Select Volume footprint from the chart-type menu, then open Chart settings. The official screenshot below shows the native controls, including automatic row sizing. It documents the interface; it is not a signed-in account test performed for this guide.

• For the calculation exercise, choose manual sizing with one tick per row, a buy/sell display, and a 300% imbalance threshold. Record any setting the account does not expose.
• Save the full exchange-prefixed symbol, chart interval, session, timestamp, and all calculation settings alongside the chart image. A short ticker name alone is an incomplete record.
• Compare the same closed bar in the native chart and your script. Check row boundaries before investigating differences in the volumes.

What Pine Script can request

The current Pine manual allows request.footprint() for Premium and Ultimate accounts. It returns a footprint object or na when a bar has no footprint. Check for na before accessing its methods; missing data is not zero volume.

• An ordinary lower-timeframe volume estimate is a separate implementation. Label its source and classification instead of presenting it as an identical fallback.
• An account permission failure and a missing footprint on one bar require different responses. Log the actual message or missing-data state before changing the calculation.

Keep historical comparisons reproducible

Historical footprints can use coarser intrabars as finer data runs out. TradingView documents repainting when calculation granularity changes between realtime and historical views. On daily or higher intervals, intraday-derived footprint totals can also differ from end-of-day volume feeds.

• Capture a bar after close, reload the chart later, and compare its rows and imbalance flags. Preserve both observations if they differ.
• Use fixed manual row sizing for the comparison and record the exact value. Automatic sizing introduces another setting to reconcile.
• Do not fill unavailable history with zeros or assume that all visible dates use equal precision. Record the earliest usable footprint and exclude missing observations from any signal count.
• A test of a chart condition still needs separate execution assumptions before it becomes a strategy test: entry timing, exits, position size, fees, and slippage.

Specify an observable condition before coding

Pineify AI Coding Agent can help translate a written condition into Pine Script. Start with the fields your TradingView account can retrieve. Keep observations without a verified programmatic field in a manual review log.