Price impact is the price movement your own trade causes by changing the pool’s balance. Slippage is the price movement caused by everyone else between your quote and your execution. They produce similar-looking numbers on a swap screen and have completely different causes, so the fixes are different too: price impact is solved by trading smaller or splitting the order, slippage by adjusting a tolerance setting. Traders who treat them as one thing routinely raise slippage tolerance to fix a price impact problem, which permits the loss instead of preventing it.

Key Facts

• Price impact is deterministic — calculable from pool depth and your trade size before you send anything.
• Slippage is probabilistic — it depends on what other people do in the seconds you are waiting.
• Price impact exists even if you are the only trader in the world.
• Slippage exists even if your trade is tiny.
• Price impact scales with your size relative to pool depth, not with the dollar amount.
• Raising slippage tolerance never reduces price impact — it only lets a high-impact trade through.
• Both are shown separately on good swap interfaces, and both are worth reading before confirming.

Why an AMM Charges You for Size

A constant-product pool holds two assets and keeps their product constant. Take tokens out and you must put SOL in, which shifts the ratio and therefore the price — every unit you buy costs slightly more than the one before. That is price impact, and it is a mathematical property of how AMM pools work rather than a fee anyone charges.

The magnitude depends entirely on your size relative to the pool. A $500 buy against a $2M pool moves almost nothing. The same $500 against a $8,000 pool is a large fraction of the depth and moves the price several percent. This is why “how much can I buy” has no fixed answer and must be read against the specific pair.

Side by Side

	Price impact	Slippage
Caused by	Your own trade size	Other traders during your wait
Predictable	Yes, exactly	No, only bounded by your tolerance
Shown before you confirm	Yes, as a percentage	Only as a limit you set
Fixed by	Smaller size, splitting, deeper pool	Tolerance setting, faster execution
Affected by priority fee	No	Yes — faster inclusion means less drift
Exploitable by bots	Indirectly	Directly, via sandwiching

The “fixed by” row is the practical takeaway. If the interface warns you of 14% price impact, no setting anywhere will improve that outcome — the pool is simply too thin for the size you want. Splitting the trade into pieces helps only slightly, since each piece still moves the pool and the next piece starts from the worse price. The genuine solutions are trading less or waiting for deeper liquidity.

The Expensive Mistake

Here is the sequence that costs people money. A trader tries to sell a large memecoin position, the swap fails, they assume it is a slippage problem and raise tolerance from 3% to 30%. The swap now succeeds — at a price 25% below quote, because the failure was never about other traders. It was their own order eating through a shallow pool, and the higher tolerance simply removed the guard that had been stopping them.

Reading the impact number before adjusting anything prevents this entirely. If price impact is already 20% at the size you entered, the swap failing is the interface protecting you. Reduce the size until impact is tolerable, then set slippage tolerance to cover only genuine market drift on top.

How Routing Changes the Maths

Price impact is calculated per pool, so a trade split across several pools has lower impact than the same trade forced through one. This is the main thing aggregators do: Jupiter will divide an order across multiple venues specifically to keep each pool’s movement small, which frequently produces a better result than the deepest single pool would. Comparing quoted impact against the pool depth shown on DEXScreener is a quick sanity check on whether a route is doing its job — a trade with far lower impact than the main pool alone would imply is being split, which is what you want.

Sizing a Position in $DOLAN

DOLAN Duck ($DOLAN) has a fixed 98.3M supply distributed across roughly 10,700 holders, and the number that determines what any of those holders can actually exit with is pool depth, not supply. The useful discipline is to check price impact for your intended exit size before you enter, not after — a position you can build for 1% impact but only exit for 12% is a position sized wrong from the start, regardless of how the chart looks. That check takes seconds on any interface that shows impact separately, and running it through an aggregator that splits routes generally gives the most honest number, because it reflects the entire available liquidity rather than one pool.