Higher slippage tolerance can make a token swap more expensive when the executed price moves against you and the wider limit lets that price through. It sets the worst acceptable execution rather than adding its percentage to the bill. For an exact-input swap, compare the minimum output shown by the interface with the output you expect.
-
Same fill: Two tolerance settings can accept the same output at the same cost.
-
Worse fill: A wider setting can accept fewer output tokens after a price change.
-
Failed swap: A tighter setting can reject that price, though an on-chain attempt may still use gas.
Higher Tolerance Changes the Minimum Output
Higher tolerance lowers the minimum output an exact-input swap will accept. The word “tolerance” invites an assumption: raising it from 1% to 5% means paying 4% more. The setting changes an execution boundary. You commit a fixed input amount and set a minimum output amount. The swap fills at the available price if the output meets that minimum. Below it, the transaction reverts.
Take an illustrative quote of 1,000 output-token units for a fixed input. In a simple quote-based percentage model, 1% tolerance gives a minimum of 1,000 × (1 − 1%) = 990 units. At 5%, the minimum is 1,000 × (1 − 5%) = 950 units. Actual router and interface conventions determine the displayed minimum, so use the numbers shown before signing. The wider setting permits another 40 units of downside in this illustration; it is not a 50-unit charge.
Say the route would deliver 998 output-token units when your transaction executes. Both 990 and 950 are below 998, so either setting permits the same 998-unit fill. You submit the same input, use the same route, and receive the same output in this controlled comparison. Only the rejection boundary changes. The Uniswap swap concepts documentation describes the minimum-output check for exact-input trades and the resulting revert below it.
Compare the displayed minimums because they reveal what you authorize, rather than what you necessarily pay. At 990, a possible 980-unit execution is rejected; at 950, it can fill. That difference matters even while the current quote reads 1,000. The quote estimates a price before the transaction lands; the minimum is enforced at execution. Quoted output shows the expectation, while actual output shows the result.
Price impact is a separate cost. It is the change in the route’s price caused by your trade against available liquidity. Larger trades generally push further through a pool’s liquidity and get a worse average rate; deeper liquidity usually softens the effect. Price impact can already be included in the displayed 1,000-unit quote. Changing tolerance leaves trade size and pool liquidity as they were. Market movement before execution can then change the fill.
Take an Ethereum-to-Sui transfer through Suibridge, a cross-chain bridge that locks a supported asset on Ethereum and mints a corresponding asset on Sui. For the transfer step, how does suibridge work explains how the asset reaches Sui before a separate Sui swap gets its own quote and tolerance setting. Judge that later swap by its displayed minimum received.
Other charges follow their own rules. A pool fee is built into the route’s pricing; an interface or routing fee, where applicable, follows its stated terms. Gas pays for network computation and varies with network conditions and the transaction path. A token contract may impose a transfer charge. Raising tolerance does not itself raise those fee rates, although a changed route or repeated attempt can change the total spent.
The trade-off appears when the price moves outside a tight bound. A tighter minimum protects the output amount you accept, but more attempts can revert in a moving market. A reverted on-chain swap can consume gas even though the trade does not complete. Widening the bound raises the chance of execution and may spare a retry, while allowing a smaller output. The value of a quick fill, likely retry gas, and your acceptable output loss determine which side matters more.
MEV, or value extracted by strategically ordering transactions, adds another reason to choose the bound carefully. On susceptible public routes, a searcher can place a buy before your swap and a sell after it. This sandwich trade worsens your execution. A wider minimum can leave more room for that loss while still allowing the swap to succeed. Exposure varies with route design, trade size, liquidity, and transaction submission.
Before increasing tolerance, refresh the quote and compare its new expected output and minimum received with the old ones. A stale quote may describe a price that has moved. If price impact is large, reducing input size or choosing a deeper route can improve the quote itself. Widen tolerance when you accept the newly displayed floor. That choice trades a stronger output guarantee for a higher chance of completion.
Related Questions
Can slippage be positive?
Slippage can be positive when execution improves relative to the quote and the route passes that improvement through. Say the 1,000-unit quote executes at 1,005 units: you receive five more output-token units, subject to the route’s rules. The actual fill can land above the quote even though tolerance is usually described through its downside boundary.
How does slippage affect exact-output swaps?
Exact-output swaps fix the desired output and bound the maximum input instead. If the price worsens before execution, the transaction may require more input tokens. It reverts once that requirement exceeds the approved maximum. Read the maximum input on the confirmation screen: the cost risk is measured in tokens spent rather than tokens received.
Does slippage tolerance remove token taxes?
Slippage tolerance does not remove a charge written into a token contract. A token that charges on transfer follows its own contract rules when the swap moves it. A wider tolerance may let the transaction complete despite that deduction, depending on the route and its checks. Inspect the token’s fee terms and the swap’s minimum received before accepting the trade.