What is slippage, and how does it differ from price impact?
The slippage tolerance on a swap screen states how much price movement you accept while the transaction is pending. Price impact is how much the swap itself moves the price. The two are routinely confused; we set out the difference and what raising the tolerance opens the door to.
In short
A swap screen on a decentralised exchange usually shows two numbers: price impact and slippage tolerance. They are not the same thing, and confusing them can cost money.
Uniswap's documentation defines slippage as:
"alterations to a given price that could occur while a submitted transaction is pending"
So slippage is price movement between submitting the transaction and its inclusion in a block.
Price impact: the weight of the swap itself
Price impact has nothing to do with the pending window. It comes from the size of the swap. In an automated market maker the relative value of the two assets shifts continuously while the swap executes; a large swap moves its own price.
What decides it is depth:
"The greater the liquidity available at a given price, the lower the price impact for a given swap size."
The same swap gets a far worse price in a shallow pool than in a deep one. Price impact can be calculated before submitting; slippage cannot be calculated, only bounded.
The tolerance is a limit, not an estimate
In the documentation's terms the tolerance sets an accepted margin of change beyond price impact. How it is applied fits in one sentence:
"as long as the execution price is within the slippage range, e.g., 1%, the transaction will be executed. If the execution price ends up outside of the accepted slippage range, the transaction will fail."
On chain the protection is written as a minimum output amount (amountOutMinimum); if the output falls below that threshold the transaction reverts.
So the tolerance is not a forecast but a cancellation threshold: the way to say "I will not accept worse than this".
What raising the tolerance changes
When a transaction keeps failing, raising the tolerance looks like an easy fix. What it does is allow the transaction to go through at a worse price.
A wide tolerance opens room for third parties who collect the difference: while the transaction waits, the price can be pushed to the edge of the tolerance and the transaction still counts as valid. A narrow tolerance means failed transactions, a wide one means poor prices; there is a tradeoff, and it is left to the user.
Risks
Biggest uncertainty Default tolerance values and routing behaviour of particular interfaces were not examined here.
- A high tolerance is a silent cost. The transaction looks successful; nothing on screen says where the loss occurred.
- Price impact and slippage must be read separately. Raising the tolerance does not fix the price impact caused by a shallow pool.
- A failed transaction still pays a fee. When a narrow tolerance reverts the transaction the gas spent is not refunded (gas fees).
- This piece does not examine particular interfaces. Default tolerances and routing differ between applications.
What was not examined is listed in the data status above.
Sources
This article rests on the sources below. Whether each has a permanent copy is stated next to it.
- #1
Primary source for the slippage definition, the price impact distinction and the minimum output protection: the Uniswap developer documentation.
developers.uniswap.org· no permanent copy· no screenshot
Evidence chain: 1 sources
Tweets get deleted, sites go down. Below is whether a durable copy exists for each source.
Sources (1)
- #1
Primary source for the slippage definition, the price impact distinction and the minimum output protection: the Uniswap developer documentation.
“as long as the execution price is within the slippage range, e.g., 1%, the transaction will be executed. If the execution price ends up outside of the accepted slippage range, the transaction will fail.”
developers.uniswap.org/docs/get-started/concepts/traders/swaps- no durable copy: if the source disappears, this claim loses its basis
- no screenshot captured
Correction history
Articles are never deleted, only corrected. Every change appears here.
- Version 1 ·
Section