How to Export TradingView Strategy Results to CSV
First choose the data you need: individual trades, a strategy summary or parameter-search results. These files have different row meanings. This guide covers the TradingView export and the separate Pineify extension export, then shows how to preserve their structure in Excel or Python.
Export a Single TradingView Strategy Run
- Add the strategy to the intended chart. Confirm the active script, symbol, timeframe, date range and simulation properties, then wait for the report to finish.
- Open its Trades or List of trades view when you need entry and exit records. For a summary-only task, choose the metrics view instead.
- Use Download where CSV is offered. In the current report, the context menu can also offer Download data as XLSX. Keep the original workbook if you convert a worksheet to CSV.
- Open a copy and reconcile a small sample against the platform. Save a companion note with script version, capital, currency, commissions, slippage and report scope; those settings may not all appear in every export.
Understand the Three Export Types
TradingView trade-list exports contain the records needed to examine entries, exits and trade outcomes. A performance-summary export contains aggregate metrics. The official CSV instructions export the selected tab separately; the current strategy report also offers Download data as XLSX. Available controls and access depend on your account and report interface.
Pineify Supercharged exports parameter-search results from its Results view. Each row represents a tested setting with captured summary values. Current collected fields include netProfit, netProfitPercent, totalTrades, winRate, profitFactor, maxDrawdown, maxDrawdownPercent, avgTrade and avgTradePercent. Actual export columns are taken from the first stored row, so inspect the header rather than assuming additional fields exist.
When parameter configuration is available, the file begins with Parameters, status, type and value/range rows before a Results section. The table header begins with #; an interval field is named tradingview_interval. Keep this metadata with the run, but separate it from the rectangular results table when importing into tools that expect one header row.
Analyzing in Excel
Use the spreadsheet import preview instead of assuming that opening a file preserved its types. Check quoted commas, decimal separators, blank fields and dates. With a report XLSX, select the trade worksheet before saving CSV; renaming the file extension does not convert the workbook.
For trade data, reconcile trade IDs, completed trade count and summed net P&L with the original report. Entry and exit records may occupy separate rows, so CSV row count is not necessarily trade count. Confirm currency, costs, open positions and partial exits before accepting any aggregate.
For parameter results, keep all other experimental settings fixed while comparing a range. A pivot table or scatter plot can reveal local sensitivity, but an isolated high profit factor is not proof of a better strategy. Set screening criteria before evaluating the sample and reserve a separate period for testing; no universal 30-trade or 10% drawdown cutoff applies.
Analyzing in Python
The pandas.read_csv documentation describes header, skiprows, dtype, encoding and date handling. Inspect the downloaded file first. For a Pineify parameter export with a preamble, locate the actual Results header or extract that table into a separate file before loading it.
Validate imported column names, row count, missing values and numeric conversion before grouping. Keep parameter types explicit: a checkbox, dropdown label and numeric input are different variables. Do not silently coerce failed parses into zero or remove failed runs without recording what was excluded.
Summary rows cannot reconstruct a trade sequence, intratrade drawdown or the path needed for trade-level bootstrap analysis. For those tasks, export the underlying trade records for the selected setting. Pineify Backtest Deep Report expects a compatible TradingView trade CSV, not the optimizer Results table.
When merging runs, add a run identifier and preserve symbol, timeframe, date range, script version, capital, costs and search ranges. Compare matching experimental conditions. Averaging across assets or periods can conceal an interaction, while repeatedly selecting the best observed region increases the risk of fitting the sample.
FAQ
Sources and Format Checks
- TradingView CSV export instructions explain the per-tab export.
- TradingView strategy report documentation describes current report tabs and XLSX export.
- Pineify extension result columns, optional parameter preamble and access requirements were checked against the current implementation on October 21, 2026. File-format inspection does not verify the strategy or demonstrate trading performance.
Choose the Export for Your Task
Use TradingView native export for a single strategy report. For a parameter search, Pineify Strategy Optimizer provides a separate extension workflow requiring Advanced-or-higher access; installing the extension does not grant that plan entitlement.
View the Extension