What is slippage tolerance and how does it affect your final cost?

03 November 2026

Slippage tolerance is the maximum price change you accept between submitting a trade and having it execute on a decentralized exchange. It directly determines how much you might overpay - or how likely your trade is to fail. Set it too tight, and your transaction reverts. Set it too loose, and you can buy at a price far worse than what you saw on screen.

How Slippage Happens

On a decentralized exchange, your trade must be confirmed by the network before it updates the pool’s price. Between the moment you click "confirm" and the moment the transaction is included in a block, other trades can move the price. If the price moves against you, you receive fewer tokens per unit of cryptocurrency you spend. Slippage tolerance is your limit on that movement.

Slippage is not a fee. It is a cost from price movement that occurs before your trade settles. The exchange does not collect it; the market does.

The Default Trap

Most wallets and DEX interfaces set a default slippage tolerance, typically 0.5% to 1%. That works for many ordinary trades on liquid pairs. But it can be dangerously high for tokens with low liquidity or small pools.

If a token pair has a thin order book or a small liquidity pool, even a modest trade can move the price several percent. With a 1% slippage tolerance, you authorize the trade to execute at up to 1% worse than the quoted price. On a $1,000 trade, that means you could pay $10 more than expected - and the trade still goes through.

When tight slippage backfires

Setting slippage too low - say 0.1% on a volatile pair - causes frequent transaction failures. The price moves a fraction of a percent before your trade lands, your tolerance is exceeded, and the transaction reverts. You pay the gas fee for the failed attempt anyway.

This is especially common during: - News-driven volatility - Sandwich attacks on Ethereum or similar chains - Trades on new or illiquid tokens where the pool is shallow

When loose slippage backfires

Setting slippage very high - 5% or more - exposes you to frontrunning and sandwich attacks. A bot sees your transaction in the mempool, buys ahead of you to drive up the price, then sells after your trade settles. You buy at the inflated top. The bot profits from your loose tolerance.

This is why reputable DEX aggregators and wallets warn you when slippage exceeds a threshold. They cannot stop you, but they flag the risk.

What affects the right slippage tolerance

No universal number works for every trade. The right setting depends on three factors:

1. Liquidity of the trading pair. A major stablecoin pair on a deep pool can tolerate 0.1% to 0.3%. An obscure token on a small pool may need 2% to 5% to fill at all.

2. Trade size relative to pool depth. A $10,000 trade on a $50,000 pool moves the price more than the same trade on a $5 million pool. Larger trades require wider tolerance or splitting across multiple routes.

3. Network congestion and block time. On Ethereum, blocks arrive every 12 seconds. On Solana, they arrive every 400 milliseconds. Faster blocks mean less time for price movement between submission and confirmation, so tighter tolerance is safer.

How to set it yourself

1. Check the liquidity of the pair you are trading. A DEX aggregator like 1inch or Matcha shows the pool depth for each route.
2. Start with the default or the aggregator's recommended slippage. Most aggregators calculate a minimum safe value based on current pool conditions.
3. If the trade fails, increase slippage in small increments - 0.25% or 0.5% at a time - until it goes through.
4. If the trade succeeds but the final price is noticeably worse than the quote, decrease slippage on your next trade of similar size.

Slippage vs. price impact

These two concepts are often confused but are not the same.

Price impact is the estimated price change from your own trade, assuming no other trades happen. It is calculated by the DEX or aggregator before you confirm.

Slippage tolerance is the extra price change you allow from other trades happening before yours settles.

Your final cost is the sum of price impact and any slippage that actually occurs. You control slippage tolerance; you do not control price impact except by choosing a different pool or splitting your trade.

When slippage tolerance is irrelevant

On centralized exchanges, slippage tolerance does not apply. Your trade executes against the order book instantly (or on a matching engine) and fills at the best available price up to your limit order price. The concept exists only on DEXs where price updates are not instantaneous and transactions are not guaranteed to execute at the exact moment you submit.

The Short Version

Slippage tolerance is your insurance against price movement during confirmation. Too tight, trades fail and you waste gas. Too loose, you overpay. For most routine trades on liquid pairs, the default 0.5% to 1% is fine. For anything unusual - low-liquidity tokens, large trades, volatile markets - adjust it manually and check the price impact first.

Back to exchange fees