Slippage is one of the most common questions from new crypto users because it directly affects swap outcomes and is also a frequent reason for failed transactions.
What is slippage
Slippage is the difference between the price you expect to receive in a trade and the price at which the transaction actually executes.
In decentralized markets, prices can move quickly because trades are continuously updating liquidity pools. When a swap quote is generated, the app calculates expected output from current pool conditions. Between quote time and final blockchain execution, market state can change. If you want to understand the full swap process step by step, see How crypto swaps work .
If price changes in that window, the final received amount can differ from the estimate. That difference is slippage.
Why slippage happens
Slippage happens because markets are live and transactions are not executed instantly. Even short confirmation delays can expose a swap to changing pool balances.
One common cause is market activity. If other users trade in the same pool before your swap executes, reserve ratios change and AMM pricing changes with them.
Liquidity depth is another factor. In low-liquidity pools, a larger order moves token ratios more aggressively, which usually increases slippage.
Network conditions also matter. Transactions are ordered in blocks, and small ordering changes can affect final execution price.
Example of slippage during a swap
Suppose you initiate a USDC to SOL swap and receive an estimate of 1.50 SOL.
Before your transaction is confirmed, other swaps execute in the same pool and shift reserves.
When your transaction executes, the final result is 1.48 SOL. The difference between 1.50 and 1.48 is slippage.
In highly liquid markets this gap is often small, but in low-liquidity conditions or larger trades it can be more visible.
What is slippage tolerance
Slippage tolerance is the maximum price movement you allow before a swap can execute.
When the transaction is prepared, the app sets a minimum acceptable output based on your tolerance. If final execution falls below that minimum, the swap fails instead of filling at a worse price.
For example, if estimated output is 100 tokens and tolerance is 1%, execution requires at least 99 tokens. If market movement pushes the result lower, the transaction is rejected.
Common slippage tolerance ranges
| Market condition | Typical slippage tolerance |
|---|---|
| Highly liquid pairs (for example SOL/USDC) | 0.1% - 0.5% |
| Moderate liquidity tokens | 0.5% - 1% |
| Low liquidity tokens | 1% - 3% or higher |
These ranges are typical reference points. The right setting depends on volatility, liquidity depth, and urgency.
Slippage vs price impact
Slippage and price impact are related, but they are not the same metric.
Price impact is the price movement caused by your own trade changing pool balances. Slippage is the observed difference between expected output and final output at execution time, which can include your own impact plus other market movement.
| Concept | Meaning |
|---|---|
| Price impact | Price movement caused by the trade itself |
| Slippage | Difference between expected price and execution price |
Understanding both helps explain why swaps can execute with different outcomes from the initial quote.
How to reduce slippage
Slippage cannot be eliminated in live markets, but it can be reduced. Trading deeper liquidity pairs is usually the most effective step. Splitting very large swaps into smaller orders can also reduce pool distortion.
Reviewing quote details before signing is important, especially expected output and estimated price impact. In volatile periods, a realistic tolerance setting can prevent repeated failures while still limiting downside.
Routing quality also matters. Engines that evaluate multiple liquidity sources can often improve execution consistency.
How Monavo handles slippage
When you initiate a swap in Monavo, the system evaluates liquidity across decentralized exchanges and computes an efficient route for the trade.
By accessing multiple pools where beneficial, Monavo helps reduce unnecessary price impact and improve final execution quality.
Before confirmation, Monavo shows estimated output so you can review expected results. After wallet signature, the swap is executed directly on-chain.
Example of slippage tolerance
| Estimated output | Slippage tolerance | Minimum received |
|---|---|---|
| 100 tokens | 1% | 99 tokens |
| 100 tokens | 0.5% | 99.5 tokens |
| 100 tokens | 2% | 98 tokens |
This table shows how tolerance directly defines the minimum acceptable output that protects execution.