Price impact is the effect of your own swap on the available pool price; slippage is the difference between the expected and realized execution price. A quote can already include substantial price impact before you set a slippage tolerance. Therefore, a low tolerance does not turn a poor starting quote into a good one, even when the amount feels small to you.
Put the two effects on a timeline
First, a service calculates what your proposed amount could receive through its available liquidity. That calculation can already reflect how the order moves through the pool. Later, between the quote and execution, the relevant state or price can change. The Uniswap explanation of impact and slippage separates the price change caused by your trade from the difference between expectation and outcome.
A slippage setting usually constrains a particular execution condition, such as the minimum output for an exact-input swap. It is not a universal cap on every cost relative to a price website. Read the transaction's actual terms: an exact-output order has a different constraint, and fees or token mechanics can introduce other deductions. Do not infer the meaning of the setting from the percentage alone.
A small amount can be large relative to the pool
The relevant comparison is between your proposed trade and the liquidity available along its route. Ten units may be modest in your account but substantial against a small pool. A token's total market value or its balance in your wallet is not the same thing as usable liquidity at the quoted price. Uniswap's price-impact reference identifies pool depth as a factor in the impact of a trade.
This also explains why simply raising slippage tolerance does not fix an impact warning. The new setting can permit a worse execution than the existing quote; it does not create additional liquidity. Reducing the input may change the quote, but that needs a fresh comparison including fixed network costs. Do not assume that splitting an order is automatically cheaper: each execution can add costs and the state can change between them.
Work through a quote before choosing a tolerance
Use a deliberately simplified teaching model: a constant-product pool holds 100 units of fictional token A and 100 of fictional token B. Ignore all fees and assume no other activity. The initial reserve ratio is one B per A, but adding ten A does not withdraw ten B. Preserving the product gives a remaining B reserve of 10,000 divided by 110, so the output is about 9.090909 B.
The Uniswap v2 swap documentation describes the constant-product mechanism. Our numbers strip away its real-world fees to isolate the arithmetic; they are not a live quote or a claim about every modern pool. Concentrated liquidity, routing, order books and token transfer rules require their own execution model.
| Stage in the example | Calculation | Result | What it tells you |
|---|---|---|---|
| No-impact reference at the initial reserve ratio | 10 A multiplied by 1 B per A | 10 B | A comparison point, not the executable output |
| Quote after the trade's reserve effect | 100 minus 10,000 divided by 110 | About 9.090909 B | The proposed trade already changes the execution rate |
| Output shortfall against that reference | (10 minus 9.090909) divided by 10 | About 9.09% | A defined teaching comparison, not a universal interface formula |
| Minimum output with a 1% tolerance below the quote | 9.090909 multiplied by 0.99 | 9 B | The tolerance is measured from the quote, not from 10 B |
| Output difference from the initial reference at that minimum | 10 B minus 9 B | 1 B | A 1% setting did not cap the total reference difference at 1% |
The key observation is the base of comparison. At zero further slippage, the quoted 9.090909 B is already below the ten-B reference. At the illustrated minimum, nine B can still satisfy the chosen condition. Neither outcome contradicts a one-percent tolerance, because that tolerance was applied to a different starting amount. An interface may calculate or label impact differently, so retain the definition alongside any percentage you record.
Keep network charges and token deductions in separate lines
A pool price, an application fee, a token's transfer deduction and a network charge are different quantities. Some are included in a displayed output and others are paid in a separate asset. Before comparing two routes, establish the net asset you will actually receive, the asset used for network costs, and whether an additional approval transaction is required. A headline percentage is not enough to compare different fee presentations.
A failed attempt can also have a cost if an on-chain transaction was executed. That is a reason to diagnose the quote and transaction conditions before resubmitting, rather than repeatedly increasing tolerance. Do not change a token approval simply because a price warning appeared. Authorization determines what a contract can spend; it does not improve the price offered by the available liquidity.
A quote-reading checklist
- Record the exact input and quoted output, their assets and networks. Compare amounts that use the same units and token contracts.
- Identify the reference behind the impact figure. A website's displayed token price may not be an executable price for your order.
- Find the transaction's actual limit: minimum output, maximum input or another condition. Note what fees it includes.
- Inspect a fresh quote when changing the amount or route. Do not carry an old percentage into a different transaction.
- Include approvals, network costs and any token transfer deductions in the final comparison. Resolve warnings before signing rather than treating a larger tolerance as a repair.
For background on the asset itself, the native coin and token explanation helps distinguish token balances from the network asset used for gas. The gas-limit guide covers an execution budget, which is another setting entirely. Neither a larger gas limit nor an allowance increase directly removes price impact.
When reviewing a no-account swap, compare the actual offered output and the current order conditions. Inspect the service fee page for stated charges and obtain a fresh quote if the proposed input changes. Keep the original quote, order details and final receiving record together when reconciling the result; a percentage copied from another route cannot replace those records.
FAQ
What is the difference between price impact and slippage?
Impact refers to the price effect of your own trade against the available liquidity. Slippage compares an expected execution price with the realized one, so the two percentages can use different reference points.
Why is price impact too high on a small swap?
The amount can still be large compared with the liquidity available for that route. Check the specific pool or quote instead of comparing the order only with your wallet balance.
What does slippage tolerance mean?
It sets a permitted execution boundary, such as minimum output for an exact-input swap. It does not necessarily cap the total difference from an outside reference price or include every fee.