PROOF · proof · Updated 2026-11-05 · Derek William Frazier

Why a Backtest Rarely Matches Live Trading Results

A backtest and the live version of the same exact strategy rarely post the same numbers, even when the backtest has no coding errors at all — because a backtest fills every trade at a clean, already-known price with no hesitation, and live trading does neither. The gap isn't a bug to find and fix. It's the cost of moving from a simulation that already knows what happened to an account that has to act before it knows.

That's the direct answer. The rest of this page covers exactly where the gap comes from, why it isn't the same thing as curve-fitting or look-ahead bias, roughly how it tends to show up, and the one practice that narrows it without pretending it can be closed to zero.

PLATE · THE SAME RULE, TWO DIFFERENT ACCOUNTSOne rule, run two ways past the same point in time.real money starts herebacktest — same rule, continued on paper← live — fills, costs, and hesitation all cost somethingThe backtest never pays a real fill, a real cost, or a moment of hesitation.CYCLICAL MARKETS · THE CYCLITECNICAL METHODEducational. Not advice. No performance promise.

What actually changes between a backtest and the live version of the same rule?

Four things, and none of them involve the rule's logic being wrong.

Is this the same thing as curve-fitting or look-ahead bias?

No — and the distinction matters, because the fix for each one is different.

Curve-fitting and look-ahead bias are both ways a backtest can be built wrong: a rule shaped to match history it already knew, or a rule that accidentally used information it wouldn't really have had yet. Fix either one and the backtest becomes more honest about what the strategy could have done.

The backtest-to-live gap is different: it shows up even in a backtest built with zero look-ahead leakage and zero overfitting anywhere in it. Even that kind of backtest only tells you how a rule would have performed inside a simulation that fills every trade cleanly and never hesitates. It was never built to answer "how will this perform when a real account has to act on it" — that's a separate question, and no amount of fixing the backtest's internal logic answers it.

ProblemWhat it meansWhat fixes it
Curve-fittingThe rule was shaped to match this specific historyA genuine walk-forward test on unseen data
Look-ahead biasThe rule used information it wouldn't have had yetPoint-in-time data, checked bar by bar
Backtest-live gapThe simulation never had to pay real costs or hold its nerveForward testing with real (or close to real) execution

A backtest can pass the first two checks completely and still face a real gap once it goes live, because the third problem was never inside the backtest's logic to begin with.

How big does the gap usually run?

There's no fixed number — it depends on how often the strategy trades and how it's actually run. But the direction is consistent enough to plan around:

Can the gap be closed to zero?

No, and treating any backtest number as the live number is the mistake this page exists to head off. What actually narrows the gap is forward testing the exact rule, unchanged, on real or near-real conditions before it's trusted with size — a small live or paper account, run for long enough to generate a real sample, with real fills and real costs recorded rather than assumed.

Forward testing still won't erase the discipline piece entirely — a small test account doesn't carry the same pressure a larger one does — but it converts the fill-and-cost portion of the gap from a guess into a measured number, which is the one part of this that's actually knowable in advance.

Questions traders ask

Does paper trading solve the backtest-to-live gap?

Partly. Paper trading fixes the data-cleanliness problem — it runs on the same real-time, still-arriving data a live account sees — and it can approximate fills and costs reasonably well. It does not fix the discipline problem, because there's no real money attached, and risk-taking behavior reliably changes once an account's balance is actually at stake. Paper trading is a genuine step toward the live number; it isn't the live number.

Why would a backtest with a great Sharpe ratio still disappoint live?

Because a Sharpe ratio computed entirely inside the backtest inherits every one of the backtest's own blind spots — it can look excellent on paper and still be measuring a world with no real fills, no real costs, and no real hesitation built in. A great in-sample statistic says the rule performed well against the simulation it was tested in; it says nothing about how much of that performance survives the move to a real account.

Should every backtest just assume a worse result than it shows?

A flat haircut is a reasonable rough habit, but it's a placeholder for a real forward test, not a substitute for one. How much a given rule degrades depends on its own turnover, the market it trades, and who's actually running it — three things a generic discount can't account for. Treat any backtest number as the ceiling, not the expectation, and replace the guess with a measured forward result as soon as one exists.

Where this fits the bigger picture: a backtest that's free of look-ahead bias and curve-fitting has cleared the internal checks: it is an honest description of its own simulation. Whether that simulation's number survives contact with a real account is a separate question, answered only by trading the rule forward. How this house holds its own graded record to that bar is on the methodology page.

Keep reading

I Graded Four Years of My Own Public Calls. Here's the Scoreboard.How a Trading Educator Should Score Their Own CallsHow to Verify a Trading Guru's CredentialsMy 2022 Posts Beat My 2026 Posts. Badly.
Get our AI tools and everything we send out New AI trading tools and our Claude Code builds, plus session invites. All free.
Get them free