Price Impact Versus Slippage
If you've ever swapped tokens on Solana and watched the numbers on your screen shift, you've run into two related but different concepts: price impact and slippage tolerance. Confusing them is common, and it can cost you money. Let's untangle them.
What Price Impact Actually Is
Price impact is the effect your own trade has on the market price of a token, specifically within the liquidity pool you're trading against.
Automated market makers (AMMs) like Raydium or Orca use pools of two tokens sitting in a smart contract. When you swap, you're not trading against a person — you're trading against that pool's balance. Every swap shifts the ratio of tokens in the pool, which shifts the price.
The bigger your trade relative to the pool's total liquidity, the more you push the price against yourself. A $50 swap in a deep pool with millions of dollars in liquidity might move the price by 0.01%. That same $50 in a thin, newly launched pool could move it by 5% or more.
Price impact is not a bug or a fee — it's math. It's baked into how AMMs work, and it happens *before* you even think about slippage.
What Slippage Tolerance Actually Is
Slippage tolerance is a setting you control. It's the maximum difference you're willing to accept between the price you saw when you clicked "swap" and the price you actually get when the transaction confirms on-chain.
Why would those prices differ? Because time passes between when you submit a transaction and when it lands in a block. Other trades might execute first, pool balances shift, and by the time your swap actually runs, conditions have changed slightly.
Set your slippage tolerance too tight (say, 0.1%) on a volatile token, and your transaction will likely fail because the price moved outside your allowed range. Set it too loose (say, 5% or more), and you're exposed to bots that can exploit the gap between what you expected and what you're willing to accept — a practice known as sandwich attacking.
Where They Show Up on the Swap Screen
Most Solana swap interfaces display three related numbers before you confirm a trade:
- Price impact — how much your trade itself is expected to move the pool price, based on its size.
- Slippage tolerance — the buffer you've set, usually adjustable (0.1%, 0.5%, 1%, custom).
- Minimum received — the worst-case amount of tokens you'll get, combining both factors.
If price impact is already high, no slippage setting will fix that — you're paying for the trade size, not the tolerance. Slippage only protects you from *unexpected* price movement between submission and confirmation, not the *expected* movement your own order causes.
A Concrete Example
Say you want to swap 500 SOL for a small-cap SPL token on Raydium. The pool only has $200,000 in total liquidity. The interface shows a price impact of 8% — your trade alone is large enough to push the price significantly just by executing.
Even if you set slippage tolerance to 0.5% (a reasonable, tight setting), your minimum received will already reflect that 8% impact. The slippage setting doesn't reduce the impact — it just protects you from further, unrelated price movement while your transaction is in flight.
In this case, the fix isn't adjusting slippage. It's either trading a smaller size, splitting the trade into parts, or choosing a token with deeper liquidity.
Common Mistake
Traders often raise their slippage tolerance to "fix" a failed transaction without checking price impact first. This can mean unknowingly accepting a much worse price than intended, especially on illiquid pools, and it opens the door to sandwich bots that specifically target wide slippage settings.
On MAPLUStrade
Before confirming a swap, check MAPLUStrade's trade preview panel, which separates price impact and slippage tolerance into distinct fields so you're not guessing which one is driving your final price. Use the liquidity depth indicator to see pool size before sizing your trade, and the route comparison tool to check if splitting a large order across multiple pools reduces total impact.
Recap
Price impact comes from the size of your own trade relative to pool liquidity — no setting fixes it. Slippage tolerance protects you from unrelated price changes between submission and confirmation, so treat them separately, not as one dial.
*This lesson is educational only and not financial advice. Trading crypto involves risk of loss.*