Every Solana trader has experienced it: you click swap, expecting to receive 10,000 tokens, and your wallet shows 9,400 instead. That 6% difference is slippage, and understanding how it works is the single most important skill for trading on decentralized exchanges. Whether you are swapping SOL for a blue-chip token on Jupiter or aping into a freshly launched memecoin on Raydium, slippage affects every trade you make.
This guide covers exactly what slippage is, why it happens on Solana specifically, how to configure it in every major tool, and the practical settings that will save you money across different trading scenarios.
What Is Slippage?
Slippage is the difference between the price you expect when you submit a trade and the price you actually receive when the trade executes on-chain. It can work in both directions — you might receive fewer tokens than expected (negative slippage) or occasionally more tokens than expected (positive slippage).
Here is a concrete example. You want to buy a memecoin trading at $0.001 per token. You submit a swap for 1 SOL (roughly $140) expecting to receive 140,000 tokens. By the time your transaction lands on-chain and executes, the price has shifted to $0.00105. You receive 133,333 tokens instead of 140,000. That is approximately 4.8% negative slippage.
On Solana, slippage is particularly relevant because transactions confirm in roughly 400 milliseconds. That sounds fast, but in a market where thousands of traders are buying the same token simultaneously — especially during a memecoin launch — prices can move dramatically within that window.
Your slippage tolerance setting tells the DEX smart contract: "Execute this trade only if the price has not moved more than X% from my quoted price. If it has, reject the transaction entirely." Set it too low and your transactions fail. Set it too high and you overpay or get exploited by MEV bots.
Why Slippage Happens on Solana
Slippage is not random. It is a direct consequence of how automated market makers (AMMs) work, combined with network conditions and adversarial actors. Here are the core causes.
AMM Mechanics and the Constant Product Formula
Most Solana DEXs — including Raydium and the liquidity sources Jupiter routes through — use AMM pools based on some variant of the constant product formula: x * y = k. When you buy token B with token A, you are adding token A to the pool and removing token B. The more you remove relative to the pool's total reserves, the more the price shifts against you.
A pool with $5 million in total liquidity can absorb a $1,000 trade with minimal price movement. That same $1,000 trade in a pool with $20,000 in liquidity will move the price dramatically. This is the single biggest driver of slippage on Solana.
Low Liquidity (The Primary Culprit)
The Solana memecoin ecosystem is defined by low-liquidity tokens. A freshly launched Pump.fun token might have only $10,000-$30,000 in its bonding curve. A token that just graduated to Raydium might have $50,000-$100,000 in its initial liquidity pool. At these levels, even a 0.5 SOL buy ($70) can move the price by 1-3%.
Compare this to swapping SOL/USDC on a major pool with $50 million+ in liquidity, where a $10,000 trade barely registers.
Network Congestion
Solana processes thousands of transactions per second, but during high-activity periods — major token launches, market-wide sell-offs, or NFT mints — transaction inclusion can slow down. The longer your transaction sits in the queue, the more the price can shift before execution. During peak congestion in late 2024 and throughout 2025, Solana experienced periods where transaction landing rates dropped significantly, increasing effective slippage for time-sensitive trades.
Concurrent Trading Pressure
When hundreds of traders simultaneously try to buy the same newly launched token, each successive trade executes at a slightly higher price than the last. Your quoted price was based on the pool state at the moment you requested the quote, but by the time your transaction executes, dozens of other buy orders may have already landed, pushing the price up.
MEV and Sandwich Attacks
Maximal Extractable Value (MEV) bots on Solana actively monitor the transaction mempool. When they see your pending swap, they can execute a sandwich attack: buying the token before your transaction (frontrunning), letting your trade execute at a worse price, then immediately selling for a profit (backrunning). This is covered in detail in a dedicated section below.
Slippage vs Price Impact — The Difference Most People Confuse
These two concepts are related but distinct, and confusing them costs traders money.
Price impact is the guaranteed price change your trade will cause based on the current pool state. It is deterministic and calculable before you trade. If you are buying $500 worth of a token from a pool with $10,000 in liquidity, your price impact might be 5%. This means the act of your trade alone moves the price by 5%, and you will receive 5% fewer tokens than the current spot price suggests. Price impact is shown on Jupiter and Raydium before you confirm a trade.
Slippage is the additional, unpredictable price movement that happens between when you submit your transaction and when it executes. It is caused by other trades landing before yours, network delays, or MEV activity.
Here is why this matters practically. You are buying a low-cap token. Jupiter shows: "Price impact: 3.2%." You set your slippage tolerance to 1%. Your transaction fails. Why? Because the 3.2% price impact already exceeds your 1% slippage tolerance once combined with even minimal market movement. You needed your slippage tolerance to be at least 3.2% just to account for your own trade's impact, plus additional buffer for market movement.
Many traders see a low slippage setting as "safe" without realizing that price impact and slippage compound. If a trade shows 4% price impact, you likely need at least 5-7% slippage tolerance to reliably execute.
Tools like Birdeye and DexScreener display liquidity depth for pools, which lets you estimate price impact before you even open a swap interface. Check these first.
How Slippage Settings Work
When you set a slippage tolerance of, say, 3% on Jupiter, you are instructing the swap program: "I expect to receive approximately X tokens. Execute this trade only if I receive at least X minus 3% tokens. If the output would be less than that minimum, revert the entire transaction."
This means:
- At 0.5% slippage: Your trade executes only if the price has moved less than 0.5% against you. Very tight — good for stable, liquid pairs, but will fail frequently on volatile tokens.
- At 5% slippage: Your trade tolerates up to 5% worse execution than quoted. Wider protection window — necessary for lower-liquidity tokens, but gives MEV bots more room to extract value.
- At 15%+ slippage: You are telling the contract you will accept dramatically worse pricing. Only appropriate for extremely low-liquidity tokens where you expect massive price impact and movement.
A failed transaction due to slippage tolerance being too low still costs you a small transaction fee (typically 0.000005 SOL on Solana). In periods of congestion with priority fees, failed transactions can cost 0.001-0.01 SOL each, which adds up fast if you are retrying repeatedly.
Recommended Slippage Settings by Scenario
There is no single correct slippage setting. It depends entirely on what you are trading.
Large-Cap Tokens (SOL, JUP, RAY, BONK, JTO): 0.3% - 1%
These tokens have deep liquidity across multiple pools. A $10,000 trade on SOL/USDC might have 0.01% price impact. Setting slippage to 0.5% gives you plenty of buffer while protecting against sandwich attacks. There is almost never a reason to go above 1% for these pairs.
Mid-Cap Established Tokens ($5M - $100M market cap): 1% - 3%
Tokens that have been trading for weeks or months with reasonable liquidity — think established memecoins that survived their launch phase, or newer DeFi tokens. Pools typically have $500K-$5M in liquidity. A 1-3% setting handles normal market volatility and moderate price impact without leaving excessive room for MEV extraction.
New Memecoins and Low Liquidity Tokens: 5% - 15%
Freshly launched tokens on Raydium, or tokens that recently graduated from Pump.fun bonding curves, often have $20K-$200K in liquidity. Price impact on even small trades can be 2-5%, and concurrent buying pressure during a trend can add another 5-10% movement. Settings of 5-15% are common, though you should be aware you are accepting significant execution risk.
Sniping New Launches on Pump.fun: 15% - 50%+
When a token first launches on Pump.fun and is still on its bonding curve, liquidity is extremely thin. The first few buyers face enormous price impact, and dozens of bots and manual traders are competing to buy simultaneously. Traders using tools like BullX, Photon, or Axiom for early entries often set slippage to 20-50% — accepting that execution quality will be poor in exchange for getting a position at all. Some Telegram bots like Trojan handle this by using fixed SOL amounts with high slippage rather than targeting specific token quantities.
Selling Positions: Add 1-2% Buffer
When selling tokens — especially memecoins — add a slightly higher slippage tolerance than you used to buy. If the token has a sell tax or transfer fee (some Solana tokens implement these), you need the extra buffer. A common frustration is being unable to sell a token because slippage is set too low for the token's built-in fee mechanics.
How to Minimize Slippage
Slippage is unavoidable on DEXs, but you can significantly reduce its impact with these strategies.
Check Liquidity Depth Before Trading
Before you swap, check the token's pool liquidity on Birdeye or DexScreener. Look for the total liquidity value in the trading pair. As a rough rule: if your trade size is more than 1-2% of the pool's total liquidity, expect noticeable price impact. If it is more than 5%, you will experience severe slippage.
For example, if a pool has $100,000 in liquidity and you want to buy $5,000 worth — that is 5% of the pool. Expect 5%+ price impact on top of any market slippage. Consider whether the trade is still worth it at that effective entry price.
Split Large Orders
Instead of swapping 10 SOL into a low-liquidity token in one transaction, split it into 3-4 smaller trades of 2.5 SOL each. Each individual trade has lower price impact, and if the price moves against you after the first few buys, you can stop. This is especially effective for tokens with $50K-$500K in liquidity.
The downside is higher total transaction fees and the risk that other buyers fill orders between your splits, but the net execution is usually better for trades above $500 in low-liquidity pools.
Use Limit Orders
Jupiter offers limit orders that execute at your specified price or better. These eliminate slippage entirely — your order only fills if the price reaches your target. The tradeoff is that your order might never fill if the price moves away from your limit.
For non-urgent trades on established tokens, limit orders are strictly superior to market swaps. You set your price, walk away, and either get filled at your price or not at all.
Leverage Route Optimization
Jupiter aggregates liquidity from dozens of Solana DEXs, including Raydium, Orca, Meteora, and others. Its routing algorithm automatically splits your trade across multiple pools and DEXs to minimize price impact. A $5,000 trade that would cause 3% price impact on a single Raydium pool might only cause 0.8% impact when split across four pools by Jupiter's router.
Always use Jupiter (or a tool that routes through it) rather than swapping directly on a single DEX, unless you specifically need to interact with a particular pool.
Time Your Trades
Solana network congestion follows patterns. Major token launches, high-volatility market events, and peak US trading hours (roughly 14:00-22:00 UTC) tend to have higher congestion. If your trade is not time-sensitive, executing during lower-activity periods can improve transaction landing rates and reduce the chance of slippage from delayed execution.
Use Priority Fees Strategically
Higher priority fees increase the likelihood your transaction is included quickly, reducing the window for price movement. Most trading interfaces let you set priority fee levels. For time-sensitive trades on volatile tokens, a higher priority fee (0.001-0.01 SOL) often saves more in slippage than it costs in fees.
Slippage Settings in Every Major Solana Trading Tool
Here is where to find and adjust slippage in the tools you are most likely using.
Jupiter (Web — jup.ag)
Jupiter displays a gear icon near the top of the swap interface. Click it to open the settings panel. You will see slippage tolerance with preset options (0.3%, 0.5%, 1%) and a custom input field. Jupiter also shows "Minimum Received" below the swap details, which is the exact minimum token amount your trade will accept based on your slippage setting. Jupiter defaults to "Auto" slippage mode which dynamically adjusts based on the token's volatility and pool liquidity — this works well for most trades. For manual control, switch to fixed mode.
Jupiter also offers "MEV Protect" mode in its settings, which routes transactions through Jito bundles to avoid sandwich attacks. Enable this for large trades on liquid pairs.
Raydium (Web — raydium.io)
Raydium has a gear icon in the swap panel. Preset options are 0.5%, 1%, and a custom field. Raydium also shows price impact as a separate percentage — pay attention to this number. If price impact alone is 5%, a 1% slippage setting will not work. Raydium's concentrated liquidity pools (CLMM) can have different slippage characteristics than standard AMM pools — liquidity might be deep at the current price but thin if the price moves, so slippage can spike unexpectedly during volatile moves.
Phantom Wallet (Built-in Swap)
Phantom includes a built-in swap feature powered by Jupiter's routing. Tap the swap icon, then look for the settings gear. You can adjust slippage tolerance there. Phantom defaults to auto slippage, which works well for standard tokens. For memecoins or low-liquidity tokens, you may need to switch to manual and increase the percentage. One common issue: Phantom's swap sometimes shows a slippage warning but does not make it obvious how to change the setting — it is in the gear icon at the top right of the swap screen.
BullX (Web Trading Terminal)
BullX is a popular web-based trading terminal for Solana memecoins. Slippage is configurable per trade in the buy/sell panel. BullX lets you set separate slippage values for buys and sells, which is useful because sell slippage often needs to be higher (especially for tokens with transfer taxes). BullX also supports fixed SOL amount orders rather than percentage-based swaps, which simplifies the mental model — you specify how much SOL to spend and accept whatever tokens you get within your slippage tolerance.
Photon (Web Trading Terminal)
Photon provides slippage controls in its trading panel. Like BullX, it supports separate buy and sell slippage. Photon is known for fast execution and provides priority fee settings alongside slippage, letting you optimize both speed and execution quality. For new token sniping, Photon users often pair high slippage (15-30%) with high priority fees to maximize the chance of early entry.
Axiom (Web Trading Terminal)
Axiom includes slippage settings in its trade execution panel with presets optimized for different token types. Its interface clearly separates price impact from slippage tolerance, making it easier to understand your true cost of execution. Axiom also displays estimated versus actual execution prices after trades complete, which helps you calibrate your settings over time.
Trojan (Telegram Bot)
Trojan is a Telegram-based trading bot. Slippage is configured via bot commands. You can set default slippage for buys and sells separately. Typical commands look like /slippage buy 10 and /slippage sell 15. Trojan also supports auto-slippage mode which adjusts based on the token's recent volatility. For Telegram bots in general, slippage settings tend to be higher than web interfaces because the execution path is longer (message to bot, bot processes, bot submits transaction), adding more time for price movement.
Bloom (Telegram Bot)
Bloom operates similarly to Trojan — configure slippage via bot commands with separate buy and sell values. Bloom provides transaction simulation before execution, showing expected output and price impact, which helps you decide if your slippage setting is appropriate before committing.
Common Slippage Mistakes
Setting Slippage Too Low
The most frequent mistake. You set 0.5% slippage on a volatile memecoin and wonder why every transaction fails. Each failed transaction still costs gas. After 10 failed attempts at 0.000005 SOL each plus priority fees, you have wasted SOL and still have no position. Meanwhile, the token has moved 20% higher. Match your slippage to the token's liquidity and volatility.
Setting Slippage Too High on Liquid Pairs
The opposite mistake. You leave slippage at 10% while swapping SOL/USDC. Your trade will execute, but you have told MEV bots they can extract up to 10% from your trade without it reverting. On a $1,000 swap, that is $100 in potential MEV extraction that you have explicitly permitted. For liquid pairs, keep slippage tight.
Ignoring Price Impact Warnings
Jupiter and Raydium show price impact before you confirm a trade. A "Price impact: 8.5%" warning means your trade alone will move the price 8.5% — before any additional slippage. Many traders dismiss these warnings and are shocked by their final execution price. If price impact exceeds 5%, seriously reconsider the trade size.
Not Adjusting Slippage for Sells
Buying a token at 5% slippage does not mean you can sell it at 5% slippage. Token supply changes, liquidity might have decreased, and some tokens implement sell taxes. Always verify your sell slippage is adequate, especially for memecoins you have held for days or weeks.
Ignoring Token Transfer Fees
Some Solana tokens implement a transfer fee (Token-2022 extension). This fee is separate from slippage but affects your minimum received amount. If a token has a 3% transfer fee and you set 1% slippage, your transaction will fail because the effective cost exceeds your tolerance. Check whether the token uses Token-2022 extensions before setting tight slippage.
MEV and Sandwich Attacks: How They Exploit Your Slippage
MEV (Maximal Extractable Value) is one of the most important concepts for understanding why slippage matters on Solana. Sandwich attacks are the primary way MEV bots exploit retail traders.
How a Sandwich Attack Works
- You submit a swap: 5 SOL for Token X, with 10% slippage tolerance.
- A MEV bot sees your pending transaction in the mempool.
- The bot frontruns you: it buys Token X just before your transaction, pushing the price up.
- Your transaction executes at the higher price — but still within your 10% slippage tolerance, so it does not revert.
- The bot immediately sells (backruns) the tokens it bought in step 3, pocketing the difference.
Your 10% slippage tolerance effectively told the bot: "You can extract up to 10% from me and I will not complain." The bot does not always take the full 10% — it optimizes for profit after gas costs — but your slippage setting is the upper bound of what it can extract.
How to Protect Against Sandwich Attacks
Use Jito bundles. Jito is a Solana MEV-aware transaction system. When your transaction is sent as a Jito bundle, it is not visible in the public mempool, so sandwich bots cannot see it to frontrun. Many Solana trading tools now support Jito bundles natively — Jupiter has "MEV Protect" mode, and tools like BullX, Photon, and Axiom route through Jito by default or as an option.
Keep slippage as low as possible. Even with Jito protection, minimizing your slippage tolerance limits the maximum damage from any form of unfavorable execution. Use the lowest setting that still reliably executes.
Avoid round numbers. Setting slippage to exactly 5% or 10% makes your transaction predictable to MEV searchers. Some traders use values like 4.7% or 11.3% — this is a minor defense but does not hurt.
Trade during lower-activity periods. MEV extraction is more profitable and more competitive during high-volume periods. Trading during quieter hours reduces (but does not eliminate) MEV exposure.
MEV extraction on Solana has grown substantially through 2025 and into 2026. Jito validators process billions of dollars in bundled transactions monthly. While not all MEV is adversarial (arbitrage MEV actually improves market efficiency), sandwich attacks directly harm retail traders. Using MEV-protected transaction submission is no longer optional — it is a baseline requirement for any serious Solana trader.
Quick Reference: Slippage Cheat Sheet
| Scenario | Slippage | Priority Fee | MEV Protection |
|---|
| SOL, USDC, major tokens | 0.3% - 0.5% | Low | Optional |
| Established tokens ($10M+ mcap) | 0.5% - 1% | Normal | Recommended |
| Mid-cap tokens ($1M-$10M) | 1% - 3% | Normal | Recommended |
| New memecoins (recently graduated) | 5% - 15% | High | Required |
| Pump.fun bonding curve snipes | 15% - 50% | Maximum | Required |
| Selling memecoins | Buy slippage + 2-3% | High | Recommended |
Final Takeaways
Slippage is not something that happens to you — it is a parameter you control. The traders who lose the least to slippage are the ones who check liquidity depth before trading, match their slippage tolerance to the specific token and situation, use Jupiter's routing to optimize execution, and protect transactions with Jito bundles.
Start by checking your current default slippage settings in whatever tool you use most. If it is set to a flat 10% across all trades, you are likely overpaying on every liquid pair swap while potentially still failing on volatile memecoin trades. Adjust per trade, pay attention to price impact warnings, and treat slippage tolerance as one of the most important inputs in every transaction you make.
For discovering and comparing Solana trading tools — DEXs, aggregators, bots, and analytics platforms — browse the full directory at MadeOnSol.
