TradingView Backtest & Robustness Lab

How to Export TradingView Strategy Tester Data to CSV

How to Export TradingView Strategy Tester Data to CSV | SG Group
TradingView Backtesting Series · BT02

How to Export TradingView Strategy Tester Data to CSV

The short answer: the download inside the Strategy Tester writes out whatever tab you are currently viewing. If you want to analyze trade by trade, open the List of Trades tab first, then export. This guide walks through the three kinds of CSV you may meet, the export steps, how to fix import errors, and how to load the file into a free Lab.

  • See which tab produces which file
  • Tell strategy, chart and broker CSVs apart
  • Fix garbled text, date shifts and column drift
  • Import into the free Lab in three steps
About 9 min read Updated July 13, 2026 Category: Backtesting in practice

Key takeaways

  • The download writes out the tab you are viewing. For trade-level analysis, choose List of Trades.
  • A chart-data CSV is a price history, not a trade history. Mixing them up makes analysis impossible.
  • Most import errors come down to encoding, delimiter, date format or time zone.
  • Button and column names vary by version and language, so confirm the current labels in the official help before exporting.
Open contents
  1. The bottom line: which tab to export
  2. Three kinds of CSV
  3. How to export the CSV
  4. What each tab gives you
  5. Assumptions to note before exporting
  6. Sample columns and column mapping
  7. Import errors and how to fix them
  8. Pre-export checklist
  9. Load into the free Lab in three steps
  10. What to analyze next
  11. Frequently asked questions
  12. Related reading
  13. Sources and further reading
  14. Disclaimer

The bottom line: which tab to export

The download inside the Strategy Tester writes out the data for the tab you are currently viewing. When you want to analyze each trade’s entry, exit and profit or loss, open the List of Trades tab first, then export. If you only need aggregate KPIs, that is Performance Summary; if you only want a price history, that is a chart-data CSV. Because button names and icons can change by version and language, confirm the current label in the official help just before you export.

Right after you run a backtest in TradingView, it is common to be stuck at “I can open the Strategy Report, but I am not sure which data to export.” The reason is simple: the same download icon produces a completely different file depending on which tab is active. If you want the full picture first, reading the parent article on the complete TradingView backtesting workflow (BT01) makes it easier to see where this lesson fits.

The goal of this guide is to help you pull the right CSV from the right tab, tidy up its encoding and columns, and move on to external analysis. From here we work through the differences between the three kinds of CSV and resolve, one at a time, the places where people most often get stuck.

Three kinds of CSV

The CSV files you can obtain around TradingView fall broadly into three kinds. Their names look similar, but their contents and uses differ, so separating them at the outset saves confusion later.

Backtest trade detail

Strategy-report CSV

The KPIs and trade detail produced by the Strategy Tester. From the List of Trades tab you get one row per trade.

Best for trade analysis
Price time series

Chart-data CSV

Prices over time (OHLC and volume). Useful for reading market conditions, but it contains no record of trades.

Not suited to trade analysis
Live account fills

Broker trading-data CSV

Execution history from a live or paper account. Good for recording real activity, but it is a different file from a backtest result.

Separate from a backtest
Table 1: The three kinds of CSV (use and contents compared)
Kind Main contents Export source Trade-level analysis
Strategy-report CSV KPI aggregates / trade detail (tab-dependent) Strategy Tester Possible (choose List of Trades)
Chart-data CSV Prices over time (OHLC, volume) Chart export Not possible (no trade history)
Broker trading-data CSV Fills from a live or paper account Trading panel / account history For real-activity records (separate data)

In short, when you want to analyze backtest trades, the file to choose is the List of Trades from the strategy-report CSV. Everything below assumes this file.

How to export the CSV

The overall flow has four stages: open the strategy, show the Strategy Tester, choose the tab, download, and then load into the Lab. Let us fix the big picture with a diagram first.

Conceptual diagram (not a reproduction of the actual screen)
Four-stage flow from CSV export to loading into the Lab An abstract diagram connecting four stages left to right with arrows: choose a tab, download, the CSV file, and loading into the analysis Lab. 1. Choose a tab List of Trades 2. Download exports the active tab 3. CSV / XLSX check encoding & columns 4. Load into the Lab map columns → analyze Export source: Strategy Tester
Figure 1: The four stages from choosing a tab to loading into the Lab. Because the download follows the active tab, the key is to choose the tab first.
  1. Apply the strategy to the chart

    Add your strategy to the chart and set the symbol, timeframe and period as you intend. The conditions you pick here become the assumptions baked into the CSV.

  2. Open the Strategy Tester panel

    Show the Strategy Tester below the chart. Tabs such as Performance Summary, Trades Analysis and List of Trades sit side by side.

  3. Choose the tab you need

    If you want per-trade detail, open List of Trades. The download exports the active tab, so this choice matters most.

  4. Download and check the contents

    Use the download control at the top of the panel to save the CSV (XLSX in some environments). Once it opens, confirm that the encoding, delimiter and date format are what you expected. Because button names and export formats can change, confirm the current label in the official help on exporting strategy data.

