How to Export TradingView Strategy Tester Results (2026)

To export TradingView Strategy Tester results, open the strategy report below your chart, go to the Trades tab and click the Download icon next to Column setup: that saves the List of Trades as a CSV file. To export the whole report (metrics, trades and properties) instead, choose "Download data as XLSX" from the strategy report's menu; both exports need the Essential plan or higher as of October 2026.

Older guides disagree on the format (some say CSV, some XLSX) and on which plans can export. Both formats exist, and they do different jobs. This guide settles the details from TradingView's own documentation, explains every column in the trade list, lists the problems people hit, and covers what to do with the file once you have it.

Where the export buttons are

The Strategy Tester is now called the strategy report in TradingView's documentation. It opens in the panel below the chart whenever a strategy is on the chart, and it has two main sub-tabs: Metrics and Trades.

To export the List of Trades as CSV:

1. Add your strategy to the chart and wait for the report to finish calculating.
2. In the report, switch to the Trades tab.
3. Above the top-right edge of the list, find the Column setup icon. The Download icon sits next to it.
4. Click Download. The browser saves a CSV file.

To export the full report as XLSX:

1. Open the strategy report.
2. Open the report's menu (the context menu at the top of the report).
3. Choose Download data as XLSX.

TradingView's Pine Script strategies documentation describes both: the Download icon "download all available data for the list as a CSV file", and the XLSX option downloads "all applicable data" from the report's sub-tabs. The XLSX file also includes the Properties tab data (initial capital, order size, commission, slippage and so on), which makes it the better file to archive alongside a strategy version.

CSV or XLSX: which one do you need?

TradingView's older help page, How to export strategy data, says each tab exports separately and only mentions CSV. The current Pine Script documentation and the pricing page list both formats, so the safest reading as of October 2026 is: CSV for the trade list, XLSX for the whole report.

If you only want to analyse trades, use the CSV. It is simpler to parse and most import tools expect it.

Which TradingView plan can export?

TradingView's plan comparison lists "Export trades in CSV" and "Export report in XLSX" as separate features. As of October 2026 the comparison table shows:

Third-party guides from earlier years quote different plan requirements. Plans change, so check the pricing page if you are reading this much later.

The 9,000 trade limit and Deep Backtesting

With the default testing range, a strategy keeps individual data for only the latest 9,000 trades. TradingView's documentation says trimmed trades are not visible "in the strategy report interface or any downloaded XLSX or CSV files". The Metrics tab still counts them, so your summary profit factor can be based on more trades than your export contains.

If your strategy has more than 9,000 trades in the default range, choose a different testing period from the menu at the top of the report. That switches the report into Deep Backtesting mode, which keeps individual data for all trades in the range. Deep Backtesting needs Premium or Ultimate.

Two things to know about Deep Backtesting:

• It only changes the testing range of the report. Trade markers, plots and alerts on the chart still use the chart's loaded data.
• You can't click a trade in the list to scroll the chart to it while it's active.

What each column in the List of Trades means

TradingView documents these columns for the Trades tab. The CSV contains all of them, whatever you have switched off in Column setup. The exact header text in the file has changed between TradingView versions (older files say things like "Profit" and "Run-up"), so match on meaning rather than exact names if you write a script.

The excursion columns are the most underused. They show how far price went for and against each trade, which is the raw material for MAE and MFE analysis.

Time zones: check before you analyse

TradingView's help centre says the List of Trades date and time is "the transaction time in the chart's time zone". Change the chart's time zone and the times in the list change with it.

Before exporting, set the chart to the time zone you want to analyse in, usually the exchange's time zone or UTC, and write it down. If you later group trades by hour or session, a one-hour offset will put trades in the wrong bucket, and daylight saving changes make it worse. After exporting, compare two or three rows in the file with the list on screen to confirm they match.

Common export problems

• The Download icon is missing. You are probably on the Basic plan. Exports need Essential or higher.
• The file has fewer trades than the Metrics tab says. The 9,000 trade limit trimmed the oldest trades. Use a custom testing range with Deep Backtesting, or shorten the range and export in parts.
• Each trade appears twice. The CSV has usually listed the entry and the exit as separate rows with the same trade number. Filter on the Type column, or combine the two rows so each trade has one entry time and one result.
• Excel shows dates as text or mixes up day and month. Import the CSV through Excel's data import (or Google Sheets' import) and set the date column's format explicitly, rather than double-clicking the file.
• Results differ from yesterday's export. Historical data can be revised and new bars extend the range. Save the XLSX with each strategy version so you can compare like with like.
• Numbers don't match after you filter trades. The Cumulative PnL column is the original running total. Recalculate it from the Return column for any subset.

What to do with the file next

The Metrics tab gives you one profit factor and one win rate for the whole history. The export is where you find out what's behind those numbers: which sessions, weekdays, hours and volatility levels make the money, and which give it back.

A good next step is to break the trades down by condition. How to analyse a TradingView backtest walks through doing it in a spreadsheet with formulas, including the minimum trade count each bucket needs before you act on it. Before you trust any slice, check it has enough trades using the method in how many trades a backtest needs.

If you'd rather not build the spreadsheet, Tessera imports the TradingView Strategy Tester CSV directly and breaks the trades down by session, weekday, time of day, volatility and symbol, with the trade count behind each slice. Rules you test there can be composed into a copy of your Pine Script to paste back into TradingView and re-backtest, which is what the strategies page covers.

Get a free breakdown of your export

Upload your List of Trades CSV to the free Entry Analysis report and see your strategy's results split by market condition. No card needed.

Strategy Tester exports load into Tessera's algo trading journal alongside live trades, kept in a separate account so backtest and real fills don't mix. See the full list of supported brokers and platforms.