Option backtesting looks, from a distance, like backtesting anything else. Up close it is a different job: an option's price depends on time passing, on implied volatility and on the strike, three things a price history of the underlying does not contain.
- Backtesting options is a data problem first, not a software problem.
- An option's price moves for three reasons: the underlying, time, and implied volatility.
- A backtest that ignores implied volatility produces wrong results, not approximate ones.
- The journal remains the most reliable method: your real trades already contain what no reconstruction can recreate.
On a stock or a currency pair, a backtest needs a price series and a rule. On an option you also need to know what that specific contract was worth, at that strike, at that expiry, on that day. The data exists, but it is bulky, usually paid for, and rarely complete on older expiries.
That is why most attempts at option strategy backtesting end with results that look too good: the option price gets reconstructed from a model, and the model does not know the real spreads of the market. This article covers what is feasible, what is not, and where to start.
Why options trading backtesting is not stock backtesting
A stock price on a given date is a single number. An option price, on the same date, depends on strike, expiry, direction, and the implied volatility of the moment. For one day and one underlying, that is not a handful of values but hundreds of combinations, each with its own history.
Then there is time decay. An options position loses value simply because time passes, regardless of any move in the underlying. A backtest that only tracks the underlying ignores that permanent cost, and any premium-selling strategy will look better than it is, or the reverse for a buying strategy.
Third difference, implied volatility. It rises before earnings and falls afterwards, which changes option prices without the underlying moving. A strategy tested without it misses the factor explaining a large share of real-world results.
What you actually need to backtest an options strategy
| Data needed | Why | How hard to get |
|---|---|---|
| Complete historical chains | To know the price of the exact strike | High, usually paid |
| Implied volatility per strike | Price moves without the underlying | High |
| Historical bid-ask spread | The real cost of entry and exit | Very high, rarely supplied |
| Dividends and events | They shift strike prices | Medium |
The bid-ask spread is the most commonly forgotten item and the most expensive. On illiquid options it can account for a large part of the expected result. A backtest assuming execution at the mid price describes a market that does not exist.
The three workable paths
The first is to buy the data and use a specialised tool. It is the most complete and most expensive route, and it requires knowing precisely which question you are asking, otherwise you pay to explore.
The second is forward testing: running the strategy live, at minimum size, over several months. It is slow, but it is the only test that automatically includes every factor, spreads and your own execution included. The distinction between backtesting and forward testing applies across all markets, not just options.
The third is to journal rigorously the options trades you already place, recording the strike, the expiry, the implied volatility at entry and the reason for the choice. After a few months you hold a genuine dataset, small but true, where a reconstructed backtest is vast but wrong.
Options backtesting software: what to look for, and what free really covers
Every options backtester faces the same constraint, whatever its interface: it can only be as good as the chain data behind it. So the first question to ask any options backtesting software is not what its charts look like, it is where its historical prices come from and how far back they go, strike by strike.
Free options backtesting exists, with real limits that are worth knowing before you spend a weekend on it. Free tools generally cover a handful of very liquid underlyings, over a short window, with mid prices rather than bid and ask. That is enough to check that an idea is not absurd, and not enough to judge whether it makes money. Any free options backtesting software that claims otherwise is quietly reconstructing prices.
| Question to ask | Good answer | Warning sign |
|---|---|---|
| Where does the chain data come from? | A named historical provider | Prices computed by a model |
| Does it include bid and ask? | Yes, historical spreads | Mid price only |
| How far back does it go? | Several years, expiry by expiry | A few months |
| Can I export the results? | Open format | Screenshots only |
Among options backtesting tools, the honest ones state these limits up front. It is also worth knowing that options strategy backtesting on a paid dataset does not remove the need for forward testing: it removes the data problem, not the overfitting problem, and those are two different failures.
The mistake that invalidates most option backtests
It has a name: parameter overfitting. An options strategy has far more settings than a directional one, since you choose the strike, the expiry, the entry timing and the exit rule. Multiplying settings over a fixed history guarantees you will find a combination that worked, and guarantees nothing about what comes next.
The remedy is the same as everywhere: hold back a period the optimisation never saw, and apply only the final setting to it. If the result collapses there, it was not a strategy, it was a fit to history. That principle is covered in our article on backtesting without fooling yourself.
What Tradoshi does for options traders
Tradoshi takes options through the third path, the one built on genuine data. The tool imports your real options positions from the brokers that support them, journals them with their strike and expiry, and analyses them like the rest: by instrument, by time of day, by size, with their maximum excursions. For an options trader that is the only angle resting on their own decisions rather than on a reconstructed past.
The backtesting module replays candles of the underlying with simulated execution, fees and carry costs configurable per session. That is what you need to test a directional logic, the scenario that decides to buy a call or a put. The price of the option itself, at that strike and expiry, comes from a historical option chain, and that is a market constraint more than a vendor one: those datasets are bulky, expensive, and nobody distributes them for free.
Frequently asked questions
Frequently asked questions
How to backtest options strategies without paid data?
You can check that an idea is not absurd on a free dataset covering liquid underlyings, then move to forward testing at minimum size. What you cannot do is judge profitability that way: without historical spreads, the result is systematically flattering. Backtest option strategy ideas for free, but validate them live.
How to backtest an options strategy?
You need complete historical option chains, with the price of each strike, the matching implied volatility and ideally the bid-ask spread. Without that data a backtest reconstructs prices from a model and produces wrong results. Failing that, forward testing at minimum size and rigorous journaling remain the two reliable methods.
Can you backtest options for free?
Only partly. A few free sources cover very liquid underlyings over a short window, but complete chain histories are almost always paid. A free and honest approach is to journal your own options trades rather than reconstruct an approximate past.
Why does my option backtesting give such good results?
Three causes recur: execution assumed at the mid price when the bid-ask spread is real, time decay left out, and parameters optimised on the very period used to judge. Holding back a period the optimisation never saw collapses most of those results.
Is implied volatility really essential?
Yes, for any strategy whose result depends on the premium level, which is nearly all of them. Implied volatility rises and falls without the underlying moving, notably around earnings, and it explains a large share of real gains and losses.
What does Tradoshi do for options traders?
It imports your options positions from your broker, journals them with their strike and expiry, and analyses them like your other trades: by instrument, by time of day, by size, with their maximum excursions. On the backtesting side, the module replays candles of the underlying with simulated execution, which tests the directional logic behind the position. Simulating a full option chain, strike by strike, requires historical chain data that nobody distributes for free.
How long does it take to validate an options strategy?
There is no universal duration, but there is a criterion: enough positions that the result no longer depends on two or three trades. On weekly expiries that is counted in months; on long expiries, in years. Which is precisely why forward testing takes patience.