Can positive slippage increase the received amount?

Yes. A swap can execute at a better price than the displayed quote, producing more output than expected. Minimum received is a floor for adverse movement, not a target or upper limit. The executed amount and wallet balance show the actual result. Widening tolerance does not seek positive slippage; it only permits more movement in the unfavorable direction.

Does Auto Slippage work on every network?

No. Auto Slippage availability depends on the network. Where it is unavailable, the interface applies the previously selected fixed setting or its fallback setting. Review the percentage shown for the specific swap before signing because switching networks can change the applicable mode. Automatic selection also does not override low liquidity, token restrictions or a route that cannot satisfy its output condition.

How is tolerance applied to a crosschain swap?

The selected percentage applies independently to each on-chain swap leg in a crosschain route. It does not govern the bridging step itself. A source-chain swap can therefore satisfy its boundary while a destination-chain swap encounters a different price movement. Review each quoted leg and its final asset because one shared percentage does not combine their separate execution conditions.

Do token approvals inherit the swap’s slippage setting?

No. A token approval changes the allowance that a contract may spend, while slippage tolerance defines an acceptable price boundary for the swap. The approval can remain recorded even when the swap fails or is never submitted. Lowering the allowance does not tighten minimum received, and widening tolerance does not grant additional spending permission.

Could a private RPC replace slippage tolerance?

No. An RPC that routes transactions through private relays may reduce exposure to transaction-ordering strategies such as frontrunning or sandwich attacks, but it cannot stop ordinary market movement or change available liquidity. The swap still needs an execution boundary. Keep a tolerance that matches the acceptable minimum output and treat any transaction-routing protection as a separate control.

Are token decimals responsible for high price impact?

No. Token decimals define how contract units map to the displayed balance; they do not create price impact. High price impact comes from the proposed trade relative to available liquidity along the route. Rounding can matter for extremely small displayed amounts, but changing the decimal display does not deepen a pool or improve the underlying exchange rate.

Pancakeswap slippage: tolerance, price impact and swap failures

Pancakeswap slippage tolerance determines how far execution may move from the displayed quote before a swap reverts. Set the tolerance only after checking price impact, route and minimum received. A lower value protects the output boundary, while a higher value accepts a wider execution range and can expose the swap to worse pricing.

Sep 2026 · updated

In short: A sensible tolerance defines the acceptable minimum received; it cannot correct price impact, thin liquidity or token rules that can make a swap fail.

Auto and fixed tolerance options

The swap interface offers Auto Slippage and a fixed percentage. Auto Slippage chooses the tolerance for an eligible swap, while the fixed option leaves that boundary under direct control. Neither option locks the quote. Pool state and market prices can continue changing until the transaction executes.

Auto Slippage derives its percentage from gas cost relative to the output token value where the feature is supported. Check the displayed percentage because network availability and swap conditions affect which setting applies. Automatic selection can reduce avoidable failures, but it cannot guarantee a successful transaction.

A fixed tolerance is useful when the acceptable minimum output is already clear. There is no single percentage that fits every swap. Volatility, pool depth, input size and token transfer rules can change how much room execution needs. A narrow boundary rejects more price movement; a wide boundary accepts a lower possible output.

Changing the tolerance recalculates the minimum received without improving the quoted exchange rate.

A large tolerance should not be used to conceal an unattractive quote. It expands the permitted adverse movement after that quote and may increase exposure to transaction ordering that produces worse execution. If the initial price impact is already unacceptable, reduce the input or abandon the route instead of moving the floor farther down.

Where tolerance stops and price impact begins

Price impact appears in the displayed quote before signing because the proposed input is priced against available liquidity along its route. Slippage describes additional movement between quoting and execution. Reducing the input can improve price impact when trade size is the cause. Raising tolerance cannot repair that initial effect; it merely allows the transaction to execute across a wider range after the quote.

Open full-size image

How does minimum received define the boundary?

Minimum received is the output floor for an exact-input swap. The interface derives this floor from the quoted output and selected tolerance, subject to route logic and token behavior.

Conceptually, if the quoted output is Q and tolerance is t as a decimal, the floor is approximately Q × (1 - t). This relationship explains why a wider percentage produces a lower minimum. Interface rounding, transfer fees encoded by a token and route-specific handling can affect the displayed or delivered units, so the visible minimum is the relevant boundary to review.

The quote is an estimate. Minimum received is the condition that the submitted swap enforces.

Four reversible responses to a moving quote

Before signing, compare adjustments by what they change and what remains observable. Each choice below preserves the option to stop and review a new quote.

Reversible choice	Immediate effect	Observable condition
Use Auto Slippage	Selects a tolerance from eligible swap conditions	Availability depends on the network and the displayed setting
Set a fixed tolerance	Narrows or widens the minimum output boundary	A wider setting permits a lower minimum received
Reduce the input	Moves less value through the quoted liquidity	Price impact may fall when trade size caused it
Refresh and request a new quote	Updates the route and expected output	The previous price and route were not reserved
Order of adjustment	Refresh, compare and reduce size before widening tolerance	Sign only if the displayed minimum remains acceptable