What each tab gives you

Each tab in the Strategy Tester differs in granularity and purpose. Choose the tab according to what you want to analyze. The example below uses fictional, illustrative data.

Table 2: Main tabs and what they provide (figures are fictional, illustrative data)
Tab Granularity Example output (fictional) Main use
Performance Summary Overall aggregate 128 trades · PF 1.42 · Max DD -8.6% Grasp the strategy at a glance
Trades Analysis Grouped aggregate Win rate 57.8% · Avg profit +1,425 See the breakdown of wins and losses
List of Trades Per trade 128-row detail (entry/exit, P&L, cumulative) Use for detailed external analysis

Performance Summary is convenient for the overall picture, but because it has no detail you cannot study the sequence of losing streaks or verify individual trades. Per-trade analysis needs List of Trades. How to read each KPI itself is covered in depth in the guide to profit factor, expectancy and other metrics (BT03).

Assumptions to note before exporting

A CSV may look like a string of numbers, yet you cannot interpret it correctly without knowing the assumptions behind it. Before you open the file, note the following. Each one is essential for reproducing or comparing the backtest conditions.

  • Period: the start and end dates. A sample that is too short is easily swayed by chance.
  • Symbol and timeframe: for example, USD/JPY on the 1-hour (H1) timeframe (fictional).
  • Position currency and initial capital: the unit of profit and loss and the basis for percentages.
  • Order sizing: fixed, percentage or compounding. It changes what a profit figure means.
  • Commission and slippage: whether they are included changes profit and loss substantially.
  • Time zone: whether times are on the chart or the exchange clock.

Cost assumptions move the result

A backtest that leaves out commission and slippage tends to look better than live trading. How to apply them and how to stress-test them is covered in modeling slippage, spread and fees (BT09).

Sample columns and column mapping

A List of Trades CSV lines up columns such as trade number, type, date and time, price, quantity and profit or loss. Because column names can vary by version and language, they cannot be asserted as a fixed specification. The Lab supports generic column mapping, so you can map the original CSV columns to analysis fields and load the file.

Column names can vary by environment (example)
Mapping TradingView columns to analysis fields A diagram with typical TradingView CSV columns on the left and the Lab’s generic fields on the right, with lines connecting the corresponding items. TradingView columns (example) Analysis fields Trade # Type / Signal Date / Time Price Contracts Profit / Cumulative trade_id side (buy / sell) time (entry / exit) price size (quantity) pnl / cum_pnl
Figure 2: Example of mapping typical TradingView columns to analysis fields. Run-up can be treated as MFE and Drawdown as MAE. Even if column names differ, assigning each to the field with matching meaning lets the file load.

If the file has Run-up (the peak of unrealized profit) and Drawdown (the trough of unrealized loss) columns, you can use them to analyze exit efficiency. This angle is also touched on in the overview of the backtesting workflow (BT01). Even when column names differ from what you expected, mapping each one manually to the analysis field with matching meaning is all it takes.

Import errors and how to fix them

The CSV will not load, the columns drift, the text is garbled — most of these come down to one of the following. Working through them in order resolves nearly every case.

Triage flow (conceptual diagram)
Yes/No triage flow for import errors A branching diagram that steps through garbled text, misaligned columns and abnormal row counts with Yes and No, arriving at a fix for each. Import error Garbled text?Yes → re-save as UTF-8 Columns misaligned?Yes → match the delimiter Row count off?Yes → check blank rows & open trades No → import succeeded
Figure 3: Triage. Checking in the order encoding → delimiter → row count helps you pinpoint the cause quickly.

Common causes and fixes

  • Encoding: anything other than UTF-8 shows as garbled text. Re-save as UTF-8 (with BOM if needed).
  • Delimiter: a comma versus a semicolon makes columns drift. Specify the delimiter when you import.
  • Decimal mark: a period versus a comma (regional settings). If numbers break, check the decimal notation.
  • Date format: the order of year, month and day, or a time-zone difference. State the format explicitly on import.
  • Blank rows and duplicates: a trailing blank row or a repeated header creates a row-count mismatch.
  • Open trades: a trade left open at the end of the period has no finalized profit or loss — keep that in mind.
  • Multiple files and changed headers: watch for naive merging of files with different assumptions, and for column names that change by language.

Pre-export checklist

We provide the pre-import checks both as a static table and as an interactive checklist. Everything is tallied on this device only; no file or entered value is ever sent over the network.

Table 3: Pre-export checks (static version, an alternative to the checklist)
CategoryCheck
TabConfirmed the export source is List of Trades
AssumptionsNoted the period, symbol and timeframe
AssumptionsNoted the position currency and initial capital
AssumptionsNoted the order sizing (fixed / percent / compounding)
CostNoted the commission and slippage settings
TimeChecked the time zone (chart / exchange)
FormatChecked that the encoding is UTF-8
FormatChecked the delimiter (comma / semicolon)
IntegrityChecked for open (unclosed) trades
SafetyRemoved personal data and unnecessary columns

