EA Backtest vs Live Results: Why the Numbers Never Match (From an EA Vendor)
Key takeaways
- No backtest survives contact with a live feed. Spread, slippage, commission, swap and tick quality all diverge in the same direction: against you.
- The peak of an optimization is the configuration most contaminated by luck. Demand out-of-sample validation and stable parameter regions, not record runs.
- Read backtest drawdown against prop firm style limits, and assume live drawdown will eventually run deeper than the report admits.
- Red flags that end the conversation: near-perfect curves, win rates near 99 percent, demo-only proof, undated methodology, and guarantees of any kind.
- An honest vendor shows dated methodology, set files per firm, declared limits and a rule-update commitment, not cherry-picked numbers.
- Your own forward test on demo is the cheapest insurance against paying repeat challenge fees for someone else's curve fit.
The uncomfortable truth about EA backtest vs live results
Let's put the conflict of interest on the table before anything else. This blog is published by PraxAI, and PraxAI sells trading software. A beautiful backtest is the single easiest way to sell an EA, which is exactly why this guide to EA backtest vs live results exists: the gap between the two is the most predictable disappointment in retail automation, and almost nobody with something to sell talks about it honestly.
So here is the honest baseline. A live account will not reproduce a backtest. Not sometimes, not with the right broker, not ever. The useful question is not whether the results will diverge, but by how much, in which direction, and whether the strategy still clears prop firm rules after the divergence. This guide walks through the mechanics that create the gap, how to read a vendor's backtest like a skeptic, and what a trustworthy vendor should be willing to show you instead.
None of this is an argument against automation. The case for [replacing discretionary decisions with software](/blog/manual-trading-vs-automated-eas) survives the backtest problem just fine. It is an argument against buying numbers that were never going to survive contact with a live spread.
Why EA backtest vs live results always diverge
Divergence is not one problem. It is a stack of small ones, all leaning the same direction: against the live account. Each layer gets modeled optimistically in a tester and paid in full on a real server.
- Spread. Most backtests apply one fixed spread. Live spreads breathe: they widen at rollover, before news, and in thin sessions, which is precisely when many strategies want to trade. A system earning a couple of pips per trade can lose a large share of its edge to spread variance alone.
- Slippage and execution. The tester fills you at the price on the chart. A live server fills you after latency, requotes and queue position, and the cost lands hardest on stop entries and fast markets. We wrote a separate breakdown of [how slippage and execution quality reshape EA results](/blog/slippage-execution-prop-firm-ea).
- Commission and swap. Raw spread accounts charge commission per lot, and positions held through rollover pay or earn swap. Backtests frequently model neither, or model both at zero.
- Tick quality. A test built on 1 minute OHLC data invents the path price took inside every bar. Real tick testing on MetaTrader 5 is far closer to reality, but even real ticks are one broker's ticks from one historical feed.
- Feed differences. Your evaluation account lives on a specific server with its own quotes. The backtest data almost never comes from that server, so entries triggered by a wick in one feed simply never fire in the other.
- Overfit. The largest layer of all: parameters tuned until history looks perfect encode noise, not edge. It gets its own section below.
A worked example of the cost stack (invented numbers)
Every number in this example is invented for illustration, but the mechanism is real. Say a backtest shows 600 trades averaging 2.0 pips of profit each, tested at a fixed 0.6 pip spread with no commission and no slippage. On one standard lot at 10 dollars per pip, that reads as 12,000 dollars of profit.
Now price the same trades live. Spread averages 0.9 pips instead of 0.6, commission adds roughly 0.7 pips per round trip, and average slippage costs another 0.3 pips. That is 1.3 pips of extra cost per trade, so the same 600 trades now average 0.7 pips: 4,200 dollars. Nothing about the strategy changed. Close to two thirds of the paper edge was modeling, not market.
This is why small-edge, high-frequency curves look flattering in testers and fragile in production. The thinner the average profit per trade, the larger the share of it that lives inside the modeling assumptions.
Overfitting: the optimization peak never repeats
Run an optimizer over enough parameter combinations and something will always look spectacular. That is not discovery, it is arithmetic: test thousands of configurations against one slice of history and some configuration will fit that slice's noise almost perfectly. The peak of an optimization is, by construction, the setting most contaminated by luck, which makes it the least likely to repeat.
The honest defense is out-of-sample testing: tune parameters on one window of data, then run them untouched on a later window the optimizer never saw. If performance collapses out of sample, the edge was noise. The companion test is parameter stability. In another invented example, imagine an optimizer reporting that a lookback of 37 made 18,000 dollars while 35 and 39 barely broke even. That peak is a spike standing on nothing. If every value from 30 to 45 makes money, the region is robust and the exact number barely matters.
This is also why a vendor rerunning fresh optimizations every month to keep the marketing curve pretty is a warning sign, not a service. Parameters that need constant re-tuning to look good were never stable in the first place.
How to read a backtest like a skeptic
A backtest is not evidence of future profit. Read as a document, though, it can still tell you a great deal, mostly about the vendor. Run any report you are shown through five filters.
- Period and regimes. Ten months of a friendly trend proves nothing. Look for several years covering trend, chop, rate shocks and at least one genuine crisis, with start and end dates stated rather than cropped.
- Data quality. Ask what modeling the test used. Real tick data with variable spread, commission and swap included is the serious minimum on MetaTrader 5. Every-tick interpolation from 1 minute bars is a simulation of a simulation.
- Out-of-sample proof. Ask which window the parameters were optimized on and which later window validated them. A vendor who cannot answer has optimized on everything, which means validated on nothing.
- Drawdown against prop rules, not against profit. Every firm sets its own daily loss limit and its own maximum drawdown, both commonly structured but varying by account type and platform and changing over time, so read the report against the current rules on the firm's own site. A report bragging about profit while quietly recording a drawdown well past the limit you will actually trade under fails the only test that matters.
- Trade count and smoothness. A few dozen trades prove nothing statistically, and a curve with no visible losing streaks usually means averaging down is hiding them. [Martingale and grid logic manufacture exactly that seductive smoothness](/blog/martingale-grid-ea-prop-firms), right up until one cluster of losses ends the account.
Vendor red flags that should end the conversation
Selling software is legitimate. Selling certainty is not. These patterns, alone or combined, are how overfit curves get monetized.
Price is deliberately absent from the list, in either direction. Expensive tells you nothing and neither does cheap. The filter that actually works is falsifiability, and each flag below is a different way of making a claim that cannot be checked. Our [guide to choosing an AI trading bot for prop firms](/blog/best-ai-trading-bot-prop-firms-2026) applies that same test across the current market.
- A near-perfect equity curve. Straight lines do not survive spread variance, let alone a crisis. Smoothness at that level is either curve fitting or averaging down.
- Win rates near 99 percent. Trivially manufactured: pair take profits of a few pips with stops of hundreds, or no stop at all. The win rate is real right up until the one loss that erases it.
- A vendor demo account as the only proof. Demo fills have no slippage, no requotes and no market depth, and you cannot verify the settings behind the screenshot. It is execution evidence from a market that does not exist.
- No dated methodology. If a vendor cannot say when the strategy was built, what data it was optimized on and what has changed since, the backtest is unfalsifiable marketing.
- Guarantees of passing or of monthly returns. Nobody controls that outcome, and evaluation rules can change under everyone's feet.
What an honest vendor should show you instead
Since we opened this article by admitting we are a vendor, we should stand in front of our own test first. We do not publish backtest numbers as marketing, for every reason in this article: a backtest is a research tool, not proof of your future results. What we publish instead is the operating envelope, a validated gold configuration that takes one position at a time with no martingale and no grid, a news filter that pauses around high-impact events, rule updates within 48 hours when a firm changes its rulebook, and a 7 day guarantee that exists so your own forward test makes the decision rather than our history.
Now flip every red flag, and you get the disclosure any serious vendor should meet before asking for your card.
- A dated methodology: when the strategy was built, what data trained it, which windows were held out for validation, and a change log since release.
- Set files per firm and account type, because a configuration tuned for one drawdown model is misconfigured for another. [Set files are the mechanism that adapts one EA to different rulebooks](/blog/setfiles-explained).
- Declared limits: the conditions the strategy avoids, how it behaves around news, and the losing periods it has already lived through.
- A rule-update commitment, since firms change drawdown math and news policies without asking anyone first.
- A refund window long enough for you to run your own forward test before the decision becomes final.
The real test starts after the backtest
Due diligence ends with your own data, not the vendor's. Run the EA on a demo account using your target firm's platform and conditions for a few weeks before risking an evaluation fee. A vendor's demo proves little because the vendor controls every variable. Yours answers the only question you care about: how this EA behaves on the feed you will actually be judged on. Your forward test will not match the vendor's backtest either, and that is the point. You are measuring the size of the gap while measuring it is still free. Repeat challenge fees can add up to $2,400+ a year, which prices a month of patience rather well.
When the forward test holds up, move deliberately: our [checklist for passing a challenge with an EA](/blog/pass-challenge-with-ea-firm-checklist) covers firm selection, sizing and the settings that respect evaluation rules. And if you are tempted to pay extra to skip the evaluation entirely, carry the same skepticism into [instant funding accounts](/blog/instant-funding-prop-firms-2026), where the rulebook you must survive is relocated, not removed.
Keep the destination in view, too. Passing is the cheap part: only 1 to 3 percent of funded traders keep the account long term, and the reasons [funded traders lose their accounts](/blog/why-funded-traders-lose-the-account) are the same forces that separate backtests from live results, namely cost, execution and risk that was never modeled. Reading a backtest with skepticism is not pessimism. It is the first habit of traders who plan to still be funded next year.
Frequently asked questions
Why are my EA backtest vs live results so different?
Because live trading pays costs the tester modeled optimistically: variable spread, slippage, commission, swap and a different price feed, stacked on top of parameters that were tuned to past noise. The gap almost always runs against the live account. You can shrink it with real tick testing, realistic cost assumptions and out-of-sample validation, but you should expect a gap to remain.
How can I tell if an EA backtest is overfitted?
Ask for the optimization window and the validation window. If the parameters were tuned on the same data that produced the marketing curve, assume overfit. Parameter stability is the other test: if small changes to a setting collapse the results, the peak was noise. Robust neighborhoods of settings matter more than one record run.
Is a demo account good proof that an EA works?
A vendor's demo is weak proof: demo fills ignore slippage, requotes and depth, and you cannot verify the settings behind it. Your own demo forward test is different and genuinely useful, because it measures the EA on the platform and feed you will actually be evaluated on, before any fee is at risk.
What win rate should a legitimate EA have?
There is no correct number, and that is the trap. Win rate is trivially manufactured by pairing tiny profit targets with huge stops. Judge the relationship between average win, average loss and drawdown against the rules you will trade under, not a standalone percentage, and treat anything marketed near 99 percent as a red flag.
How long should I forward test an EA before paying for a challenge?
Long enough to watch it trade through different conditions, including news days it should have avoided. Many traders use a few weeks to a month on demo. The goal is not to reproduce the backtest, it is to confirm live behavior, real costs and rule compliance on your target firm's platform before the first fee leaves your pocket.
Want the bot that runs this discipline for you?