What Is Slippage in Crypto Trading?
Slippage is the gap between a trade's quoted price and its executed price. Why it happens on crypto exchanges and swap platforms, and how tolerance settings work.
Updated September 2026 · Reviewed by the PipeFlare team
Slippage is the difference between the price a trade is quoted at and the price it actually executes at. It happens because the trade itself moves the market before it fills
A trade with no slippage limit set can execute at a far worse price than the one shown on screen, especially on thin order books or shallow automated-market-maker pools
Category
Trading mechanics
Difficulty
Intermediate
Where you'll see it
Decentralized exchange swap screens like Uniswap, market orders during high volatility, aggregators like 1inch, on-chain trading bots
First introduced
A concept borrowed from traditional finance order execution. It became central to crypto trading with the 2018 launch of automated-market-maker decentralized exchanges (DEXs) like Uniswap
About crypto slippage
Slippage is the difference between the price a trade is quoted at and the price it actually fills at. It shows up because the trade itself moves the market before it finishes executing. A large order on a small order book, or a big swap through a shallow automated market maker (AMM) pool, eats through the available price levels as it fills. The average execution price then drifts from the price first shown on screen. Slippage can run in a trader's favor or against it, but the term almost always comes up when people mean the unfavorable direction.
How it actually works
On a traditional order-book exchange, slippage comes from thin liquidity at the top of the book. A market order to buy fills against the lowest asking prices first, then climbs to the next-cheapest ask as each level runs out. A large order against a shallow book therefore pays a higher average price than the first quote suggested. The same mechanic runs in reverse on a sell order eating through bids.
On a decentralized exchange (DEX) built on an AMM, slippage works differently but produces the same result. An AMM prices a swap using a constant-product formula (x times y equals k) rather than an order book. Every swap shifts the pool's ratio of the two tokens and its price along a curve. A larger swap relative to the pool's total liquidity moves further along that curve. That is why the same trade can carry small slippage on a deep pool like ETH/USDC and large slippage on a thinly-traded pair. Most DEX interfaces, including Uniswap, let a trader set a slippage tolerance. This is a maximum percentage the execution price may drift from the quote before the transaction reverts, instead of filling at a worse price.
Setting that tolerance is a genuine tradeoff. It is not a field to simply maximize or minimize. A tolerance set too low fails during normal price movement between submission and block confirmation. The trader still pays the gas fee for that failed attempt. A tolerance set too high opens the trade up to a sandwich attack. A bot detects the pending transaction in the public mempool and buys ahead of it, pushing the price up. The victim's trade then fills at that worse, still-allowed price, and the bot sells immediately after, pocketing the gap the trader's own setting permitted. Most DEX interfaces default to a moderate figure instead, commonly around 0.5 percent, because neither a 0 percent nor a very high tolerance is safe by default.
The arithmetic makes the size of the risk concrete. A $10,000 swap quoted at a token price of $1.00 but executed with 2 percent slippage fills at an average price of $1.02. The trade receives roughly $9,804 worth of the token instead of $10,000 worth, a real loss of about $196 before any trading fee or gas cost is added. On a deep pool, that same $10,000 swap might move the price by a few hundredths of a percent, costing only a few dollars. The trade size alone does not decide which of those two outcomes a trader gets. The pool's depth relative to that trade size does.
Start here
- 1Check the pool or order-book depth for the pair before trading. Slippage on a $50,000 trade in a $10 million pool looks nothing like the same trade in a $50,000 pool.
- 2Set slippage tolerance based on the pair's typical volatility. A single fixed default does not fit every pair. A stablecoin-to-stablecoin swap can often run under 0.1 percent, while a new or thin token often needs several percent to fill at all.
- 3Split a large order into smaller trades over time, or use an aggregator like 1inch that routes across multiple pools. Either approach reduces how far any single fill has to move the price.
- 4Avoid trading volatile pairs during known high-volatility windows, like a major economic announcement. Normal slippage tolerances are more likely to be tested by a sandwich bot or a fast price move then.
Strengths
- A visible slippage tolerance setting gives a trader direct control over the worst price they will accept, rather than being filled at any price regardless of how bad.
- Aggregators that split routing across multiple pools can measurably reduce slippage on larger trades compared to swapping through a single pool.
- Slippage reverts protect against a transaction filling far outside expectations during a sudden price spike.
Common misunderstandings
- A tolerance set too high exposes the trade to a sandwich attack, where a bot profits from the exact gap the trader allowed.
- A tolerance set too low causes failed transactions that still cost gas, with no trade to show for the fee.
- Slippage compounds with trading fees and, on Ethereum, gas costs, so a trade's effective cost can run well above the pair's quoted swap fee alone.
Common questions
What causes slippage in crypto trading?
Slippage happens because a trade's own size moves the price before it finishes filling. On an order-book exchange, a large market order consumes multiple price levels as it fills. On an automated market maker like Uniswap, a swap shifts the pool's token ratio along a pricing curve. Either way, the average price the trade actually pays drifts from the price quoted before the trade started.
What is a good slippage tolerance to set?
There is no single correct number, since it depends on the pair's liquidity and volatility. A deep, stable pair like ETH/USDC commonly needs well under 1 percent, while a newly-launched or thinly-traded token can require several percent just to fill at all. Setting it too low causes failed transactions. Setting it too high exposes the trade to a sandwich attack.
Can slippage make a trade lose money even if the price call was right?
Yes. A trader can correctly predict that a token's price will rise and still net a loss on that specific trade. This happens whenever slippage, trading fees, and gas costs together exceed the price gain, especially on a large order routed through a shallow pool.
Is slippage the same as a trading fee?
No. A trading fee is a fixed percentage the exchange or protocol charges on every trade, disclosed up front. Slippage is a variable cost created by the trade's own price impact and market movement during execution. It can run near zero on a small trade in a deep, calm market.
How do sandwich attacks exploit slippage?
A sandwich attack targets a pending transaction sitting in the public mempool with visible slippage tolerance. A bot places its own buy order just ahead of the victim's trade, pushing the price up to the edge of the victim's allowed slippage. The victim's trade fills at that worse price. The bot then immediately sells, capturing the price gap the victim's own tolerance setting permitted.
Does slippage apply to centralized exchanges like Coinbase or Binance too?
Yes. A market order on any order-book exchange, centralized or decentralized, can experience slippage if it is large relative to the visible order book. It fills against successive price levels rather than one fixed price. A limit order avoids slippage entirely by only filling at a specified price or better. The tradeoff is that it then risks not filling at all if the market never reaches that price.
Why did my swap fail with a slippage error instead of just costing more?
A failed transaction with a slippage error means the price moved past the tolerance set before the transaction confirmed. The smart contract reverted the swap rather than executing it at a worse price than allowed. The gas fee for that attempt is still spent even though no trade happened. That is the direct cost of setting a tolerance too tight for how fast the pair is moving.
Does trading during low-volume hours reduce slippage?
Not by itself. Low trading volume often means a shallower order book or a thinner AMM pool at that moment, and that can make slippage worse rather than better. Fewer resting orders or less liquidity means the same trade size moves the price further. The time of day on its own does not determine slippage. Liquidity depth relative to the trade size does.
Sources
Related guides
Ready to put this into practice?
Exchange sign-up bonuses pay both you and a referrer after a qualifying trade.