Interactive pre-export check

Tick each item you have confirmed and the “ready” and “check again” counts update. Nothing is submitted.

11 items total

Tick each item you have confirmed (currently 0 / 11).

Load into the free Lab in three steps

Once the assumptions and the file are in order, load the CSV or XLSX into SG Group’s TradingView Backtest & Robustness Lab. The free plan lets you try core KPIs, equity and drawdown, Monte Carlo and stress tests, with no cap on the number of runs (the free scope can change, so confirm the latest on the plan page).

  1. Load the file

    Drag and drop the List of Trades CSV or XLSX into the Lab. Removing personal data and unnecessary columns before uploading gives you peace of mind.

  2. Map the columns

    With generic column mapping, assign date and time, type, price, quantity and profit or loss to the analysis fields. Even if names differ, you can map by meaning.

  3. Review the analysis

    KPIs, the equity curve, drawdown, Monte Carlo and more appear automatically. Compare files with different assumptions separately so you do not misread the results.

Keep your noted assumptions and go straight to a free analysis

Load your List of Trades CSV and the Lab visualizes KPIs, equity, drawdown and Monte Carlo in line with the assumptions you just confirmed. Start with the basic analysis for free, then move to saving, comparison and deeper diagnostics when you need them.

What to analyze next

Once the CSV loads, the next task is interpreting what is inside. Reading the following in this order lets you check the reliability of a backtest step by step.

For all of these, the List of Trades CSV you exported in this guide is enough to review straight away in the free Lab.

Frequently asked questions

Where can I export TradingView backtest results?
You export them from the Strategy Tester panel that appears below a chart once a strategy is applied. The download control at the top of that panel writes out the data for the tab you are currently viewing, so if you want trade-level analysis, open the List of Trades tab before you download. Button names and icons can change by version and language, so confirm the current label in the official help before exporting.
Should I export List of Trades or Performance Summary?
Export List of Trades when you want to study each trade’s entry, exit and profit or loss. Performance Summary is a table of already-aggregated KPIs; it is handy for the big picture but does not contain a row per trade. Most diagnostics in the Lab expect trade-level detail, so List of Trades is the export to start with.
Can I use a chart-data CSV for trade analysis?
A chart-data CSV is a series of prices over time (OHLC), not a record of trades, so it is not suited to trade-level analysis. To review profit, loss and losing streaks, use the List of Trades from the Strategy Tester instead. Chart data is useful for understanding market conditions, but it is a different file from a backtest’s trade detail.
What should I do when a CSV shows garbled text?
In most cases the file is being opened with an encoding other than UTF-8. In your spreadsheet software, import it again with the encoding set to UTF-8 (with BOM if needed), or re-save the file as UTF-8. Checking whether the delimiter is a comma or a semicolon at the same time often clears up misaligned columns as well.
Why are the dates or times shifted?
The usual causes are a time-zone difference and how the date format is interpreted. TradingView’s display depends on the chart or exchange time zone, so the timestamps in the CSV may differ from your local time. The order of year, month and day (such as YYYY-MM-DD) can also be re-read differently across environments, so state the date format and time zone explicitly when you import to keep everything consistent.
Can I analyze several CSV files together?
Yes, the Lab can load multiple files. That said, simply merging files whose assumptions differ — symbol, timeframe, period or initial capital — makes them easy to misread, so it is safer to align the assumptions or to compare the analyses separately. More advanced work that compares across symbols and timeframes is available on the higher plans.
Is XLSX supported?
Yes, the free plan reads XLSX in addition to CSV. You can import a file you have tidied up in a spreadsheet as-is, but extra sheets, formatting and merged cells can interfere with column recognition, so importing is more reliable when the detail sits on a single, clean sheet.
Does simply importing a CSV tell me whether to buy or sell?
No. The Lab is a descriptive tool that aggregates, visualizes and diagnoses the backtest results you load; it does not provide trading signals, investment advice or forecasts of future prices. What a CSV shows is behavior on past data, which does not guarantee future results. Outputs change with the assumptions, the data and the costs you apply.

Sources and further reading

TradingView button names, specifications and plan contents may change. Confirm the current labels in the official help before you act. For SG Group features and free scope, the current plan page takes precedence.

Disclaimer

  • This article and the Lab are for education and information, aimed at the descriptive analysis and visualization of the backtest results you load; they are not investment advice, trading signals or forecasts of future prices.
  • All figures in the text, figures and tables are fictional, illustrative data. They do not represent any real performance, user numbers or win rates.
  • Backtest results are based on past data and do not guarantee future results. Outcomes change with differences in assumptions, data and costs such as commission and slippage.
  • We do not recommend any particular instrument, quantity or parameter. Make individual investment decisions at your own responsibility.
  • This article does not indicate any partnership, certification or endorsement with TradingView. Trademarks belong to their respective owners.