"Deep Backtesting" means two different things, and TradingView's pricing page only gates one of them. The first meaning is more history: running the Strategy Tester over an extended historical range, which TradingView locks behind a higher-tier plan. The second meaning is more analysis: extracting more insight per trade from the backtest you already have — hour-by-hour attribution, Sharpe and Sortino ratios, stability scoring across rolling windows. That second kind of depth doesn't live behind any TradingView paywall, because it happens after export. This guide covers what the plan limits actually restrict, and how to get analytical depth from any Strategy Tester export on any plan.
What TradingView's plan tiers actually limit
Two constraints matter for backtesters:
- Bar history. Basic plans limit how many bars of history load onto the chart, and the Strategy Tester can only process bars that are loaded. On low timeframes this is the binding constraint — a 1-minute strategy may only see a few months of data.
- Deep Backtesting mode. The extended-historical-range mode requires a higher-tier TradingView plan. Without it, your backtest window is whatever the standard tester loads.
Here's the part that matters for this guide: the .xlsx export always covers whatever the tester actually ran. If your plan gave the tester 18 months of 5-minute bars, the export contains every trade from those 18 months, with full entry/exit timestamps, prices, P&L, and excursion data. The export is not a degraded summary on cheaper plans — it's the complete trade-level record of the test that ran. The ceiling on history is plan-gated; the ceiling on analysis is entirely up to what you do with the file.
Honest framing: what post-export analysis can and can't replace
Let's be clear about what this approach does not do: no amount of post-export analysis manufactures history you never tested. If your strategy needs validation across the 2020 volatility regime and your plan's bar limit starts in 2024, deeper analytics won't conjure those years. What post-export analysis does do is extract far more signal from the sample you have — and in practice, most traders are leaving the majority of that signal on the table. The Strategy Tester report shows aggregates; the trade list supports questions the report never answers.
Depth axis 1: hour-by-hour attribution
The tester reports one net profit for the entire session. Bucketing trades by entry hour shows you where in the day the P&L actually came from — and it's common to find that a strategy's profits concentrate in two or three hours while other hours quietly subtract. That's a structural fact about the sample that a whole-session aggregate cannot express, whatever plan produced it. The full method, including the rolling-window persistence test that separates real hourly patterns from lucky ones, is in How to Find Your Strategy's Most Profitable Trading Hours.
Depth axis 2: risk-adjusted metrics the report omits
The Strategy Tester gives you net profit, drawdown, profit factor, and win rate. From the same trade list you can also compute Sharpe (return per unit of total volatility) and Sortino (return per unit of downside volatility) — and the gap between them describes the shape of your strategy's volatility in a way nothing in the standard report does. A Sortino well above Sharpe means the wobble is mostly upside; near-equal values mean symmetric chop. What each metric means, and the order to read them in, is covered in TradingView Backtest Metrics Explained.
Depth axis 3: stability scoring across rolling windows
This is the analysis most worth having and least available anywhere in TradingView at any price. Aggregate numbers can't tell you whether a strategy's edge was persistent or concentrated. Slicing history into rolling windows (1, 3, and 6 months) and measuring the share of windows in which each entry hour was net profitable — its Stability % — converts "this hour made $3,000" into "this hour was profitable in 9 of 10 windows" (persistent, 90%) or "in 3 of 10" (inconsistent, likely one lucky stretch). As descriptive bands: >70% persistent, 40–70% mixed, <40% inconsistent. A backtest whose profits score high on stability is describing a very different historical record than one with identical totals and low stability — even though the Strategy Tester report for both looks the same.
The workflow, end to end
- Run the strategy on your chart; the Strategy Tester panel appears at the bottom.
- Export to .xlsx via the tester's export control. Watch for the standard traps — no timezone metadata in the file, open positions written as fake exit rows dated at export time. Details in the export guide.
- Analyze the trade list — in a spreadsheet if you enjoy that kind of plumbing, or with a purpose-built tool.
For step 3, the fastest zero-commitment option is to run your export through the free instant report: no signup, the file is processed in memory and never stored, and you get win rate, profit factor, max drawdown, average win/loss, P&L by entry hour, and a best-hour stability teaser in seconds. From there, the analytical tiers stack roughly along the three depth axes above: a free account adds core charts, risk metrics, and CSV export (plus a one-click sample dataset with the Pro heatmap unlocked so you can see the stability analysis before paying anything); Plus ($9/mo) adds Active Window Analysis — hour-filter scenarios with an equity curve per scenario — and PDF export; Pro ($19/mo) adds the full Rolling Window stability heatmap across 1/3/6-month windows, multi-strategy comparison, AI-generated statistical summaries, and Excel export. Both paid tiers have a 7-day free trial.
One caveat that applies to hour-filter scenarios specifically, on any tool: filtering a backtest by hour after the fact is path-dependent. Positions interact across hours, so a strategy actually restricted to certain hours live may behave differently than the filtered historical subset suggests. DataViz Studio displays this disclaimer in-app; it belongs in your mental model too.
Depth axis 4: distribution and directional decomposition
Two smaller but genuinely useful reads come almost free once the trade list is parsed. First, the distribution of trade returns: whether the P&L is a smooth cluster around a modest mean or a barbell of scratches and outliers is invisible in averages but obvious in a histogram, and it changes how much weight the headline totals deserve. Second, the long/short decomposition: splitting every metric by trade direction regularly reveals that a combined report is averaging a strong side with a side that only subtracted. Neither view requires more history — both are extractions from data the tester already produced.
Making a limited sample work harder
If you are on a basic plan and the bar limit genuinely constrains your history, a few practices raise the informational value of what you have:
- Test on a higher timeframe where feasible. The same bar budget covers far more calendar time on 15-minute bars than 1-minute bars.
- Weight stability over totals. With a shorter sample, persistence measurements matter even more — a pattern present in most windows of a short sample is a stronger description than a big total driven by one week.
- Re-export periodically and compare. As new data accrues, exporting again and watching whether the hourly signature and stability scores hold is a rolling out-of-sample check you can run on any plan.
- Mind the trade count. Statistical descriptions of 40 trades are anecdotes. Be honest with yourself about sample size regardless of how deep the analysis layer is.
The bottom line: TradingView's premium tiers sell you a longer test. What most backtests are actually starving for is a deeper read of the test they already ran — attribution, risk-adjustment, and persistence. That layer starts with a thirty-second export, and it works the same on every plan.