Suppose a quote becomes unusable before confirmation. Request a fresh quote, then check whether its route, output and minimum remain acceptable while you review it. Refreshing submits nothing and shows whether ordinary quote movement caused the mismatch.

If reducing the input lowers price impact, the original size was large relative to the available liquidity. If price impact stays similar but the quote keeps moving, market activity or confirmation delay is more likely. Adjust tolerance modestly only when the new minimum remains acceptable. If there is no usable route, or if a token has an unexplained deduction or transfer restriction, stop rather than repeatedly widening the boundary.

Why did the swap fail after a valid quote?

A valid quote can still fail because it is not a reservation. Execution must satisfy the minimum output, deadline, token rules and transaction requirements when the network processes it. Match the message and receipt to the relevant condition before changing slippage.

INSUFFICIENT_OUTPUT_AMOUNT means execution could not meet the minimum output, often after quote movement or with limited liquidity.
A high price-impact warning points to the proposed size relative to available liquidity. Reducing the input changes that relationship.
An expired swap has passed its execution deadline. Request a fresh quote, then sign and submit it promptly.
A gas-estimation or RPC error can come from network access, wallet configuration or token behavior rather than tolerance.
A wallet without enough of the network’s fee token cannot pay the transaction fee; wider slippage does not fix that.

Why did the swap fail after a valid quote?: A valid quote can still fail because it is not a reservation.; Execution must satisfy the minimum output, deadline, token rules and transaction requirements when the network processes it.; Match the message and receipt to the relevant condition before changing slippage. — Why did the swap fail after a valid quote?

Open full-size image

On an EVM network, a swap that reverts can still consume gas because the network processed the failed transaction. A rejection before broadcast has no on-chain execution to charge. Check the transaction receipt before assuming that an error shown by the interface reached the network.

Token mechanics and other false slippage signals

Some tokens deduct a transfer fee or apply other contract rules when balances move. The router may then receive or deliver a different amount from the ordinary quote path, causing its input or output condition to fail. A documented transfer fee may require room beyond normal market movement, but a guessed percentage can expose the swap to a poor result.

A higher setting cannot bypass a contract that blocks transfers, restricts sellers or otherwise makes the requested exchange impossible. Repeated failure at progressively wider tolerances is therefore evidence to inspect token behavior, not proof that the percentage remains too low. Avoid further approvals when the token identity or transfer rules cannot be established.

Allowance and slippage also govern separate conditions. An allowance authorizes a contract to spend up to a token amount. Slippage governs the swap’s acceptable execution boundary. Changing one does not correct a failure caused by the other.

Choose the next adjustment from the observed state

Use price impact to judge the proposed size, minimum received to judge the worst acceptable output and the receipt to classify a submitted failure. Refresh a moving quote before changing its tolerance. Reduce the input when depth is the constraint. If token rules or route compatibility remain unresolved, stop rather than converting uncertainty into a wider execution range.

Pancakeswap slippage FAQ

Can positive slippage increase the received amount?: Yes. A swap can execute at a better price than the displayed quote, producing more output than expected. Minimum received is a floor for adverse movement, not a target or upper limit. The executed amount and wallet balance show the actual result. Widening tolerance does not seek positive slippage; it only permits more movement in the unfavorable direction.
Does Auto Slippage work on every network?: No. Auto Slippage availability depends on the network. Where it is unavailable, the interface applies the previously selected fixed setting or its fallback setting. Review the percentage shown for the specific swap before signing because switching networks can change the applicable mode. Automatic selection also does not override low liquidity, token restrictions or a route that cannot satisfy its output condition.
How is tolerance applied to a crosschain swap?: The selected percentage applies independently to each on-chain swap leg in a crosschain route. It does not govern the bridging step itself. A source-chain swap can therefore satisfy its boundary while a destination-chain swap encounters a different price movement. Review each quoted leg and its final asset because one shared percentage does not combine their separate execution conditions.
Do token approvals inherit the swap’s slippage setting?: No. A token approval changes the allowance that a contract may spend, while slippage tolerance defines an acceptable price boundary for the swap. The approval can remain recorded even when the swap fails or is never submitted. Lowering the allowance does not tighten minimum received, and widening tolerance does not grant additional spending permission.
Could a private RPC replace slippage tolerance?: No. An RPC that routes transactions through private relays may reduce exposure to transaction-ordering strategies such as frontrunning or sandwich attacks, but it cannot stop ordinary market movement or change available liquidity. The swap still needs an execution boundary. Keep a tolerance that matches the acceptable minimum output and treat any transaction-routing protection as a separate control.
Are token decimals responsible for high price impact?: No. Token decimals define how contract units map to the displayed balance; they do not create price impact. High price impact comes from the proposed trade relative to available liquidity along the route. Rounding can matter for extremely small displayed amounts, but changing the decimal display does not deepen a pool or improve the underlying exchange rate.