What Is Slippage in Liquidity Pools? Price Impact, Tolerance and How to Reduce It

On this page
I started doing transactions and trading in decentralized exchanges. However, I was warned that slippage might cause me not to get the initial amount shown. Apparently, this is called slippage. But how does this work?
The short answer
Slippage in a liquidity pool is the difference between the price a decentralized exchange quotes you and the price your swap actually fills at. It happens because a pool’s price isn’t fixed: every trade moves it along a pricing curve, and other trades can move it further while yours waits to be confirmed. Your slippage tolerance setting caps how bad the final price can be; if the market moves beyond it, the transaction fails rather than filling.
Why liquidity pools have slippage
On a centralized exchange, your order fills against other people’s orders in an order book. On most DEXs you trade against a liquidity pool run by an automated market maker (AMM). The pool holds two tokens and sets the price from their ratio.
The classic design, used by Uniswap v2 and many forks, is the constant product formula: x × y = k. When you buy token Y with token X, you add X and remove Y, and the formula forces the price of Y up as its supply in the pool shrinks. The bigger your trade relative to the pool, the further you push the price, and the worse your average price.
Uniswap’s documentation puts it simply: the more liquidity available at a given price, the lower the price impact for a given trade size.
A worked example
Imagine a pool with 100 ETH and 300,000 USDC, so 1 ETH = 3,000 USDC. Ignoring fees:
| You spend | ETH you’d get at the 3,000 spot price | ETH you actually get | Price impact |
|---|---|---|---|
| 3,000 USDC (1% of the USDC side) | 1.000 | 0.990 | about 1% |
| 30,000 USDC (10% of the USDC side) | 10.000 | 9.091 | about 9% |
| 150,000 USDC (50% of the USDC side) | 50.000 | 33.333 | about 33% |
For the 30,000 USDC trade, the pool ends with 330,000 USDC, so it can keep only 300,000 × 100 ÷ 330,000 = 90.909 ETH and gives you the remaining 9.091. The same trade in a pool a hundred times larger would cost about 0.1%. That is why a trade that looks identical can be cheap on one DEX and expensive on another, and why aggregators split large orders across many pools.
To turn any quote into a percentage yourself, see how to calculate price slippage as a percentage.
The two parts of slippage
- Price impact is predictable. The DEX can calculate it before you sign, and most interfaces show it and warn when it’s high.
- Execution slippage is the change between the quote and the moment your transaction is included in a block. Other swaps in the same pool, ordinary market volatility and MEV bots can all move the price in that window. Uniswap notes that transactions with low network fees may wait longer, giving the price more time to move.
How pool design changes slippage
- Constant product pools spread liquidity across every possible price, so they’re simple but relatively shallow at the current price.
- Concentrated liquidity (Uniswap v3 and v4, PancakeSwap v3 and similar) lets liquidity providers put capital in a chosen price range. More liquidity sits near the current price, so slippage is lower, until price moves outside the ranges where most liquidity sits and depth suddenly thins out. A pool’s total value locked can therefore overstate how much liquidity is actually usable at today’s price.
- Stableswap pools (Curve and similar) concentrate liquidity around a 1:1 price for assets that should trade at par. Curve’s docs give the example that a $1 million swap in a healthy $20 million USDC/USDT pool would likely incur less than 0.01% slippage. If one coin loses its peg, though, the pool becomes imbalanced and prices move quickly.
- Order-book DEXs behave like centralized exchanges: slippage depends on how many orders sit near the best price.
How slippage tolerance works
When you set a slippage tolerance of, say, 0.5%, the DEX calculates a minimum amount received. If execution would deliver less, the transaction reverts and you keep your tokens, though you still pay the network fee on most chains.
Getting the setting right is a trade-off:
- Too low and swaps fail whenever the price ticks, wasting gas fees.
- Too high and you’re telling bots exactly how much they can take. In a sandwich attack, a bot buys just before your swap, lets your trade push the price up to your limit, then sells straight after. The higher your tolerance, the more they can extract.
Many interfaces now set tolerance automatically. The Uniswap web app, for example, typically picks a value between 0.1% and 5% based on gas costs and trade size. Our glossary entry on slippage tolerance covers the basics.
How to reduce slippage
- Trade in deep pools. Check the liquidity of the specific pool, not just the DEX’s total. Our guide to which DEX to use compares the main venues.
- Use an aggregator. Aggregators split orders across pools to cut price impact; see understanding DEX aggregators.
- Break up large trades or use limit orders where available.
- Use MEV protection. Private transaction routing and intent-based systems such as CoW Swap, where third-party solvers fill orders in batch auctions, reduce exposure to front-running.
- Avoid peak volatility. Prices move fastest around big news; our Q&A on whether trading at peak times affects slippage looks at timing.
- Prefer lower-fee networks for small trades, where you can afford to retry a failed swap.
Risks and red flags
- A token that only trades with very high slippage (10% or more) may charge a hidden transfer tax or be designed so it can’t be sold. That’s a common scam pattern, not normal slippage.
- Thin pools for new tokens can be drained or abandoned by the creator; see how locked liquidity works.
- Price-impact warnings exist for a reason. If an interface asks you to type a confirmation to proceed, stop and check the pool.
- Liquidity providers face a mirror-image risk: when traders move the price, LPs end up holding more of the falling asset, known as impermanent loss.
For the basics of trading on a DEX, see how to access a decentralized exchange, the glossary entry on slippage or the DEXs and AMMs guide.
Frequently asked questions
How do you calculate slippage?
Slippage (%) = (expected amount − amount received) ÷ expected amount × 100. If you were quoted 1,000 USDC and received 990, slippage was 1%. Our guide on calculating slippage as a percentage has more worked examples.
What is a good slippage tolerance?
There is no universal number. Many apps now set it automatically; the Uniswap web app, for example, typically uses 0.1% to 5% depending on gas and trade size. Stablecoin swaps in deep pools can use very tight settings, while thinly traded tokens need wider ones and carry more risk.
What's the difference between slippage and price impact?
Price impact is the part of slippage caused by your own trade moving the pool's price. Slippage is the total gap between quote and execution, which also includes market moves and other transactions landing before yours.
Can slippage be positive?
Yes. If the price moves in your favor before your trade executes, you can receive more than quoted. Most DEX interfaces pass that through to you, though some aggregators and intent-based apps handle surplus differently.
Why does my DEX swap keep failing with a slippage error?
The price moved more than your tolerance allowed, often because of volatility, a small pool or a token that charges a transfer tax. Check the token and the pool before simply raising the tolerance.
Sources
Educational content, not financial advice. DeFi carries risk, including total loss of funds.