Slippage is the difference between the price you expect when you place a trade and the price you actually get. If a swap screen shows 100 tokens and you receive 97, you experienced 3% slippage. It happens for two reasons: your own order moves the price (price impact), and the market moves between clicking “swap” and the trade being confirmed. Slippage exists on every exchange, but it is most noticeable on decentralized exchanges (DEXs) and with low-liquidity tokens. This guide explains the mechanics with real numbers, how to set slippage tolerance, and how to avoid overpaying.
You’ll find this and every related walkthrough in our DeFi hub.
Key takeaways
- Price impact is the slippage you cause yourself by trading against limited liquidity; it is shown before you confirm.
- Slippage tolerance is the maximum worse-than-quoted price you will accept; if the price moves further, the transaction fails instead of filling.
- Setting tolerance too high invites “sandwich” bots to extract value from your trade.
- Deep pools, aggregators, smaller order sizes and limit orders are the main ways to reduce slippage.
Why Slippage Happens
- Thin liquidity: Small liquidity pools or sparse order books mean each trade moves the price more.
- Large orders: The bigger the trade relative to available liquidity, the more it eats into worse prices.
- Volatility: During fast markets, the price can move in the seconds before your transaction is included in a block.
- Network congestion: Slow confirmation leaves more time for the price to change, and other traders’ swaps may be processed ahead of yours.
- Token taxes: Some tokens deduct a percentage on every buy or sell, which shows up as slippage if you have not allowed for it.
Price Impact vs Slippage Tolerance
These two terms appear on almost every swap screen, and confusing them is the most common mistake.
| Price impact | Slippage tolerance | |
|---|---|---|
| What it is | How much your own trade moves the pool price | A setting: the worst outcome you will accept versus the quote |
| Who controls it | Pool depth and your trade size | You |
| Where to see it | “Price impact” line on the swap preview | Settings gear icon; shown as “minimum received” |
| What happens if exceeded | Nothing automatic; you just get a worse price | Transaction reverts; you pay only the network fee |
Worked example: price impact in an AMM pool
Most DEX pools use a constant-product formula (x × y = k). Imagine a pool holding 1,000 SOL and 150,000 USDC, so the spot price is 150 USDC per SOL.
- You swap 15,000 USDC for SOL. The pool now holds 165,000 USDC.
- To keep k constant (1,000 × 150,000 = 150,000,000), the pool must hold 150,000,000 ÷ 165,000 = about 909.1 SOL.
- You receive roughly 90.9 SOL, an average of about 165 USDC per SOL, 10% worse than the 150 spot price (before fees).
Now repeat with 1,500 USDC: you receive about 9.99 SOL at roughly 150.15 each, a 0.1% impact. Same pool, a trade ten times smaller, and the impact falls roughly a hundredfold. That is why trade size relative to pool depth matters more than anything else.
Worked example: a market order on a centralized exchange
On an order book, a market order fills against the best available sell orders first, then the next ones. Suppose you want 3 ETH and the book shows 1 ETH offered at $3,000, 1 at $3,006 and 1 at $3,015. Your market order fills at an average of $3,007, about 0.23% above the best price you saw. On major pairs, books are deep enough that small orders barely move; on thin altcoin pairs, a market order can fill several percent away from the last trade.
How concentrated liquidity changes the picture
The example above assumes a classic pool where liquidity is spread across every possible price. Newer designs, such as Uniswap v3 and v4 or Raydium’s concentrated liquidity pools, let liquidity providers place their capital in a chosen price range. When most liquidity sits close to the current price, small and medium trades see much lower price impact than the simple formula suggests. The catch is that liquidity can thin out abruptly once a large trade pushes the price beyond the ranges most providers chose, so impact can jump from tiny to severe within a single order. This is another reason to trust the live price impact figure on the swap screen rather than assumptions about how deep a pool “should” be.
A 30-Second Pre-Swap Checklist
- Confirm you are swapping the right token by contract address, not just by name.
- Read the price impact. Above about 1% on a major token, reduce size or find a deeper route.
- Set tolerance to the lowest level the trade realistically needs.
- Check the minimum received and ask whether you would be happy with that exact amount.
- Compare the quote with a second aggregator or a centralized exchange if the trade is large.
Running through this takes less time than reading the swap button, and it catches most expensive mistakes before they become permanent.
Slippage on DEXs vs Centralized Exchanges
On DEXs, you see the expected output, price impact and minimum received before confirming. Uniswap, for example, sets an “auto” tolerance and warns when price impact is high; our Uniswap guide shows where these settings live. On Solana, Jupiter offers dynamic slippage that adjusts the tolerance based on the token’s volatility.
On centralized exchanges, there is no tolerance setting for market orders; you simply get the fills available. Limit orders remove slippage entirely, at the cost that your order might not fill if the price runs away.
Sandwich Attacks: Why High Tolerance Costs You
On public blockchains, pending swaps are visible to bots before they are confirmed. If you set 10% slippage tolerance on a swap that only needs 0.5%, a bot can buy just before you (pushing the price up), let your trade fill near your worst acceptable price, then sell right after. This “sandwich” is a form of MEV (maximal extractable value), and the extra 9.5% of room you allowed is what the bot takes.
For more on the bots behind these trades and how to protect your swaps, read our explainer on what MEV is.
Protection:
- Keep tolerance as low as the trade realistically needs.
- Use wallets or RPC endpoints that offer MEV protection (private transaction routing) on Ethereum.
- Use aggregators and intent-based swap systems, such as those used by 1inch and CoW Swap, which can route orders away from the public mempool.
What Slippage Tolerance Should You Use?
| What you are trading | Typical starting tolerance |
|---|---|
| Stablecoin to stablecoin (USDC/USDT) | 0.05–0.1% |
| Major assets in deep pools (ETH/USDC, SOL/USDC) | 0.3–0.5% |
| Mid-cap tokens | 0.5–2% |
| Fresh memecoins and thin pools | 2–5%, only if you accept the risk |
| Tokens with built-in taxes | The tax plus 1–2% |
These are starting points, not rules. If a swap fails repeatedly, raise tolerance in small steps rather than jumping straight to 10% or more. If a token only trades with very high tolerance, ask why: hidden taxes and sell restrictions are common in scams, as covered in our rug pull guide.
How to Minimize Slippage
- Trade deep pairs: Use the pool or pair with the most liquidity; aggregators find it for you.
- Split large orders: Several smaller trades spaced out, or a TWAP/DCA order offered by some DEXs, reduce impact.
- Use limit orders on centralized exchanges and on DEXs that support them.
- Avoid the first minutes of big news or token launches, when liquidity is thin and prices jump.
- Check “minimum received” before every confirmation; it is the number that actually protects you.
- Use Layer 2s or fast chains for smaller trades, where quicker confirmation shortens the window for price changes.
Troubleshooting: “Slippage Tolerance Exceeded”
This error means the price moved beyond your tolerance before the transaction confirmed, so the swap reverted. Your tokens are safe; you lost only the network fee. Refresh the quote, check whether the token has a buy or sell tax, and retry with slightly higher tolerance or a smaller amount. If it still fails, liquidity may be too thin, or the token may restrict selling.
FAQ
What is a good slippage tolerance?
For major tokens in deep pools, 0.3–0.5% is usually enough, and stablecoin swaps can use 0.1% or less. Mid-cap tokens may need 0.5–2%. Only go above 3–5% for very illiquid or taxed tokens, and understand that the extra room can be captured by bots. Start low and increase gradually if transactions fail.
Can slippage make me lose money?
Yes. High price impact or a loose tolerance can mean receiving noticeably fewer tokens than the headline quote, and that loss is permanent once confirmed. On a large trade in a thin pool, the difference can be 5–20% or more. Always read the price impact and minimum received figures before confirming.
Can slippage be positive?
Yes. If the price moves in your favor between quoting and execution, you can receive more than quoted. Some aggregators pass that surplus to you, while others keep part of it, so read the platform’s documentation. Positive slippage is less common than negative because bots tend to capture favorable moves first.
Is slippage the same as a trading fee?
No. Fees are a fixed, disclosed charge, such as a 0.3% pool fee or an exchange commission. Slippage is the variable difference between quoted and executed price caused by liquidity and market movement. Your total cost on a trade is fees plus slippage plus any network gas.
Crypto is volatile and risky; this is education, not financial advice. Do your own research.
