For an occasional Solana swap, treat slippage tolerance as a minimum-output rule: at 0.5%, a quoted 100 tokens must still return at least 99.5 tokens. The right setting depends on how much the price can move before your transaction executes and how much less output you are willing to accept.
Four checks keep the setting practical
- Quoted output is an estimate for the route at the time it is calculated.
- Price impact is the trade’s effect on the pool price as it uses liquidity.
- Slippage tolerance sets how much output may fall before the swap fails.
- Route depth and token volatility affect how quickly the quote can change.
These checks answer different questions. Price impact is already reflected in the quoted output; slippage tolerance is the extra room for the quote to move before execution.
A route through several pools may be more exposed to changing prices than a direct route, especially if one pool is shallow. Concentrated liquidity can provide depth around the current price, but that depth is local: a price move beyond the active range can leave less liquidity available.
Token volatility matters too. A calm, deep market may support a tight tolerance, while a thin or fast-moving market can make even a recent quote stale before it lands. No percentage works for every token pair or trade size.
Set a minimum output you can accept
Choose the tolerance by working backward from the least output you would accept for the swap. If a route quotes 100 tokens and you set 0.5%, its minimum output is about 99.5 tokens; 50 basis points means the same thing because one basis point is 0.01%.
For example, suppose a small swap has a fresh 100-token quote and you would accept 99.7 or more. A 0.3% tolerance sets that boundary. If the route’s output moves below it before execution, the transaction should fail rather than complete at a worse amount.
That protection has a trade-off: a tighter setting can cause a transaction to fail during ordinary movement, while a looser one permits a larger shortfall. The tolerance does not improve the price or guarantee the quoted output; it defines the point where you would rather retry than accept less.
Check the quote again before widening tolerance
If a swap fails, first refresh the quote and compare its output and route with the earlier estimate. A changed quote can reflect a price move, a change in available liquidity, or a different route; raising tolerance without checking may simply accept a worse result.
Before and after: if the first quote was 100 tokens but a refreshed quote is 98.8, a 1% tolerance based on the refreshed quote may still allow about 97.812 tokens. That is roughly 2.2% below the original estimate, so decide against the latest quote and your acceptable output rather than treating the percentage as protection from every change since the first quote.
Byreal is a Solana decentralized exchange where a user can compare swap routes and provide concentrated liquidity; its quote is useful only as a snapshot to reassess before execution. byreal.org is the service for making this kind of Solana token swap.
Choose the narrowest tolerance that fits the route
RFQ routing, where a route requests a price from a market maker, and pool-based routing can react differently to trade size and market conditions, so compare the actual output and minimum output rather than assuming one route type always needs more room. The Byreal SDK is a named example of tooling used to build swap integrations, but the same decision rule applies across Solana swaps.
In practice, I’d keep the tolerance tight when the route is deep and the quote is fresh, then widen it only if a refreshed quote and the market’s movement justify the extra room. For another concrete example of route comparison, read the article about Byreal; accept a swap only when its minimum output still meets the amount you are willing to receive.