Definitions in plain language
Price impact is how much your trade size moves the pool price before the transaction executes — a direct consequence of liquidity depth and order size. If you sell a large amount of a thin token into a small pool, you push the price against yourself. Impact is often shown as a percentage of the spot price you would get for a tiny trade.
Slippage is the maximum additional price movement you accept between the moment you receive a quote and the moment the transaction lands on-chain. Markets move constantly: other traders, arbitrage bots, and block ordering all change the pool state. Slippage tolerance tells the router “fill me at this quote, but revert if output falls below X.”
Impact is about you versus the pool. Slippage is about quote time versus execution time. A trade can have low impact but still fail if slippage is set too tight during a volatile minute — or high impact with generous slippage and still deliver a bad average price because you moved the market yourself.
Side-by-side comparison
| Question | Price impact | Slippage |
|---|---|---|
| What it measures | How your size moves the pool mid-trade | How much price may drift after the quote |
| Main driver | Liquidity depth, route splits, token volatility | Market volatility, block delay, MEV, congestion |
| Who controls it | You (trade size, timing, venue choice) | You (slippage % setting in the wallet) |
| Typical UI signal | “Price impact 4.2%” warning | 0.5% / 1% / 3% tolerance presets |
| Failure mode | Bad fill even if tx succeeds | Transaction reverts (“insufficient output”) |
| Fix if too high | Smaller trade, split orders, better route | Raise tolerance slightly or refresh quote |
For a deeper dive on tolerance presets alone, read crypto slippage explained. For route mechanics on EVM, see how LI.FI routing works.
How aggregators surface both
LI.FI (EVM) and Jupiter (Solana) simulate routes off-chain. They estimate output given current pool reserves. Impact appears when the simulation compares your trade to a baseline “infinite liquidity” price. Slippage becomes a minimum received field — in LI.FI terms toAmountMin — derived from your slippage percentage.
GaurdWallet Exchange displays “you receive” and minimum received before you sign. Treat impact warnings as “you are the whale in this pool” and slippage as “the world may move while this tx confirms.” Both belong in your pre-sign checklist alongside network and token symbols.
Displayed impact is a model, not a guarantee. Extremely fast markets, sandwich attacks, and stale quotes can make reality worse than the preview. Refresh expired quotes — see why swap quotes expire.
When price impact gets dangerous
High impact usually means one or more of: low liquidity on the token you sell, a single-pool route, memecoins with concentrated holdings, or a trade size large relative to daily volume. Symptoms include double-digit impact percentages, receiving far fewer stablecoins than spot price implied, or routes that only succeed through obscure pools.
High impact is not always a scam — sometimes it is the honest math of a thin market. It is still a reason to pause. Ask whether you need the full size now, whether a limit-style workflow exists elsewhere, or whether splitting across time reduces average cost. On bridges, impact can appear on the swap leg inside a cross-chain route even when the bridge fee looks modest.
- Memecoins and launch tokens — pools start tiny; early buyers face brutal impact.
- Stablecoin exits during stress — everyone hits the same pool; impact spikes together.
- Long-tail ERC-20 on L1 — deep liquidity may live on an L2 instead; consider swap vs bridge sequencing.
Splitting trades to reduce impact
Splitting means executing several smaller swaps instead of one block-sized order. Each slice moves the pool less, so marginal price improves — at the cost of multiple gas payments (EVM) or priority fees (Solana) and more signing steps.
- Check impact at full size in Exchange. If above your comfort (many traders use 1–3% as a sanity band on mid-cap assets), note the minimum received.
- Halve the amount, refresh the quote, compare impact and total expected out × 2 mentally.
- Execute slices sequentially; wait for confirmation between slices if the token is hyper-volatile.
- Stop if later slices show rising impact — liquidity may be exhausted or bots may be front-running the pattern.
Splitting does not fix slippage failures by itself — each slice still needs a fresh quote and appropriate tolerance. It also does not replace due diligence on token contracts and approvals; see ERC-20 token approvals.
Slippage tolerance in GaurdWallet
Exchange offers 0.5%, 1%, and 3% presets plus custom values. Tighter slippage protects against bad fills but increases revert risk during volatility. Looser slippage improves landing probability but widens the gap attackers or MEV bots might exploit on public mempools (more relevant on some EVM chains than on Solana’s default path).
Practical habit: start at 1% on liquid pairs (ETH/USDC on major L2). Raise cautiously on illiquid tokens only after impact is already acceptable. If transactions revert repeatedly, refresh the quote before cranking slippage — the market may have moved legitimately.
Impact and slippage on bridges
Cross-chain quotes may include an on-chain swap before bridging or after arrival. Impact applies to those legs; slippage applies to the minimum you accept on the entire route’s output asset. Bridge timing adds minutes where prices drift — another reason quotes carry TTL countdowns in GaurdWallet.
Bridges do not remove impact — they add steps. Read the route tool name in Exchange and cross-check how to swap and bridge before signing multi-hop paths.
FAQ
Can slippage be zero? On volatile pairs, zero slippage mostly guarantees reverts. Even stable pairs need a tiny buffer for rounding.
Does high impact mean the token is a rug? Not necessarily — but combine impact warnings with contract research and wallet hygiene from non-custodial swap safety.
Does Jupiter show impact differently from LI.FI? Labels vary, but the economics are the same: depth vs size vs time.
Should I cancel if impact is 5%? That is a personal risk call — many traders pause above 1–3% on non-meme assets. Reduce size first before widening slippage.
Worked example (illustrative)
Suppose a pool holds $200k of Token A and you sell $20k — roughly 10% of visible liquidity in a constant-product model. Impact might land near several percent even before fees. Slippage at 1% then sets minimum received using the post-impact estimate. If another trader sells $5k in the same block before you, your refreshed quote shows higher impact and lower minimum out — that is market movement plus your size, not “slippage lying.”
Splitting into four $5k swaps might reduce per-slice impact, but four times gas on EVM can erase savings on small L1 trades. On Base or Arbitrum, splitting is more affordable — still compare total expected output minus fees.
MEV and ordering (EVM)
Public mempool swaps can suffer sandwich attacks when slippage is loose. Tight minimum received helps; so does using routes on L2s with different mempool dynamics. Impact and slippage do not measure MEV directly — treat suspiciously good quotes on thin tokens as research signals, not gifts.
Practice in Exchange with sizes you can afford to learn from. Pair this guide with DEX swap best practices before touching illiquid tokens.