To model slippage in a TradingView backtest, set the Slippage property (in ticks) inside Strategy Tester's Properties tab, or pass the slippage argument directly in your Pine Script strategy() declaration. Pick a modeling approach, fixed ticks, percent-of-price, or per-order adjustments, then re-run your tests and report the slippage-adjusted P&L and expectancy. Keep in mind the broker emulator works off chart data, not a real order book, so treat results as a benchmark, not a live-trading guarantee.
TL;DR:
- TradingView’s Slippage field defaults to zero ticks and affects market and stop orders; limit orders fill at their specified price or better, or remain unfilled.
- Choose fixed ticks for futures and major forex, while percent of price better reflects altcoins whose tick size is tiny relative to price.
- Bar Magnifier adds intrabar detail, but TradingView’s emulator still lacks order book depth, queue position, and requotes, so backtests remain benchmarks.
- Report net P&L after commissions and slippage, average slippage per trade, and expectancy at zero, small, and medium settings; compare assumptions with actual fills.
Table of Contents
- Where to set slippage: strategy settings and Pine Script
- Modeling approaches: fixed ticks, percent slippage, and per-order adjustments
- Testing fidelity: TradingView broker emulator limits and how to tighten realism
- Measuring and reporting slippage in backtest results
- Practical tips: what scalpers do to validate slippage assumptions and reduce live slippage
- Author perspective: recommended defaults and a practical workflow
- How Scalping-Algo helps you validate slippage-aware backtests
- FAQ
- Sources
Where to set slippage: strategy settings and Pine Script
Setting slippage is quick once you know where TradingView hides the control. Here's the exact path:
- Open your strategy on the chart, click the gear icon next to its name, and go to the Properties tab.
- Find the Slippage field, enter a value in ticks, and save. The default is 0 ticks, which means your backtest currently assumes perfect fills on every order, according to TradingView's strategy properties documentation.
- In Pine Script, you can set the same value programmatically by adding the
slippageargument to yourstrategy()declaration, so anyone who loads your script gets the intended assumption automatically. - Remember that slippage only affects market and stop orders. Limit orders fill at their specified price or better, or they don't fill at all, per the same strategy properties reference.
This last point trips up a lot of scalpers. If your strategy relies heavily on limit entries, cranking up the slippage value won't do much to your equity curve, because TradingView isn't applying it to those fills. The broker emulator documentation recommends a non-zero slippage value specifically for strategies built around market or stop orders, since those are the fills most exposed to real execution cost. For scalping systems that chase momentum with market orders on lower timeframes, this single setting is often the difference between a backtest that looks great and one that holds up.
Modeling approaches: fixed ticks, percent slippage, and per-order adjustments
Not every instrument or strategy needs the same slippage assumption. Here are three approaches worth testing before you commit to one:
- Fixed-tick model: This matches TradingView's native slippage parameter directly. It's simple, transparent, and works well for instruments with a meaningful tick size, like futures or forex majors, where a few ticks represent a consistent dollar cost across price levels, as described in the strategy properties guide.
- Percent-of-price model: Rather than a fixed tick count, this scales slippage to the instrument's price. It tends to work better for assets whose tick size is tiny relative to price, such as low-priced crypto tokens, where a flat tick assumption either overstates or understates real cost depending on where price sits.
- Per-order-type adjustments: This means applying a larger slippage assumption to market entries and to bars with wide ranges or high volatility, while leaving limit orders at a near-zero slippage assumption since they fill at your price or not at all.
If you're working with a percent-based assumption but need to enter a tick value in Pine Script, convert it using the bar's close price and your instrument's tick size. Multiply the percent figure by the close, divide by tick size, and round to get a usable tick count for the slippage argument. This keeps your percent logic compatible with TradingView's native parameter instead of forcing you to build a separate slippage engine from scratch.
Scalpers trading thin altcoins or exotic forex pairs tend to lean toward percent-based models, since tick size there barely reflects real cost. Futures and major forex traders usually get more mileage out of the fixed-tick approach because spreads and typical slippage in those markets tend to hold steady in tick terms across normal conditions.
Testing fidelity: TradingView broker emulator limits and how to tighten realism
The broker emulator is a useful approximation, not a replica of a live exchange. It works on chart data, which means it has no visibility into order-book depth, queue position, or re-quotes, a limitation that 1inch's slippage overview points out applies broadly to backrest-only slippage modeling. Treat your results as a theoretical benchmark for strategy robustness, not a promise of what you'll see live.
A few steps help close that gap:
- Turn on Bar Magnifier or switch to a higher-resolution data feed where available, since intra-bar detail gets your fills closer to what would happen in real time.
- Add randomized slippage within a defined range instead of a single fixed value, which captures the uncertainty of real fills better than one static number.
- Simulate partial fills or vary your slippage assumption by volatility, applying more slippage on wide-range bars and less on calm ones.
- Write down every assumption you used, slippage value, order type logic, whether Bar Magnifier was active, so you can compare results across versions of your strategy later.
None of this turns a backtest into a live record. It does make the backtest a more honest stress test of whether your edge survives contact with real execution costs.
Measuring and reporting slippage in backtest results
A slippage assumption only matters if you track what it does to your numbers. Report these alongside your usual metrics:
- Net P&L after both commissions and slippage, not gross P&L, since gross figures hide the real cost of execution.
- Average slippage per trade and slippage as a percent of average trade size, which tells you whether your edge is thin enough for execution cost to matter.
- Win rate, expectancy, and max drawdown recalculated at several slippage levels so you can see how fragile the strategy is.
- The exact test parameters you used, slippage value, order type assumptions, whether Bar Magnifier was on, saved alongside the results so future comparisons stay apples-to-apples.
A small summary table in your backtesting dashboard, showing P&L and win rate across a few slippage scenarios side by side, makes this easy to scan before you commit capital. Our backtesting dashboard walkthrough covers how out-of-sample splits pair with this kind of scenario testing for a more complete validation process.
Practical tips: what scalpers do to validate slippage assumptions and reduce live slippage
Backtests get you close. A short live sample gets you the rest of the way. Track a batch of actual fills, compare them against what your backtest assumed, and adjust your slippage parameter to match the gap. A spreadsheet or a trading log works fine for this.
- Prefer limit orders or laddered entries where your strategy allows it, since they reduce exposure to negative slippage compared to market orders.
- Size down on thin markets or during low-liquidity windows, where a market order is more likely to walk through several price levels.
- Run sensitivity tests at zero, small, and medium slippage values, and keep a record of how much your results change, since that tells you how fragile your edge really is.
- Update your slippage assumptions after any meaningful shift in volatility or liquidity, rather than leaving a number you picked months ago.
Pro Tip: Re-check your slippage assumption every time you switch instruments or timeframes, since what's realistic on a 15-minute chart rarely holds on a 1-minute chart.
Our guide to cutting slippage with execution levers walks through these levers in more depth if you're building out a full execution checklist.
Author perspective: recommended defaults and a practical workflow
Start conservative. For market orders, a small fixed-tick slippage assumption is a reasonable default on most instruments, with percent-based scenarios layered on top for anything volatile. Don't skip the intra-bar detail step. Bar Magnifier takes a few extra seconds to load and consistently changes fill timing in ways that matter for scalping systems on 1 to 15-minute charts.
Before locking any assumption in, compare it against a small batch of live fills. Markets shift, and a slippage number that fit last quarter's volatility regime won't necessarily fit this one. Revisit it on a regular cadence, log where live fills diverge from backtest assumptions, and let that log guide your next adjustment rather than guessing again from scratch.
— Tran
How Scalping-Algo helps you validate slippage-aware backtests
Our Command Center brings together alerts, backtesting, signals, and educational resources. Our premium TradingView indicators generate non-repainting signals on lower timeframes, so the entries you're testing slippage against are the same ones you'd trade live.
- Our Smart Scalping Signals indicator provides real-time trading signals.
- Plans run Monthly at $79 per month, Yearly at $799 per year, or Lifetime at $1,999 one-off, all through our main site.
If execution realism is holding back your confidence in a strategy, take a look at what's included and pick the plan that fits how you trade.
FAQ
What does "slippage" mean in trading?
Slippage is the gap between the price you expected on an order and the price you actually got filled at, as described by Investopedia's overview of slippage. It shows up most often in volatile or thin markets, and traders reduce it using limit orders, smaller position sizes, or by avoiding erratic price periods.
How do I set slippage in TradingView's Strategy Tester?
Open your strategy's settings, go to the Properties tab, and enter a tick value in the Slippage field, or add the slippage argument to your strategy() call in Pine Script. The default is 0 ticks, and the setting applies to market and stop orders, not limit orders, according to TradingView's documentation.
What is a squeeze momentum indicator?
A squeeze momentum indicator combines Bollinger Bands and Keltner Channels to flag periods of low volatility that often precede a sharp price move, along with a momentum reading to suggest likely direction. It's commonly used to time entries right as volatility starts expanding again.
How do I add a 200 EMA to TradingView?
Open the chart, click the indicators icon, search for "Moving Average Exponential," add it to the chart, then open its settings and choose a length. You can adjust the timeframe or color from the same settings panel.
What are the "big 3" indicators traders reference?
Traders commonly refer to moving averages, RSI, and MACD as a core trio for gauging trend direction and momentum together. Definitions vary across trading communities, so some lists swap in volume or Bollinger Bands depending on the strategy.
Sources
- Strategy properties — TradingView
- What is slippage in crypto? | 1inch Learn
- Understanding Slippage in Finance: Key Insights and Examples