A replay can expose a bad trading habit. It cannot, on its own, prove that a strategy has an edge. That distinction matters more than the feature list.
On 18 September 2026, cTrader announced Market Replay for cTrader Windows: a way to choose a point in market history, set a virtual balance and trade forward through recorded data. It is useful when treated as a rehearsal room. It becomes misleading when its result is presented as a backtest.
What cTrader Market Replay is for
cTrader Market Replay is a historical practice workflow, not a claim about future performance. According to cTrader's 18 September announcement, the Windows feature lets a trader choose a historical date and time, set a virtual starting balance and control replay speed.
The same announcement says the replay can use minute open-price data or historical tick data. That choice changes what you can inspect, but it does not turn a discretionary session into a controlled experiment. A trader can slow a moment down, revisit it with a saved timestamp and see what they did. That is the point.
Practice and backtesting answer different questions
The cleanest way to avoid fooling yourself is to decide which question you are asking before you open the platform.
| If you need to know... | Market Replay can help when... | A backtest still needs... |
|---|---|---|
| Did I follow my entry and risk process? | You record the setup, the decision and the reason for every change. | A fixed rule set that does not change after seeing the outcome. |
| Can I recognise the setup in motion? | You start before the move unfolds and do not skip inconvenient periods. | A defined universe, timeframe and test window. |
| Does the strategy have an edge? | It can generate questions worth testing. | Explicit entry, exit, sizing, data and cost assumptions, plus an untouched evaluation period. |
| What did I do when the trade went wrong? | You save a timestamp and review the order path afterwards. | A result that can be reproduced rather than narrated. |
A manual replay is especially good at finding process failures: entering before a condition is complete, moving a stop without a rule, or treating one clean chart as proof. Those are useful discoveries. They are not evidence that the rules would survive another period, another instrument or real execution conditions.
A replay can leak hindsight without looking like it
Hindsight bias is the main danger in a replay. It arrives quietly: the trader already knows that an unusual day happened, starts too close to the event, skips a dull stretch or changes the definition of a valid setup after a loss.
The remedy is procedural rather than technological. Before the session, write down the symbol, historical start point, chart settings, setup definition, entry condition, invalidation condition and maximum risk rule. During the session, log every eligible setup, including the ones you decline. Afterward, review the record before changing any rule.
This is not a promise that the process is unbiased. It is a way to leave an audit trail. If the rules need changing after the review, make the change and start a fresh sample. Do not quietly rewrite the prior session until it looks competent.
A practical Market Replay review protocol
A short ledger gives the replay a job beyond entertainment.
- Freeze the plan. Write the rules in plain language before selecting the historical moment.
- Start with no visible outcome. Begin before the setup can be recognised; do not jump to the candle you remember.
- Log every decision. Record the time, setup state, order action and the reason for no trade as well as for a trade.
- Mark the review point. cTrader says saved timestamps can return you to specific moments. Use them for mistakes, not only for winners.
- Separate execution notes from strategy notes. “I entered late” is a process observation. “The entry rule is invalid” is a hypothesis that needs a separate test.
- Promote only fixed rules. When a pattern seems useful, specify it precisely enough that another person could apply it without seeing your chart annotations.
cTrader's announcement also describes Trade Watch, which brings together Positions, Orders and History with Equity and Trade Statistics. That can help connect a decision to its result. The useful question is not whether the virtual equity line went up. It is whether the record shows a repeatable decision under conditions you defined before the replay began.
When a replay should become a backtest
A replay should graduate to a backtest only after its rules stop moving. The backtest then needs a fixed data range, a clear signal definition, position-sizing logic, exits, costs and a record of every trade the rules would permit.
It also needs data that the rules did not see during design. An out-of-sample period is held back while the idea is created, then used to check whether the apparent edge persists. Without that boundary, the test can become a polished description of the past rather than a challenge to the idea.
For an automated cBot, reproducibility is the standard: the same rules and stated assumptions should produce an inspectable result. That is why realbacktesting publishes cTrader-native backtests that buyers can rerun, with the methodology explained on the proof page. A replay can sharpen the question; it cannot replace the evidence.
The limits of the new tool
cTrader's announcement says Market Replay is available on cTrader Windows. Treat availability, data options and interface behaviour as platform details that can change; verify the current product documentation before building a workflow around them.
More importantly, no practice environment can eliminate the gap between historical rehearsal and a live account. A replay cannot establish future liquidity, future spreads, future fills or a trader's live behaviour under pressure. It can reveal whether the process has enough definition to deserve a proper test.
Frequently asked
Is cTrader Market Replay a backtest?
No. cTrader Market Replay can rehearse decisions through historical data, but a backtest tests a fixed set of rules against stated data, execution and cost assumptions.
Can Market Replay help a discretionary trader?
Yes, if the trader records the setup and every decision before seeing the outcome. Its value is a reviewable practice record, not a retrospective scorecard.
What should I test after replaying a setup?
Turn the setup into explicit entry, exit and risk rules, then test those rules on a defined sample with an untouched evaluation period. The cTrader backtest verification checklist is a useful next step.
A replay is where vague judgement gets exposed. A backtest is where a precise rule has to survive.