TradingView Slippage in Ticks: Convert to Price and Cost

Entering 3 in TradingView's Slippage field does not mean three dollars, three percent or three pips. It means three minimum price increments of the chart instrument. The same number can therefore produce very different price adjustments on two charts.

Price adjustment = slippage ticks × minimum tick size. TradingView applies this assumption to simulated market and stop orders. It is a backtest setting, not a promise about the price a live broker will deliver. The official strategy-properties reference defines its units and order coverage.

When preparing TradingView automation with AlgoWay, keep that simulated adjustment separate from the execution evidence you review. Compare the strategy fill with the actual account fill, using the same instrument and order direction. AlgoWay's backtest-versus-live review guide places this check alongside alert timing, spread and strategy settings.

Convert ticks into a price distance

Pine exposes the dataset's minimum price increment as syminfo.mintick. The chart-information documentation distinguishes it from the instrument's point-value multiplier. A tick size tells you the price step; it does not, on its own, tell you the cash value of a whole position.

These are hypothetical instruments, chosen to make the arithmetic visible:

Work backward when you have a price-distance assumption: divide that distance by the instrument's tick size. A 0.50 price adjustment on a 0.25 tick grid corresponds to 2 ticks. If the desired distance is not an exact number of ticks, choose and document the whole-tick approximation used for the scenario.

Check the exact chart ticker and data feed. A familiar market name is not enough to establish a matching tick grid at the execution destination. Copying a slippage number from another instrument without converting it is a small clerical act with a surprisingly large imagination.

Apply the direction to the order, including the exit

Positive simulated slippage worsens a buy fill by moving it higher and a sell fill by moving it lower. TradingView illustrates this behavior in its slippage documentation. The direction is the transaction direction, not simply whether the overall trade is long or short.

Assume a hypothetical long trade has unslipped market fills of 100.00 at entry and 102.00 at exit. With a 0.25 tick size and 3 ticks of slippage:

• The entry is a buy: 100.00 + 0.75 = 100.75.
• The exit is a sell: 102.00 − 0.75 = 101.25.
• The resulting gross price gain is 0.50, compared with 2.00 before the adjustments.

Both fills were affected. Subtracting 0.75 just once from the trade result would miss the exit adjustment. A short trade follows the same order-side rule: its opening sell moves lower, and its closing buy moves higher.

This example holds entry and exit events fixed, excludes fees and assumes unchanged quantity. A complete strategy rerun can behave differently if its exits or sizing depend on the adjusted entry price or equity. The arithmetic isolates the direct price effect; it is not a claimed backtest result.

Convert the effect into cash without confusing fees

For a fixed-size linear contract with a known cash tick value, the direct adjustment is:

Cash effect per applicable fill = ticks × cash value per tick per contract × contracts filled

Suppose the hypothetical contract pays $5 per tick and the order fills 2 contracts. Three ticks then represent $30 per fill. One entry and one exit, each for those 2 contracts and each subject to the setting, represent $60 in total direct slippage impact. This assumes the tick value stays constant and is already expressed in the currency used for the calculation.

Scaling out requires summing the quantities in each applicable exit fill. Do not charge the original full quantity again at every partial exit. Conversely, a limit exit does not acquire the market-order adjustment merely because the entry used it.

Commission is a separate input. Check whether your fee assumption is per order, per contract or a percentage. TradingView notes that slippage can also stand in for spread. If that is your convention, document how much of the modeled cost represents spread so you do not add the same allowance twice elsewhere.

Limit fills need a different assumption

The slippage setting is not a universal surcharge on every order type. Limit-order verification controls whether price must move beyond a limit before the emulator accepts a fill. It does not mean that many ticks are deducted from the limit price. A stop-limit order also needs to be distinguished from a stop that leads to market execution.

Keep the questions separate: what price adjustment does an applicable fill receive, and would the order fill at all? A chart touching a level is not sufficient evidence of a live execution, as the guide to limit orders that touch but do not fill explains.

TradingView also warns that a large fixed slippage assumption can push a simulated fill outside the candle's range. Such a result can be an effect of the chosen model, rather than a bad price in the chart data. Inspect the setting before treating that fill as an observed market event.

Choose scenarios you can explain

There is no useful universal answer such as “always use three ticks.” Build assumptions from the instrument, order size, session and actual execution records available to you. For live comparisons, choose a consistent reference price and timestamp; comparing a fill with a much earlier signal price combines market movement during the delay with execution-price differences.

1. Record the chart symbol, minimum tick size, quantity and order types.
2. Translate each candidate tick setting into price and cash before running the test.
3. Keep commission, date range and other strategy settings fixed while comparing scenarios.
4. Inspect individual entry and exit fills, not just the change in net profit.
5. If the trade sequence changes, check whether the adjusted prices changed a stop, target, size or later signal.

A fixed allowance is a sensitivity test. It helps reveal how much price friction a strategy can tolerate under a stated assumption. It does not model every thin book, gap or delayed order, and changing it does not impose a slippage cap on a live account.