Swap Failed on Uniswap or PancakeSwap – How to Fix It
A swap failed message usually comes from one of five causes: insufficient liquidity, slippage tolerance too low, gas estimation failed, transaction reverted, or a pending / stuck swap. This page is a practical, step-by-step fix guide for swap failed uniswap, swap failed pancakeswap, and other dex swap error cases.
Why Crypto Swaps Fail on DEX
DEX swaps are on-chain transactions. If any requirement is not met (pool math, router rules, token transfer rules, gas constraints), the trade fails. A “price shown” in UI does not guarantee execution.
| What you see | Typical reason | Fastest check | Fix direction |
|---|---|---|---|
| Insufficient liquidity | Pool too thin / wrong path / pair missing | Check route + pool reserves | Try different route, reduce size |
| Slippage tolerance too low | Price moved or MEV | Increase slippage slightly + shorten deadline | Use safe slippage ranges |
| Gas estimation failed | Transaction would revert | Try smaller amount; check token restrictions | Confirm token is transferable/tradable |
| Swap reverted | Deadline expired / token transfer rules / router checks | See revert reason; adjust deadline/slippage | Fix parameters, verify token |
| Swap pending | Gas too low / network congestion | Check tx in explorer | Speed up / replace tx |
Most common “fast fix”
- Reduce swap size
- Use sane slippage (don’t go extreme)
- Shorten deadline (prevents stale quotes)
- Confirm you picked the correct token address
Most common “hard stop”
- Token transfer restrictions (honeypot-like behavior)
- Blacklist / anti-bot gating
- Liquidity removed or route invalid
Common Swap Errors Explained
Most DEX UIs group many on-chain failures under generic “swap failed”. These are the patterns that matter.
swap exact tokens for ETH failed
- Slippage too low during fast price movement
- Tax token makes output smaller than expected
- Route uses a thin pool or wrong pair
uniswap transaction reverted
- Deadline expired or minOut not met
- Token transfer returns false / reverts
- Router checks fail due to state change
If you see repeated reverts on tiny swaps with a verified token address, treat it as high-risk token behavior—not a UI bug.
Insufficient Liquidity for This Trade
Liquidity is the pool depth behind the quote. Thin pools can show a quote but fail at execution (or complete with extreme price impact).
What to do
- Reduce trade size (often fixes immediately)
- Try a different route (stable pair → blue-chip pair)
- Verify you selected the correct token contract
Red flags
- Pool reserves drop suddenly
- Only buys succeed but sells fail (restriction risk)
- Price impact is massive even for small swaps
Slippage Tolerance Too Low
Slippage protects you from receiving less than expected. If it’s too low, swaps fail when the price moves (or MEV changes state).
| Trade type | Typical slippage | When to increase | When NOT to increase |
|---|---|---|---|
| Stable ↔ stable | 0.1% – 0.5% | Only if pool is thin | Don’t go high — indicates bad route |
| Blue-chip ↔ blue-chip | 0.5% – 1.0% | High volatility moments | If you suspect tax token behavior |
| Low-cap / meme | 1% – 5% | Only for genuine volatility | If sells revert or output collapses (risk) |
If the only way to swap is “extreme slippage,” you’re often dealing with thin liquidity, taxes, or malicious token mechanics.
Gas Estimation Failed
“Gas estimation failed” often means the transaction would revert. It can be caused by token restrictions, invalid parameters, or a stale quote.
Fix checklist
- Reduce amount and try again
- Increase slippage slightly (not extreme)
- Shorten the deadline
- Confirm token address (avoid fake clones)
If it persists
- Token transfer may revert (restriction/tax)
- Route or pool may be invalid
- Try another DEX router on the same chain
Swap Transaction Reverted
A revert can happen when minimum received is not met, deadline expired, token transfer fails, or contract rules reject the trade.
Fast actions
- Set a reasonable deadline (e.g., 5–10 minutes)
- Re-check selected token address
- Try a tiny swap first
- If it’s a tax token, minOut may be too strict
How to Fix Failed Token Swaps
Run this workflow in order for any dex swap error on Uniswap or PancakeSwap.
Step-by-step runbook
- Verify the token address (don’t trust tickers/logos).
- Try a tiny swap to confirm execution.
- Check liquidity (thin pools fail or cause huge price impact).
- Set slippage to a safe range (see “Best settings”).
- Set deadline to 5–10 minutes.
- Check gas: if pending, speed up/replace transaction.
Paste a tx hash or token address (optional)
No external calls—this just helps you keep notes consistent.
When to stop
- Repeated reverts on tiny swaps
- Only buys work but sells fail
- Liquidity looks drained or moved
Best Settings for Successful Swaps
These defaults reduce failures without pushing you into dangerous “infinite slippage” territory.
Recommended defaults
- Deadline: 5–10 minutes
- Slippage: 0.5–1% (blue-chip), 1–3% (volatile)
- Trade size: start tiny, scale only after success
Do NOT do this
- Don’t jump to extreme slippage as a “fix”
- Don’t swap unknown tokens without verifying address
- Don’t ignore repeated reverts—often token-level risk
Authoritative sources (unique set for this page)
Protocol and wallet references used in this guide:
Trust & Update Notes
FAQ – Swap Failed Errors
Why does my swap fail on Uniswap?
The most common causes are slippage too low, insufficient liquidity, or a transaction revert due to token/router rules. Start with a tiny swap, verify token address, then adjust slippage and deadline.
Why does PancakeSwap show “swap failed”?
PancakeSwap failures are usually liquidity/route issues, slippage settings, or token transfer restrictions. If tiny swaps revert repeatedly, treat it as token-level risk.
What does “swap exact tokens for ETH failed” mean?
It often means the minimum received wasn’t met (price moved beyond slippage), liquidity is too thin, or the token has taxes/restrictions that reduce output below your minOut.
How much slippage should I use to avoid failed swaps?
Typical ranges: 0.1–0.5% for stable swaps, 0.5–1% for blue-chip pairs, and 1–3% for volatile tokens. If execution requires extreme slippage, investigate liquidity and token mechanics.
What does “gas estimation failed” indicate?
Often it means the transaction would revert. Reduce amount, verify token address, check liquidity/route, and only increase slippage slightly if volatility explains the failure.
My DEX swap is pending — what should I do?
Pending swaps usually mean gas is too low or the network is congested. Check the transaction in a block explorer and use your wallet’s speed-up/replace feature if needed.
Is “transaction reverted” always a scam token?
Not always. It can be deadline/slippage, routing, or state change. But repeated reverts on tiny swaps with verified addresses can indicate token transfer restrictions or malicious mechanics.
What are the safest “best settings” for swaps?
Use a 5–10 minute deadline, start with a tiny trade, keep slippage reasonable (0.5–1% for blue-chip), and verify token addresses. Use official docs: Uniswap Support and PancakeSwap Docs.
Primary keywords: swap failed, swap failed uniswap, swap failed pancakeswap, dex swap error, crypto swap failed. Long-tail: swap exact tokens for eth failed, uniswap transaction reverted, pancakeswap swap error, dex swap pending, crypto swap error.