Slippage and price impact answer different questions

The short answer

Price impact describes how a trade affects its own execution economics, because of the liquidity available on the route it uses. Slippage describes the difference between an expected quote and the eventual execution, usually because market conditions changed or the quote became stale. They have different causes and different remedies.

A worked illustration

Imagine the current marginal price suggests 100 tokens for your input amount. The route's quoted output is 95, because your order moves through limited liquidity and includes whatever costs the quote models. That gap of five tokens is price impact plus modelled fees. Loosening a slippage setting does not recover it.

Now apply a 5% output tolerance to the quoted 95. The simplified minimum received is 95 × 0.95 = 90.25 tokens. This is an illustration; platforms define tolerance differently, and some apply it to a different reference. A wider tolerance permits a worse fill. A tighter tolerance makes the transaction more likely to fail when the market moves. Neither makes execution cheaper.

Reading a quote properly

Before changing any setting, check:

• Quote age. How long ago was this computed?
• Pool depth and route. Is this a single pool or a split route, and which pools?
• Input size. Is the order large relative to reserves?
• Displayed impact. Does the interface state it, and on what basis?
• Fee treatment. Which fees are already inside the quoted output?
• Minimum received. What is the worst acceptable outcome you are authorising?

When impact is high, the setting is not the answer

Excessive price impact is information: the route cannot absorb your size at an acceptable price. The useful responses are a smaller position, a different accessible route, splitting over time while accepting new risks, or skipping the trade. Raising tolerance in response simply authorises the bad fill you were being warned about.

When a transaction fails

Read the error and check explorer evidence before resubmitting. Repeated attempts can incur costs, and depending on the platform they can duplicate execution if an earlier attempt eventually lands. Increasing tolerance repeatedly without diagnosing the cause converts a technical problem into a poor fill.

Common causes that look identical in the interface include a stale quote, a route that no longer exists, a migration in progress, an insufficient native balance for fees, and a transfer restriction on the token itself.

After confirmation

Record the actual acquired quantity and the total cost paid, not the displayed entry price. Settings are inputs to a process; they are not evidence that the process produced what you expected. Your journal entry should let you reconstruct the fill without trusting your memory of the screen.

Common mistakes

• Treating tolerance as a quality dial rather than a failure threshold.
• Assuming the displayed impact includes every fee, or that it includes none.
• Comparing quoted output across interfaces without checking which costs each one includes.
• Blaming slippage for a loss that was actually price impact on an oversized order.

What this cannot establish

A good quote does not mean a good trade, and a successful fill says nothing about whether you will be able to exit at size later. Tolerance settings protect against one narrow failure mode only.

Checklist

• Quote age checked
• Route and pool identified
• Impact distinguished from tolerance
• Minimum received understood as a floor, not a target
• Failure diagnosed before any resubmission
• Acquired quantity and total cost recorded afterwards