Trading basics

Slippage Tolerance: The Setting That Quietly Costs You Money

By , developer of CoinPriceAlert · Published 28 August 2026 · 3 min read

Slippage Tolerance: The Setting That Quietly Costs You Money
Short answer

A small number in a settings panel that determines how much worse than expected your trade is allowed to fill, and it is regularly set badly in both directions.

What the setting does

When you trade on a decentralised exchange, the price can move between submitting the transaction and it being included in a block. Slippage tolerance is the maximum adverse difference you will accept — beyond that, the transaction reverts rather than filling.

Set it too low and transactions fail repeatedly in volatile conditions, costing gas each time. Set it too high and you accept a materially worse price than you intended.

The risk of setting it high

A high tolerance on a thin market is an invitation. Because the transaction is visible before it is included, a party can trade ahead of it, push the price to the edge of your tolerance, and profit from the difference. The wider you set it, the more there is to take.

This is why the same tolerance that works fine on a deep, liquid pair can be expensive on an illiquid one — the cost scales with how far the price can be pushed.

Practical settings

For deep, liquid pairs, a fraction of a percent is usually sufficient. For thinner markets you may need more, and that requirement is itself information: if a trade needs several percent of tolerance to go through, the market is telling you it cannot absorb your size cleanly.

The better answer is often to split the order into smaller pieces, or to use a limit order on a venue that offers one. Alerts fit naturally here — the alert tells you the level arrived, and a limit order controls what you actually pay for it.

The mistakes that cost the most

Setting thresholds too tight. This is the single most common failure, and it destroys the value of the whole system: alerts that fire constantly train you to dismiss them, so the important one arrives already ignored.

Reacting to a move without checking what caused it. A fall that happens while the whole market falls is a different event from a fall that happens alone, and the correct response differs completely. Checking correlation first takes ten seconds and prevents most panic decisions.

Changing the plan mid-move. The level you chose while calm is better than the one you will choose while watching a candle. If you find yourself widening a stop or moving a target during volatility, that is the moment to close the app rather than the moment to act.

Never reviewing. Most people set up slippage tolerance once and never look at whether it worked. A short monthly review — what fired, what you did, what you would change — compounds faster than any refinement of the setup itself.

CoinPriceAlert

Never miss a move in the markets you follow

Name the price that would change your mind, set it once, and get told when it happens rather than watching a chart for it.

  • Fires about a second after the price hits
  • Runs on our servers, so it reaches you with the app closed
  • Free for 3 alerts — no card, no account

Download the app for real-time notifications

Download on the App Store Get it on Google Play

Frequently asked questions

Is any of this financial advice?

No. Everything here is general educational information about how markets and tools work, not a recommendation to buy or sell anything. Your circumstances, tax position and risk tolerance are specific to you — for decisions that depend on them, speak to a licensed professional in your jurisdiction.

Set an alert for this: crypto price alerts, or every market and alert type. Choosing an app? How the alert apps compare, from their own pricing pages.

Written by

Gurjeet Singh · developer of CoinPriceAlert

Gurjeet Singh, independent developer. He maintains CoinPriceAlert across iOS, Android and the web, and prefers writing a page that says what a feature cannot do over one that does not mention it. How this site is built and where its data comes from →

Keep reading