Failed Uniswap swaps are common enough to have become a shared DeFi user experience — everyone who uses Uniswap regularly has dealt with the frustration of a swap that consumed gas but didn’t execute the trade. Understanding why swaps fail, how to prevent failures, and what to do when they happen is essential DeFi knowledge.
Common failure reasons
1. Slippage too high
What it means: The price moved more than your slippage tolerance between transaction submission and execution.
Why it happens:
- Other trades between your submission and execution changed the pool price
- Large trades before yours consumed liquidity
- Volatile price action during your transaction’s pending time
- MEV bots deliberately moving price to fail your transaction
Etherscan shows: “INSUFFICIENT_OUTPUT_AMOUNT” or similar
How to fix:
- Increase slippage tolerance (try 1-3% for typical pairs)
- Time your swap for less volatile periods
- Use aggregators (1inch, Paraswap) that route through multiple pools
2. Insufficient gas limit
What it means: Your transaction ran out of gas before completing.
Why it happens:
- Gas limit set manually too low
- Wallet estimated too low for complex swap
- Path through multiple pools required more gas than anticipated
Etherscan shows: “out of gas” error
How to fix:
- Increase gas limit (use “Advanced” options)
- Default often 200,000-300,000 for swaps; increase to 400,000+ for complex routes
- Multi-hop swaps (through multiple pools) need more gas than direct
3. Token approval missing
What it means: You tried to swap a token you haven’t approved Uniswap’s router to spend.
Why it happens:
- First-time swap of specific token
- Approval was revoked
- Attempting to swap more than approved amount (if you used limited approval)
Etherscan shows: “ERC20: insufficient allowance” or similar
How to fix:
- Submit approval transaction first
- Then submit swap transaction
- Uniswap UI usually prompts for both steps automatically
- If manually building, approve first then swap
4. MEV / sandwich attacks
What it means: An MEV bot detected your transaction and profitably manipulated the price around it.
Typical pattern:
- Your transaction sits in mempool briefly
- Bot sees it, trades before you to push price against you
- Your transaction executes at worse price than expected
- Bot trades back to capture profit
- If slippage is close to threshold, your transaction fails from slippage
How to prevent:
- Use Flashbots Protect RPC (free, reduces MEV exposure)
- Use MEV Blocker (alternative protection service)
- Submit transactions through private mempools
- These services keep your transaction hidden from public mempool
5. Liquidity depth insufficient
What it means: The pool doesn’t have enough liquidity for your trade size at acceptable price.
Why it happens:
- Swap is large relative to pool size
- Low-liquidity token being swapped
- Pool imbalanced temporarily
Etherscan shows: Various errors depending on how this manifests
How to fix:
- Reduce swap size (split into multiple smaller swaps)
- Use aggregator (1inch) to split across multiple pools
- Check pool TVL on Uniswap info; swap size should be much smaller than TVL
6. Contract pause or restriction
What it means: The token or pool has been paused or restricted.
Why it happens:
- Emergency pause for security
- Regulatory action
- Token upgrade or migration in progress
- Buyer/seller restrictions in token contract
Etherscan shows: Various, often custom error messages
How to fix:
- Check token’s official announcements
- Wait for pause to lift
- Check if migration is in progress
7. Honey pot tokens
What it means: Token is designed so you can buy but not sell (scam).
Why it happens:
- Token contract has restrictions on selling
- Blacklist prevents your address from selling
- Buy/sell asymmetric taxes
Warning signs:
- Very new token with huge price increase
- Social media hype on unknown platform
- Cannot sell even when Uniswap shows apparent liquidity
- “Good” tax on buy, “high” tax on sell
How to fix:
- Use token scanners before buying (honeypot.is, token sniffer)
- Never buy tokens without research
- If stuck in honey pot, you’ve generally lost your investment
- Avoid buying again
Reading Etherscan transaction details
When your swap fails, Etherscan provides diagnostic information:
Status and error message
Top of transaction:
- Status: “Fail” in red
- Error message below status
- Specific revert reason when available
Internal transactions
Below main transaction:
- Shows the contract calls your transaction made
- Sequence of operations
- Where in the sequence it failed
Interpreting common errors
“INSUFFICIENT_OUTPUT_AMOUNT”: Slippage too low; price moved beyond tolerance.
“TRANSFER_FROM_FAILED”: Usually approval issue; token not approved or insufficient allowance.
“out of gas”: Gas limit too low.
“execution reverted” (no specific reason): Custom contract revert; may need to read contract code for details.
“INVARIANT” or similar pool-specific errors: Pool-specific issue; check pool state.
How to execute Uniswap swaps successfully
Pre-swap checklist
Verify you have the right tokens:
- Correct token (check contract address, not just name)
- Correct network (Ethereum mainnet vs. L2s)
- Sufficient balance
Check pool liquidity:
- Go to Uniswap Info (info.uniswap.org)
- Find your pool pair
- Verify TVL and volume
- Your swap size should be manageable relative to TVL
Current price and spread:
- Compare Uniswap price to centralized exchange prices
- Large discrepancy suggests low liquidity or manipulation
- Check bid-ask spread for reasonableness
Setting slippage
For major pairs (ETH/USDC, WBTC/ETH, etc.):
- 0.5-1% usually sufficient
- Liquid, arbitraged regularly
- Small slippage protects against most scenarios
For mid-tier pairs:
- 1-3% typical
- Less liquidity, more volatility
For small-cap or new tokens:
- 3-10%+ may be needed
- Understand you’re accepting wide price range
- Consider if large swap is appropriate at all
Adaptive slippage:
- Start lower, increase if transactions fail
- Don’t set 10% default — attracts sandwich attacks
Using aggregators
For serious trades:
- 1inch, Paraswap, Matcha, CoWSwap
- Compare prices across multiple DEXs
- Often better execution than pure Uniswap
- Built-in slippage protection
- MEV protection on some aggregators
Transaction submission
Network timing:
- Avoid submitting during gas spikes
- Weekends / Asian hours often cheaper
- Avoid times during known congestion events
Priority fees:
- Higher priority = faster inclusion
- Faster inclusion = less time for MEV
- Balance gas cost vs. inclusion speed
MEV protection:
- Flashbots Protect RPC (add to MetaMask networks)
- MEV Blocker (similar, simple setup)
- Privacy benefits beyond just MEV protection
Chain-specific considerations
Ethereum L1
Pros: Deepest liquidity, most tokens available. Cons: Highest gas, most MEV, slowest. Best for: Large trades where execution matters more than cost.
Arbitrum, Optimism, Base
Pros: Lower gas, less MEV exposure, faster execution. Cons: Less liquidity for some tokens, chain-specific routing. Best for: Medium trades where cost matters.
Uniswap v4 (2026 status)
Pros: Hook architecture, customizable pool behavior, potentially better execution. Cons: More complex, newer ecosystem. Best for: Users comfortable with newer features.
After a failed swap
Debugging workflow
Step 1: Read Etherscan error: Understand specifically what went wrong.
Step 2: Check current conditions:
- Gas prices still reasonable?
- Token still tradeable?
- Pool still has liquidity?
Step 3: Adjust and retry: Based on error:
- Slippage error: Increase tolerance
- Gas error: Increase gas limit
- Approval error: Submit approval first
- MEV: Try Flashbots Protect next time
Step 4: Consider alternative venues: If repeated failures:
- Try aggregator
- Try different DEX (SushiSwap, Curve, Balancer)
- Consider if token actually tradeable
Accepting failures
Small losses are part of DeFi:
- Failed transactions cost gas but not principal
- Lessons learned reduce future failures
- $10-50 gas lost on learning is better than $1,000 on scam tokens
Pattern recognition:
- First few failures are education
- Consistent failures suggest systemic issue (wallet, approach, token)
Security considerations
Token contract risk
Before swapping into any token:
- Verify contract address from official sources
- Don’t trust Uniswap UI search alone (fake tokens exist)
- Check token on Etherscan — verified contract? Audited?
- Use token sniffer tools
Common scams:
- Fake tokens with same name as real ones
- Honey pot tokens (can’t sell)
- Rug pull potential (developer can drain liquidity)
Wallet security
When approving Uniswap router:
- Check you’re approving legitimate Uniswap contract
- Don’t approve unlimited if uncomfortable
- Periodically review approvals via revoke.cash
Phishing risks:
- Fake Uniswap websites
- Malicious browser extensions
- Always verify URL is app.uniswap.org
Related reading
- MetaMask transaction stuck pending?
- Bitcoin transaction stuck or unconfirmed?
- How long do crypto transfers take?
- Best hardware wallets 2026: Ledger vs Trezor
- Is Bitcoin a good investment in 2026?
- Crypto glossary
- Live crypto prices
Failed Uniswap swaps are frustrating but almost always explainable. The combination of slippage management, proper gas settings, token approvals, MEV protection, and careful token selection covers most failure scenarios. Serious DeFi users develop pattern recognition for common issues and build workflows that minimize failures. For occasional users, the key insight is that failures are usually solvable by changing parameters, not a bug in Uniswap itself. When in doubt, check Etherscan for the specific error, adjust accordingly, and try again with lessons learned.
This article is for informational purposes only and is not financial advice. DeFi protocols carry substantial risks including smart contract bugs, oracle failures, and potential total loss of funds. Always verify contract addresses and understand risks before interacting with DeFi protocols.
