Market execution & costs

What Is Slippage in Crypto? Price Impact & Liquidity

What is slippage in crypto? Learn how price impact, liquidity and latency change your fill, and how to set slippage tolerance on every trade.

In brief

Slippage is the gap between the price you saw and the price you got. Price impact comes from your own size against pool liquidity, and latency decides how far the market moves before your order lands. Learn to read all three and you can limit what you overpay on entries and exits.

  • Price impact is what your own order does to the price. Check it before you size up.
  • Slippage tolerance is a limit, not a prediction. Set it per trade based on liquidity.
  • Shallow pools punish big orders. Compare trade size to liquidity first.
  • Latency is more than app speed: data freshness, submission and confirmation all count.

Slippage is the difference between the price you expected and the price you actually got. Every trader pays it sometimes. The ones who keep it small know where it comes from: liquidity, order size, and timing.

This guide breaks slippage into its parts so you can set tolerance deliberately, size orders to the pool, and explain fills you could have predicted.

What is slippage in crypto?

Slippage is the gap between the quote on your screen and the amount that settles in your wallet. You see a price, you click, and by the time the transaction executes, the market has moved or your order has pushed it.

It shows up on both sides. Buy slippage means you receive fewer tokens than quoted. Sell slippage means you receive less SOL, ETH or stablecoin than quoted. On volatile new tokens, a few seconds is enough to move the price noticeably.

Slippage has three drivers that people often lump together:

  • Price impact: your own order moving the price.
  • Market movement: other traders buying or selling while your transaction is pending.
  • Route and ordering: how your swap is routed and where it lands relative to other transactions.

What is price impact, and how is it different?

Price impact is the part of the cost caused by your trade size relative to liquidity. It exists even if nothing else in the market moves.

On a DEX pool, the price is set by the reserves in the pool. A swap pulls tokens out and pushes tokens in, and the price slides along the pool’s curve. The bigger your swap compared to the reserves, the further it slides.

Example with stated assumptions: SOL is $180 and a constant-product pool holds $40K of liquidity, roughly $20K on the SOL side, or about 111 SOL. A 2 SOL buy takes about 1.8% off your average price (2 / 113). A 20 SOL buy takes about 15% (20 / 131), because you are drawing a much larger share of the reserves. Real pools differ: concentrated-liquidity pools, fees and routing change the figures. The quote shown before you confirm already includes price impact, which is why you should read it.

The fix is simple: scale size to the pool. If the impact reading makes you wince on the way in, remember it will be at least as painful on the way out.

What is liquidity, and why does it matter more than market cap?

Liquidity is how much of an asset you can trade without moving the price much. In a pool, it is the reserves. On an order book, it is the resting orders near the current price.

Market cap is not liquidity. A token can show a large market cap while its pool holds a small amount of tradable value, because market cap is just price times supply. You cannot sell your whole bag at the displayed price. Always check pool liquidity next to market cap, as covered in crypto market cap vs FDV.

Quick rules of thumb for sizing:

  • Compare your order size to pool liquidity before you buy, and again before you sell.
  • Treat thin pools as exit-risk, not just entry-risk.
  • Split very large orders only when the market can refill between fills. In a static pool, splitting does not remove impact.
  • To read liquidity, open the pool or pair page and find the reserves or the total liquidity figure, then note whether it counts both sides of the pair.

How does slippage tolerance work?

Slippage tolerance is the maximum deviation you accept between the quote and the fill. If the final price would be worse than your limit, the transaction reverts instead of executing.

That makes tolerance a tradeoff:

  • Too tight: the trade fails when the price ticks against you. You may pay network fees on the failed attempt and miss the entry.
  • Too loose: the trade goes through at a worse price than you needed to accept, and you hand extra value to anyone positioned to exploit it.

Practical settings depend on the market. Deep, liquid pairs can run tight. Fast-moving new tokens usually need more room just to land the order. Set tolerance per trade and lower it again when the token calms down. A good habit is to read the quoted price impact first, then set tolerance slightly above it to cover movement while the transaction is pending, rather than defaulting to a huge number. Example: if the quote shows 1.8% impact, a tolerance of 3 to 5% leaves room to land in a moving market. An oversized tolerance also helps sandwich attackers, who place transactions around yours to profit from the price you allow.

