The frustrating version is familiar: you approve the token, the route looks better than the one you found manually, and then the amount received is lower than the screen led you to expect. The ParaSwap beginner guide is a useful primer on the DEX aggregator that finds routes across liquidity sources. The detail worth settling after your first couple of swaps is the minimum received number, not the headline quote.
ParaSwap can split an order across pools, tokens, and sometimes intermediate routes. That is the point: the best execution is often not sitting in one familiar pool. But the route is quoted at a particular block, while your transaction lands later. Between those moments, someone else can trade through the same liquidity, gas conditions can change, or your own order can move the price.
Read the bottom number before the route
The expected output is an estimate. The minimum output is the condition your transaction carries on-chain: if execution cannot produce at least that amount, the swap reverts. Slippage tolerance determines the distance between the two.
Suppose the quote says 1,000 USDC and the minimum received says 990 USDC. You are allowing execution to vary by up to 10 USDC. That may be perfectly sensible for a liquid, modest-sized swap during a busy period. It is a very different instruction from “get me the best price,” though. You are saying that a worse price is acceptable within that band.
This is where people often mix up price impact and slippage. Price impact is the cost created by consuming available liquidity at the size of your order. Slippage tolerance is the execution wiggle room you permit after the quote. A low-impact route can still fail if your tolerance is too tight; a wide tolerance can complete a swap that has become meaningfully worse.
A practical way to set it
For a first pass, inspect three things together: the expected amount, the minimum amount, and the size of the trade relative to the token’s available liquidity. If the minimum feels uncomfortable, do not solve that by simply raising tolerance. Try reducing the order size or checking whether the route changes when you do.
That small habit also makes routed swaps easier to judge. ParaSwap is doing useful work when it finds a better composite path, but the minimum output is the part that turns that path into your actual instruction. Read it as carefully as the token pair itself.