# Slippage and price impact

> Price impact is the change in expected execution caused by the size of a trader’s own order relative to available liquidity. Slippage is the difference between an expected execution price and the price ultimately received. They can overlap, but market movement, latency, transaction ordering, and execution rules can create slippage beyond quoted price impact.

- Canonical page: https://lynx.finance/glossary/slippage-and-price-impact/
- Published: 2026-07-31
- Updated: 2026-07-31
- Last reviewed: 2026-07-31
- Written by: Lynx Editorial
- Technical review: Lynx Protocol Team
- Category: Pricing and execution
- Also known as: execution slippage, market impact
- Related terms: [Position size and notional value](https://lynx.finance/glossary/position-size-and-notional-value/), [Mark price](https://lynx.finance/glossary/mark-price/), [Index price](https://lynx.finance/glossary/index-price/), [Liquidation](https://lynx.finance/glossary/liquidation/)
- Related articles: [On-chain perpetual futures, explained](https://lynx.finance/blog/onchain-perpetual-futures-explained/), [What is a perp DEX? Decentralized perpetual exchanges explained](https://lynx.finance/blog/what-is-a-perp-dex/)

## In plain English

A large order must consume more available liquidity than a small order. If the available prices worsen as size increases, the order creates price impact. Slippage describes the additional difference between the execution expected when the order was prepared and what actually happened.

A slippage tolerance is a limit or instruction, not a promise that the order will execute. If conditions exceed the limit, the trade may fail or fill only under the venue’s stated rules.

## How it works

Order-book venues consume quoted bids or offers at several price levels. Pool-based venues move along a pricing curve. Oracle-based perpetuals may apply a spread or impact function based on size and market skew. Each mechanism can quote a different expected average execution price.

Between quote and settlement, the market can move. On-chain transactions can also be reordered or delayed. The final execution records the combined result of quoted impact and subsequent slippage.

## Why it matters

Execution quality changes entry price, realized PnL, and the distance to liquidation. Increasing a tolerance does not create liquidity or remove impact; it only permits execution across a wider range. Comparing quotes at several position sizes can reveal when an intended trade is large relative to the market.

## Worked example

An asset displays at `$100`. Because of order size, the venue quotes an expected average execution of `$100.50`. The trader’s own expected price impact is therefore `0.5%`.

Before settlement, conditions move and the order executes at `$100.70`. Slippage relative to the `$100.50` quote is approximately `0.20 ÷ 100.50 = 0.199%`. The total difference from the original displayed price is `0.70%`.

## How it works on Lynx

Lynx does not model entry price impact by walking an order book or an AMM curve. Its documentation describes an artificial spread added to the oracle price when a position opens, based on aggregated spot-market spreads for the traded instrument.

The documented close path uses the oracle price without that artificial spread. Slippage tolerance remains separate: it limits how far an accepted execution may move from the submitted expectation.

## Common misconception

> Slippage and price impact are not interchangeable settings. Impact describes how the order interacts with liquidity; slippage compares expected and actual execution.

## Sources

- [Price impact vs price slippage](https://support.uniswap.org/hc/en-us/articles/8643794102669-Price-Impact-vs-Price-Slippage) — Uniswap Labs (primary)
- [Futures Glossary](https://www.cftc.gov/LearnAndProtect/AdvisoriesAndArticles/CFTCGlossary/index.htm) — U.S. Commodity Futures Trading Commission (regulatory)
- [Fees](https://lynx-finance.gitbook.io/lynx-finance/for-users/fees) — Lynx Finance (primary)