How to Set Slippage for Token Swaps on Base
On Base, slippage sets the worst output a swap can accept; use the app’s estimate, check minimum received, and raise the limit only when a cause calls for it.
Crypto Daybook Newsroom2 min read
Set slippage tolerance to the smallest amount that gives your Base swap a fair chance to complete. Slippage tolerance is the largest difference between the quoted output and the amount you agree to receive. If the market moves past that limit before the swap executes, the transaction usually fails instead of delivering less than the limit allows.
The setting works the same way across Base swap apps, though its label and controls vary. A guide to comparing Base swap routes and pools covers how route choice can affect execution. For the tolerance itself, start with the swap app’s estimate and inspect the minimum output before you approve.
What does slippage tolerance change on Base?
Slippage tolerance sets the minimum output your transaction will accept. For example, if a quote shows 100 tokens and the tolerance is 1%, the minimum is about 99 tokens. The exact figure appears in the swap details; check that figure rather than relying on the percentage alone.
Slippage is different from price impact. Price impact is the price change caused by your own trade, often because it is large relative to the pool’s liquidity. Slippage is the change between the quote and what the transaction can deliver when it executes. A high price impact can make the quoted amount poor even before the market moves, so a wider tolerance does not fix a bad quote.
Should you use automatic or custom slippage?
For most swaps, use the app’s automatic setting. It estimates a limit for the current trade, while custom settings make sense when you understand why that estimate is too tight or too loose. Base is a network; it does not set one slippage value for every token pair or app.
If you choose a custom value, use the smallest limit that accounts for the swap’s conditions. Compare the quote and minimum output, then consider:
- Pool liquidity: Thin pools can move more during a trade, especially for a large order.
- Market movement: A fast-moving price may change between the quote and execution.
- Token rules: Some tokens charge a transfer fee. A swap may need a wider limit to account for it, but check the token’s behavior before proceeding.
- Route: A swap that passes through several pools can face more points where prices may change.
What should you check before confirming a swap?
Review the minimum output, price impact, route, and network fee in the confirmation details. If the minimum output is lower than you would accept, reduce the trade size, wait for a steadier quote, or compare available routes. Raising slippage only changes how much worse an execution the transaction allows; it does not improve the quoted price.
A limit set too low can cause a failed transaction if the price moves before execution. A limit set too high can let the swap complete at a worse price than you intended. Set the limit, read the minimum output as your real floor, and confirm only if that amount works for you.