Since 15 September 2026, TradingView lets you move the tables a Pine script draws off the price chart and into a panel below it. Right-click a table and choose Move tables to bottom panel: every table from that indicator moves into its own tab under the chart, and you can send it back at any time.
The change is about where the table is displayed. TradingView describes placement, not a change to what the script calculates or to how its alerts work, and this article does not assume one. It explains how to use the panel to review a script's output with the candles visible, and what a table can and cannot tell you when the script feeds an automated workflow.
What changed
TradingView announced the feature on 15 September 2026 (the post was updated on 17 September 2026)[1]. Pine scripts have long used tables for strategy metrics, screener-style reports and custom statistics. The announcement names the problem as placement: a table drawn on the chart takes up space and can cover the candles you are trying to read[1].
A table sits where the script puts it. The Pine Script manual explains that tables are not tied to particular bars; they float in the script's display area, anchored to one of nine positions such as the top-right corner[2]. On a busy chart, the corner a script uses can be exactly where the most recent candles are.
What you can now do, according to the announcement[1]:
- Right-click a table and select Move tables to bottom panel. Every table drawn by that indicator leaves the chart and is drawn in a separate tab in a panel below it. The same option is in the More menu.
- Use it with any script that uses Pine's table functionality, and move more than one script into the panel at once.
- Use the panel's context menu to switch between the indicators you have moved, or to send a script's tables back to the chart.
The bottom panel is a different feature from the manual Table drawing tool that TradingView added on 10 January 2025, which lets you type your own notes into a table on the chart[3]. The panel is for tables a Pine script creates.
A review workflow that keeps the candles visible
The panel is most useful when a script's table tells you something you want to read alongside the latest price action, such as a strategy's current state or the level a script would use for a stop.
- Add the script to the chart and open its table as usual.
- Right-click the table and choose Move tables to bottom panel. All of that indicator's tables move together.
- If you run several table-drawing scripts, move each one and switch between them from the panel's context menu.
- Read the table against the most recent bars, now that nothing covers them.
- Send the tables back to the chart from the same menu when you want the original layout.
What a table can confirm, and what it cannot
Wherever a table is displayed, it shows what the script drew on its last execution, on the last bar of the dataset. Its contents do not change as you move the cursor over earlier bars, unlike the values in the Data Window[2].
A table is not limited to current values, though. A script can calculate over past bars and write the results into cells, or keep its own record, such as a rolling history or a trade log, and display it. The Pine Script manual's own heatmap example colours a row of cells by how the current price compares with its past values over a lookback period[2]. A table shows history when its author programmed it to. What it never shows by itself is what an alert sent or what happened at the broker.
- What the script calculates on the latest bar, with the chart's current inputs. The table can show it, if the script's author put that value in a cell.
- What happened on earlier bars. Only if the script stores that history and writes it into the table. Otherwise use the Data Window or the script's plotted values.
- What a running alert sent. Not from the table. An alert runs on a saved snapshot of the script and inputs; read the message in TradingView's Alerts log.
- Whether PineConnector received and processed the message. Not from the table. Check PineConnector's Bridge (signal log).
- What the broker did. Not from the table. Check three things separately in MetaTrader: whether the order was accepted, whether a deal was filled, and whether a position is open with its stop. MetaTrader's help treats the order, the resulting deal and the position as distinct records[7].
The alert point catches people out. TradingView's Pine Script FAQ explains that creating an alert saves a snapshot of the script, its inputs and the chart's context, and that later changes to any of them do not affect the alert already created[4]. If you change an input and the table updates, an alert created earlier still runs the old version. The fix is covered in why an alert keeps using old settings.
PineConnector's guidance draws the same line between what you see and what happened: a chart marker, a simulated strategy fill and a broker trade are different events[5]. A value in a table belongs with the chart marker.
If you write your own scripts, a table is still a convenient place to display the inputs to an alert message, for example the stop price the script would include. That lets you compare what the script shows now with what the Alerts log recorded when the alert fired. The two can differ for the snapshot reason above.
Limitations and common mistakes
- Reading a display change as a logic change. The announcement describes where tables are drawn. It does not say calculations, alert conditions or alert messages change, so do not expect different signals after moving a table.
- Using a table as a trade record. A table shows what the script drew on your chart. It does not confirm that a message was sent or received, that an order was accepted, that a deal was filled or that a position is open.
- Expecting the table to follow the cursor. Table contents stay as drawn on the last bar when you hover over earlier bars. A table shows past values only if the script was written to store and display them.
- Confusing the two table features. The Table drawing tool holds notes you type. The bottom panel moves tables that Pine scripts draw.
What to check when a table and a trade disagree
- Note the value the table shows now, and the time.
- Find the corresponding entry in TradingView's Alerts log and read the message it actually sent.
- If the alert was created before your last script or input change, recreate it from the updated chart.
- Find the same event in PineConnector's Bridge, then check the broker account: whether the order was accepted, whether a deal was filled and whether the position is open with its stop. PineConnector's troubleshooting guide walks through each checkpoint in order[6].
Reviewed 23 September 2026. Facts were checked against the linked sources on that date. The layout diagram is illustrative; no script or alert was run for this article.
Related reading
- TradingView updates for alert-based automation: a practical index
- I changed my Pine Script, but the alert still uses the old settings
- Pine Script alert() function: automate strategy signals
- From a TradingView backtest to a verified demo trade
- A comprehensive guide to Pine Script for TradingView
Sources
- TradingView Blog – Visualize indicator tables below the chart, published 15 September 2026, updated 17 September 2026, accessed 23 September 2026.
- TradingView – Pine Script User Manual, Visuals: Tables, accessed 23 September 2026.
- TradingView Blog – Organize your analysis with the Table drawing tool, published 10 January 2025, updated 24 October 2025, accessed 23 September 2026.
- TradingView – Pine Script documentation, FAQ: Alerts, accessed 23 September 2026.
- PineConnector Docs – Best Practices & Tips, accessed 23 September 2026.
- PineConnector Docs – Troubleshoot an alert, accessed 23 September 2026.
- MetaTrader 5 Help – Trading operations: basic principles, accessed 23 September 2026.
PineConnector executes the instructions you send it. It does not select trades, manage money, or hold funds. Trading carries risk, and past performance of any strategy does not indicate future results.
