Q&A · Community Q&A

How Do I Calculate Price Slippage as a Percentage? Formula and Worked Examples

Illustration of a token swap comparing a taller expected stack with a shorter received stack under a magnifying glass
On this page
Community question

Good day everyone, this is the second time I exchanged BUSD for CAKE in PancakeSwap's liquidity pool only to get less than I bargained for in return. I intended to get 100 CAKE and exchanged 2018.3 BUSD for it, only to get 93 tokens. It's enough to be an annoyance. I then learned that I can adjust the slippage tolerance, but I don't know how much 0.8% in slippage would be. How do I work this out?

The formula

Slippage as a percentage is the shortfall between what you were quoted and what you got, divided by what you were quoted:

Slippage (%) = (expected amount − amount received) ÷ expected amount × 100

If a DEX quoted you 100 tokens and you received 93, slippage was (100 − 93) ÷ 100 × 100 = 7%. A negative result means positive slippage: you received more than quoted.

The same calculation with prices

Traders often think in prices rather than amounts. For a purchase:

Slippage (%) = (execution price − quoted price) ÷ quoted price × 100

For a sale, flip the sign: (quoted price − execution price) ÷ quoted price × 100.

The two methods give slightly different answers because price is the inverse of amount. Here’s the question’s example, swapping 2,018.3 BUSD for an expected 100 CAKE and receiving 93:

Method Calculation Result
By amount received (100 − 93) ÷ 100 7.0%
By price paid Quoted 20.183 BUSD per CAKE, paid 2,018.3 ÷ 93 = 21.703; (21.703 − 20.183) ÷ 20.183 7.5%

Both are “right”. Just use the same method every time, and note that DEX interfaces and slippage tolerance settings work in amounts.

(BUSD, the Binance-branded stablecoin in this example, has since been wound down. The math is the same for any pair.)

Turning a slippage tolerance into a minimum received

Your slippage tolerance is the worst result you’ll accept relative to the quote. The DEX turns it into a hard limit that is written into your transaction:

Minimum received = quoted output × (1 − tolerance)

With a 0.8% tolerance on a 100 CAKE quote, that’s 100 × (1 − 0.008) = 99.2 CAKE. If the swap would deliver less, it reverts and you keep your BUSD, though you still pay the network fee.

Quoted output 100 CAKE Apply 0.8%tolerance Minimum received 99.2 CAKE At least 99.2 CAKE Swap settles Below 99.2 CAKE Swap reverts
The tolerance becomes a hard minimum in the transaction. The swap can settle at or above 99.2 CAKE, but not below it.

Some swaps are set the other way round, with an exact output and a maximum input (for example, “I want exactly 100 CAKE”). Then:

Maximum sold = quoted input × (1 + tolerance)

So 2,018.3 × 1.008 = 2,034.45 BUSD at most.

Quick reference for a 1,000 USDC quote:

Tolerance Minimum received Most you could lose to slippage
0.1% 999.00 1.00 USDC
0.5% 995.00 5.00 USDC
0.8% 992.00 8.00 USDC
1% 990.00 10.00 USDC
3% 970.00 30.00 USDC

Why did I get 7% less with a tolerance under 1%?

A normal swap can’t settle below its minimum received. So if you set 0.8% and got 7% less than you “expected”, your expectation probably didn’t come from the DEX’s final quote. Common reasons:

  1. Price impact was already in the quote. On an automated market maker, your own trade moves the price along the pool’s curve. A large trade in a small pool can lose several percent this way. The quote and the “minimum received” already include that loss, and tolerance protects you only against further moves. Our explainer on slippage in liquidity pools has a worked constant-product example.
  2. You compared against the market price, not the quote. If “100 CAKE” came from a price chart, the gap includes price impact and fees.
  3. Pool fees. PancakeSwap v2 pools charge 0.25% per hop, and a route through two pools pays it twice.
  4. Token taxes. Some tokens take a percentage on every transfer. That shortfall shows up after the swap and is a common sign of a risky token.
  5. The tolerance setting didn’t apply. Auto-slippage may have chosen a different value. PancakeSwap’s auto mode picks between 0.5% and 5%, for example. A setting that was changed on another device or app also won’t carry over.

To work out which one it was, open the transaction on a block explorer. Compare the amount out with the “minimum received” encoded in the swap and the price-impact figure the interface showed.

Where the shortfall can enter Conceptual — not to scale Market priceor price chart Price impactand fees DEX final quote Execution slippagecapped by tolerance Minimum received Below it: swap reverts
Price impact and fees can already separate a market-price expectation from the DEX's final quote. Tolerance only limits the further move from the quote to the minimum received.

Slippage, price impact and fees

Term What it is Known before you sign?
Price impact The price move caused by your own trade in the pool Yes, shown in the quote
Fees Pool or protocol fee, plus gas fees Yes
Execution slippage Price changes between quote and confirmation, from other trades, volatility or MEV bots No, only capped by your tolerance

Uniswap’s documentation describes the same split. Price impact depends on liquidity at the current price, while slippage tolerance caps how far the price can move before the trade fails.

How to keep slippage low

  • Check price impact before you sign. If it’s over 1–2% on a mainstream pair, try a smaller trade, a deeper pool or a DEX aggregator.
  • Keep tolerance as tight as the trade allows. Too low and swaps fail. Too high and sandwich bots can take the difference. See slippage tolerance.
  • Split large orders, or use limit orders where the DEX supports them.
  • Volatile tokens need more care. For how to estimate slippage when prices are moving fast, see calculating slippage for volatile coins.

Risks

  • High tolerance is an open invitation. A 10% or higher setting lets bots and bad pools take up to that much. It is rarely needed for legitimate tokens.
  • Very high slippage on a new token is a red flag. It can mean a hidden transfer tax, a pool about to be drained, or a token designed so you can’t sell. See crypto scam red flags.
  • Failed swaps still cost gas on most chains.

For more on the mechanics, see the glossary entry on slippage or the DEXs and AMMs guide.

Frequently asked questions

What is the formula for slippage percentage?

Slippage (%) = (expected amount − amount received) ÷ expected amount × 100. Using prices instead: (execution price − quoted price) ÷ quoted price × 100 for a buy.

How much is 0.8% slippage?

0.8% of the amount you're quoted. On a quote of 100 tokens, 0.8% is 0.8 tokens, so the minimum you'd accept is 99.2. On a 2,000 USDT trade, 0.8% is 16 USDT.

How do I calculate minimum received from slippage tolerance?

Minimum received = quoted output × (1 − tolerance). For a 1,000 USDC quote at 0.5% tolerance, that's 1,000 × 0.995 = 995 USDC.

Is price impact the same as slippage?

No. Price impact is the move your own trade causes in the pool, and it's already built into the quote. Slippage tolerance only covers further price changes between the quote and execution.

Does slippage include trading fees?

The DEX quote usually already deducts the pool fee, such as 0.25% per hop on PancakeSwap v2 pools. If you compare what you received against the market price instead of the quote, fees will show up as part of the gap.

Sources

  1. PancakeSwap docs: Token swaps (fees per hop)
  2. PancakeSwap docs: Auto slippage
  3. Uniswap developer docs: Swaps (price impact and slippage)
  4. Uniswap Labs blog: What is slippage in crypto?

Educational content, not financial advice. DeFi carries risk, including total loss of funds.

↑↓ to navigate ↵ to open Esc to close