What Is Slippage Tolerance?

Slippage tolerance is a setting on decentralized exchanges that defines the maximum price change you are willing to accept between the moment you request a swap and the moment it actually executes on-chain. If the price moves against you by more than that limit, the transaction reverts rather than filling. It is, in effect, a safety valve that caps how much worse than expected a trade is allowed to get.

To understand slippage tolerance, it helps to first understand slippage itself. This article explains both, how the setting works on automated exchanges, and the trade-offs of setting it high or low. It covers mechanics only and is not trading advice.

What is slippage tolerance?

Slippage tolerance is the maximum acceptable difference between the price you are quoted and the price at which your trade executes. You set it as a percentage before confirming a swap. If the realised price stays within that percentage, the trade proceeds; if it drifts beyond it, the trade is cancelled.

The purpose is protection. Between quoting and confirming, the market can move, and without a limit you could receive materially fewer tokens than you expected. Slippage tolerance draws a line the trade is not allowed to cross.

What is slippage, and why does it happen?

Slippage is the difference between the expected price of a trade and the price at which it is actually filled. It occurs because a quote is a snapshot, and conditions can change before the transaction settles.

On a blockchain, a swap is not instant: it is submitted, waits in a queue, and is confirmed some seconds later. During that gap, other trades can shift the price. Two factors make this worse — low liquidity, where there is little depth to absorb an order, and large order size relative to the available pool. On an automated market maker, a large trade also moves along the pool’s pricing curve, an effect called price impact, so the bigger the trade, the worse the average price.

It is worth separating these two contributors. Price impact is the predictable, mechanical part: it comes from the size of your own trade relative to the pool and can be estimated before you confirm. The rest of slippage is the unpredictable part — the price moving because of everyone else’s activity while your transaction waits to settle. Slippage tolerance is aimed mainly at the second, unpredictable component, capping how far the market can move against you before the trade is abandoned.

How does slippage tolerance work on a DEX?

On a decentralized exchange, slippage tolerance translates into a concrete minimum received figure. When you set a tolerance, the interface calculates the fewest tokens you will accept from the swap. That minimum is encoded into the transaction sent to the blockchain.

When the transaction is processed, the protocol checks the actual output against your minimum. If it meets or exceeds the minimum, the swap completes. If the price has moved so that you would receive less than the minimum, the transaction reverts — it fails and your input tokens remain in your wallet. This check is enforced by the smart contract, not by trust in the interface.

Slippage versus slippage tolerance

The two terms are closely related but distinct, and the table clarifies the difference.

In short, slippage is what actually happens to the price; slippage tolerance is the rule you set beforehand; and minimum received is how that rule is expressed as a hard floor in the transaction.

What happens if slippage exceeds the tolerance?

If the execution price would breach your tolerance, the swap reverts. Your tokens are not spent and the trade simply does not occur. On most networks, however, you still pay the gas fee for the attempt, because the blockchain performed the work of checking and rejecting the transaction.

This is the intended behaviour: a failed, cheap-to-retry trade is usually preferable to a completed trade that hands you far fewer tokens than expected. The revert converts an unpredictable price risk into a bounded, known outcome.

It also explains a common frustration. During periods of rapid price movement or heavy network congestion, transactions can sit unconfirmed for longer, giving the price more time to drift past the tolerance. Traders may then see several swaps revert in a row, each still costing gas. The setting is doing its job — refusing bad fills — even though the repeated failures feel like the exchange is broken.

What are the trade-offs of setting it high or low?

Choosing a tolerance is a balance. Set it too low and legitimate trades may fail repeatedly during normal price movement, wasting gas on reverts, especially for volatile or thinly traded tokens. Set it too high and you permit the swap to fill even after the price has moved sharply against you.

A high tolerance also invites a specific hazard: the sandwich attack, a form of maximal extractable value (MEV) where bots place trades immediately before and after yours to profit from the price room your tolerance allows. The wider the tolerance, the more room they have. Because the right setting depends on a token’s liquidity and volatility, many decentralized exchange interfaces suggest a range or set it automatically. What counts as appropriate is situational, and nothing here is a recommendation of a specific number.

The bottom line

Slippage tolerance is the guardrail on a decentralized-exchange swap: the maximum price movement you will accept before the trade cancels itself. It works by setting a minimum amount you must receive, enforced on-chain, so a swap that would fill too unfavourably reverts instead. Set it too tight and trades fail; set it too loose and you risk poor fills and MEV. Understanding the setting — and the difference between slippage and slippage tolerance — helps readers grasp how on-chain trades are actually protected. This explainer covers mechanics only and is not trading advice.