Liquidity, price impact and slippage explained

A price tells you a rate. Liquidity determines how much can trade around that rate. If a screen displays a token at two dollars, multiplying a large balance by two does not prove the whole balance could be sold for that amount. Execution depends on the actual route and size. The useful comparison is between a reference price, a quote for your amount and the amount ultimately received.

Key takeaways

• Liquidity is the capacity available to trade, not simply the value of an asset or its reported turnover.
• Price impact is the change associated with your own trade against available liquidity.
• Slippage concerns the difference between the quoted and executed outcome as conditions change.
• A minimum-output condition limits what a swap may accept. It does not improve the pool’s underlying price.

What provides liquidity?

In an automated market maker, traders exchange against assets held by a pool, with pricing governed by the pool’s rules. Uniswap’s documentation describes this as an alternative to matching orders in an order book. The amount available relative to the proposed trade matters: a trade that is small for one pool can be large for another. See how Uniswap works.

Keep your research questions separate. How much traded yesterday? How much is available on this route now? What average rate does this particular amount receive? A turnover figure answers the first question, not automatically the other two. A token can move repeatedly between participants, while the immediately available trade capacity remains limited. The actionable evidence for execution is a size-specific quote with its route and timestamp.

Worked example: why a larger swap changes the rate

Consider a simplified constant-product pool containing 100 units of token A and 10,000 units of token B. Its reserve product is 1,000,000. Ignore fees, rounding, token transfer behavior and all other trades. This teaching model follows the reserve relationship described in Uniswap v2’s swap documentation; it is not a live quote or a model of every pool design.

Add 10 A. The A reserve becomes 110. To preserve the product, the B reserve becomes 1,000,000 divided by 110, or approximately 9,090.91 B. The trader receives the difference: about 909.09 B. The average execution rate is therefore about 90.91 B per A. It is lower than the initial reserve ratio of 100 B per A because the trade moves through the pricing curve.

For comparison, adding only 1 A leaves 101 A and approximately 9,900.99 B in the pool. Output is about 99.01 B, much closer to the initial ratio. This arithmetic isolates trade size: the larger swap experiences a worse average rate despite starting from the same pool. Real quotes additionally account for the applicable fees and route. A chart’s last observed price does not perform this calculation for your intended amount.

Price impact is not the same as slippage tolerance

The preceding example has price impact even though nothing else changes while the trader acts. Slippage introduces the time dimension: other activity can change the available execution after a quote is prepared. Uniswap distinguishes these concepts in its swap explanation. A quote can already include substantial price impact before a user selects any slippage tolerance.

Suppose a hypothetical exact-input quote offers 500 B, and its minimum-output setting permits one percent less. The minimum is 495 B under that simple calculation. This does not mean the swap will necessarily lose one percent, nor that its reference-market price impact is capped at one percent. It defines a boundary relative to that quote. Always read the actual minimum shown by the interface because rounding and route details can affect the displayed amount.

Other reasons the received amount can differ

Transaction ordering can affect execution. Ethereum’s MEV documentation describes how actors can benefit from including, excluding or rearranging transactions, including sandwich patterns around swaps. This is a reason to examine execution conditions rather than treating a broad tolerance as harmless. It does not establish that any particular unfavorable swap was attacked. That conclusion needs transaction-level evidence. See Ethereum’s MEV overview.

Also separate network fees from the asset exchange rate. If two hypothetical routes return similar token amounts but have different network costs, the received-token comparison is incomplete. Record those costs in their own units before converting them to a common value. Avoid combining stale dollar conversions with fresh token quotes and then presenting the result as an exact total.

A quote-reading checklist

• Verify the network, input asset and output asset using exact identities.
• Enter the actual comparison size; a quote for one unit does not describe execution for a thousand.
• Read the expected output, minimum output, price impact and quote time separately.
• Identify the route and pool when the interface exposes them; different routes can produce different results.
• Keep network fees and other charges separate from the amount of output tokens.
• If conditions change, obtain a fresh quote instead of assuming an earlier estimate remains valid.

Frequently asked questions

Does high volume guarantee low slippage? No. Past turnover and present execution capacity measure different things. Compare a current quote for the relevant amount and route.

Can I remove price impact by increasing tolerance? No. Increasing tolerance does not add liquidity or change the pool’s pricing relationship; it changes what execution you permit relative to the quote.

Is a reverted swap free? Not necessarily. An Ethereum transaction can consume gas before reverting. A failed outcome can therefore still have a network cost even when the intended swap does not complete.