Sushiswap
Sushiswap slippage: Tolerance Choices and Minimum Output
last updatedSushiswap slippage measures the change between a swap quote and its execution price. Choose tolerance from the minimum output you will accept for your selected trade. A tighter bound allows less adverse price movement; a wider bound permits a lower output and may avoid some reversions. There is no useful universal percentage because liquidity, trade size and movement before execution vary. First separate a poor quote caused by price impact from a quote that changes while pending. Raising tolerance cannot repair the former. For an exact-input swap, the minimum received amount gives the concrete output boundary to review before signing.
In short: Higher tolerance lowers the output floor for the same exact-input quote, so it can permit worse execution without improving liquidity.
Tighter Protection or More Execution Room
A tighter tolerance fits an already acceptable quote when receiving appreciably fewer output tokens would defeat the trade. Widening the bound makes sense only when its lower minimum remains acceptable. Frequent reversions alone do not establish that condition. Low liquidity may already depress the quoted rate before any delay occurs. A bound that permits that quote to execute does not make its economics better. Choose the output constraint first, then consider whether the current quote leaves enough room for movement during submission.
An acceptable percentage can produce an unacceptable token amount when the quote or input size changes.
How Does Minimum Received Limit an Exact-Input Swap?
Minimum received sets the lowest output that an exact-input swap's encoded output check will accept. The input amount stays specified while execution determines the output. Contract checks compare token amounts in their smallest units, so rounded screen figures may conceal tiny differences. Keep the selected output token and recipient consistent when interpreting the amount. A displayed cash estimate cannot replace that token-denominated floor. With taxed output tokens, a check on calculated output before transfer can accept a net receipt below that minimum. V2 fee-on-transfer methods for token output check the recipient's balance increase. Exact-output methods reverse the control: they target a specified output and bound the required input. Their maximum input shows the most starting tokens that the trade can spend.
Slippage tolerance sets a permitted deviation; it does not charge a separate fee or predict the eventual output.
Liquidity Depth and Trade Size
Trade size relative to usable liquidity determines how far a swap moves pool prices. In a constant-product pool, the trade changes token reserves along the pricing curve. A larger input therefore worsens the average rate, even before unrelated transactions intervene. Concentrated liquidity makes depth depend on the price ranges that liquidity providers fund. A pool's total value cannot show how much liquidity covers the prices that a particular trade crosses. The relevant limit is liquidity along the proposed route.
The same token pair can have different available depth across pools, so pool design alone does not establish a better quote.
Does Higher Tolerance Reduce Price Impact?
Higher tolerance does not reduce price impact because it changes the execution constraint, leaving the proposed trade size and available liquidity untouched. A high-impact quote already includes the trade's effect on pool prices. Its minimum received protects only relative to that quote. Consequently, a tight tolerance can still allow poor execution compared with a smaller trade's rate. Improving that starting rate requires different liquidity or less input, where the available route supports it.
Trading fees and network fees answer a separate cost question. Read whether the quote already incorporates the fee that the route charges before subtracting it again. Network execution costs may require a separate balance in the network's gas currency. Adding every displayed percentage together can double-count deductions or mix different calculation bases. The useful comparison is the quoted output for the same input, alongside costs that remain outside that output.
Auto, Custom and Warning Fields
Swap settings offer Auto and Custom tolerance choices, while the quote details expose the resulting output boundary. Auto supplies the interface's chosen setting; Custom lets you enter a percentage. Read the actual proposed value instead of assuming that Auto always means the same percentage. A saved custom value deserves the same scrutiny when another trade begins. The quote's price impact field concerns the trade's pressure on liquidity. A low-tolerance warning concerns the likelihood that changing conditions will defeat the output bound.
Warnings identify different problems. A high-impact message calls for examining the trade's liquidity demand; a high-tolerance message concerns additional loss that the bound permits. Disabling a confirmation cannot supply missing liquidity. Recheck the proposed minimum after any settings change, because a warning's disappearance alone does not demonstrate an acceptable output.
A High-Impact Quote Before Submission
Consider a hypothetical exact-input quote that shows a price impact warning, an estimated output of 745 tokens and a minimum received of 739 tokens. These quantities use the selected output token. The quote-to-minimum gap is 6 tokens, about 0.81% of the quoted output. That gap describes the permitted shortfall from this estimate, not the trade's total cost or a recommended setting.
The output check compares execution with the encoded minimum; the quoted amount and price impact can change with live liquidity.
Entering a smaller input requests another estimate without committing a swap. Compare output per input token, since a smaller trade naturally returns fewer total tokens. A lower impact reading supports changing size. If the warning persists, the available route still warrants examination. Refreshing the quote also distinguishes an old estimate from the current route's conditions.
- Reduce the input when high price impact makes the quoted rate unacceptable.
- Compare output per input token when assessing the smaller trade.
- Refresh moving quote fields before reviewing the swap authorization.
- Recheck route fees and minimum received if the proposed route changes.
- Inspect any displayed transfer-tax adjustment before adding extra tolerance.
If the refreshed minimum remains unacceptable, decline that quote or reconsider size. Widening the bound becomes an option only after its lower output meets the amount you are prepared to accept.
Why Can a Swap Still Fail After Raising Tolerance?
A swap can fail after raising tolerance because output protection is only one contract condition. Input balance or spending authorization can also prevent execution. A token's transfer rules may cause another failure, and some methods impose a deadline. The message or revert reason can help distinguish these causes. Even a wider bound may remain insufficient if execution-time output deteriorates further.
Sushiswap's V2 router rejects an exact-input swap when the output checked by the selected method falls below the specified minimum. A failed output check blocks completion of that swap. A later reverted swap does not undo a token approval completed in a separate transaction. On EVM networks, an on-chain reverted swap can still charge gas for executed work. A rejected quote or an unsigned wallet request does not establish that the network executed a transaction.
Quote Timing and Execution Exposure
Quote age matters because other swaps and liquidity changes can alter the route before your transaction executes. Network congestion can extend that interval. Publicly visible pending swaps may also face sandwich attacks, where another trader places trades before and after the target swap. That ordering can worsen its execution price while remaining inside its allowed bound. A wider tolerance increases the adverse movement that the output check permits. Tighter bounds constrain that movement, although they do not prevent every attack or every unfavorable trade.
Faster inclusion may reduce time for a quote to change, with network fees as a separate trade-off. It cannot improve the quote's existing impact or promise execution at the original rate. When fresh quotes keep falling below your acceptable output, reconsider the input size or wait for different conditions before authorizing another swap.
Details worth knowing about Sushiswap slippage
Can a Sushiswap Swap Deliver More Tokens Than Its Quote?
The executed output can exceed an earlier quote when the route's conditions improve before execution. An exact-input minimum-output check sets a floor, so satisfying it does not require execution at exactly that minimum. The amount that the transaction delivers, subject to the token's transfer behavior, determines the outcome. The quoted amount remains an estimate until the swap executes.
Does Changing Slippage Settings Update a Pending Swap?
Changing the interface setting does not rewrite a submitted transaction's encoded minimum output. That transaction carries the terms that you authorized when signing it. A new quote can propose a different minimum for a later submission. Separate swap requests may coexist while pending, so changing settings alone does not cancel the original request or remove its execution terms.
Are Token Approvals Affected by Slippage Tolerance?
Token approvals grant spending permission and do not set the swap's execution price. An ERC-20 approval specifies a spender and an allowance. The swap carries its own output constraint when you authorize it. Changing tolerance therefore does not reduce an existing allowance. If your wallet presents approval and swap actions together, their permissions and output controls still have distinct meanings.
Will Splitting a Swap Always Lower Its Total Price Impact?
Splitting an input into separate swaps does not guarantee better combined execution. Sequential trades through the same pool keep changing its reserves; each later trade begins from the state that earlier trades leave. Separate transactions can also add network fees. Improvement depends on changes in available liquidity, routing and market conditions between trades. Compare the combined output and costs before treating smaller pieces as a saving.
When Do Transfer Taxes Affect the Slippage Setting?
Transfer taxes matter when a token deducts value during transfers that the swap requires. Sushiswap supports automatic tax handling for supported trades, and its interface can show a tax-inclusive tolerance adjustment. In the automatic-tax flow, the tax percentage becomes visible only after token approval. Check whether that adjustment already accounts for the deduction before adding extra tolerance manually. The tax and market movement have different causes, even when both influence the output that the swap can deliver.