What is latency in crypto trading?

Latency is the time between seeing a price and having your trade settled. “Fast” actually covers several separate delays:

  • Interface responsiveness: how quickly the app reacts to your click.
  • Data freshness: how recent the prices and wallet events on screen are.
  • Submission: how long the signed transaction takes to reach the network.
  • Execution and confirmation: when the transaction is processed and counts as confirmed.

Each stage adds time, and the market moves during every one of them. The less time between the data you act on and the confirmed fill, the less slippage from movement you take. That is why having charts, quotes and order entry on one screen matters: it removes the manual steps between reading a price and placing the order.

How can you reduce slippage on every trade?

Work through this checklist before you confirm:

  1. Check the pool’s liquidity and compare it with your order size.
  2. Read the quoted price impact. If it is high, cut the size.
  3. Set slippage tolerance just above that impact, not at the maximum.
  4. Confirm you are on the correct chain and token address.
  5. After the fill, compare the received amount with the quote and note the gap.

The last step builds your intuition. Over a dozen trades you learn which tokens and times of day need wider tolerance and which do not.

Worked example: sizing an entry and setting slippage

Example only; the token and numbers are hypothetical. Assume SOL at $180, a $10,000 account and 1% risk per trade.

  1. Find the pool. A new token has a pool with $40K of liquidity.
  2. Size. You plan a $400 position, about 2.2 SOL. That is 1% of pool liquidity, and the quote shows roughly 2% price impact.
  3. Set tolerance. The token is moving fast, so you set 5%: above the impact, with room for movement, and well short of the maximum.
  4. Submit. The transaction lands about two seconds after you click. The token moved up in that time, and you receive 3.5% fewer tokens than the quote. That is within tolerance, so it fills.
  5. Compare. You log quote versus fill. The gap is 3.5% against a 5% tolerance, so the setting worked.
  6. Plan the exit. On the way out, the same pool absorbs your sell, and a sell of the whole position faces similar impact. If the pool had been $4K, the same $400 would be 10% of the pool, and you would size down or skip the token.

The trigger price of a stop-loss and the price it fills at can also differ in fast or thin markets, so allow for that gap in your sizing.

Common mistakes

  • Setting a huge tolerance by default. It turns every trade into a worse fill.
  • Ignoring exit liquidity. The pool that absorbed your buy has to absorb your sell.
  • Confusing market cap with depth. Large supply value does not mean large reserves.
  • Retrying failed trades at the same settings. A reverted trade tells you the market moved. Re-quote first.

A slippage limit protects the price of a single swap, not the value of the position, and does not protect you from a token that keeps falling after you buy.

Where Zily fits

The Zily trading terminal offers pro charts, quick buy, and presets with per-trade slippage and priority fee across Solana, Base and Ethereum, so you set size and slippage with the live market in view. For venue differences that shape pricing and settlement, read DEX vs CEX. You can also get Zily on desktop or mobile from the apps page.

Frequently asked questions

What is a good slippage setting?

It depends on the token and the pool. Deep pairs work on tight tolerance, while fast-moving new tokens need more room to land. Read the quoted price impact first and set tolerance just above it.

Why did my trade fail with a slippage error?

The price moved past your tolerance before the transaction executed, so it reverted. Re-check the quote, then retry with updated size or a slightly wider limit if the move is real.

Is slippage the same as price impact?

No. Price impact is the effect of your own order on the pool price. Slippage is the total difference between quote and fill, which includes price impact plus any market movement while your transaction was pending.

Does splitting an order reduce slippage?

Only when liquidity can refill between the pieces. In a static pool, several small swaps still consume the same reserves, so the total impact barely changes.

Do failed transactions cost money?

Often yes. A reverted swap can still cost a network fee because the network processed the attempt. Set sensible tolerance so you do not pay for repeated failures.

This guide is educational, not a recommendation to buy, sell, or copy any asset or wallet. Crypto trading can result in substantial losses.