How to tell if low liquidity is blocking your swap
A swap can fail or return too little when its trade is large for the pool; compare the quote, minimum received and route before changing settings or retrying.
The Coinvane Desk3 min read

Low liquidity can make a swap return too little or fail when your trade is large compared with the assets available in its pool. Check the quote and the amount you would receive before you approve the transaction. Price impact, the change in price caused by your trade, tends to rise as the trade takes more of a pool’s available assets. For a fuller look at routes and their trade-offs, see thor swap. That detail helps explain why a route can matter as much as the pair.
How can I spot low liquidity in a swap quote?
Compare the quoted output with the amount you would expect at the displayed market price. A large gap can signal high price impact, though fees and the route also affect the final amount. Look for a price impact or liquidity fee figure if the interface shows one. Then check the minimum received: this is the least the swap will deliver if the price moves within your slippage setting.
Slippage is the difference between the quoted and final price. A low minimum received may mean the trade could complete at a worse price than the first quote suggests. If the quote is close to the expected amount but the minimum is much lower, check the slippage setting before proceeding.
What should I check before retrying?
Use the quote screen and transaction status to work out whether pool depth is the problem. Check these details:
- Trade size: Request a quote for a smaller amount. If the estimated output improves relative to the trade size, the larger order may be moving the pool price.
- Route: See whether the swap uses one pool or several. Each pool can add price impact and fees, so a different route may give a better result.
- Pool depth: Compare the pool’s available liquidity with the size of your trade. A deep pool can usually absorb a larger order with less price movement.
- Failure message: Read the transaction or app error. A network delay, missing gas or a token restriction can stop a swap even when liquidity is adequate.
Quotes can change as other trades alter the pool, so refresh the estimate before signing. A failed transaction does not by itself prove that liquidity was too low.
Should I split a large swap into smaller trades?
Try a smaller quote first. It can show whether trade size is driving the price impact, but it does not guarantee that several separate swaps will cost less. Each trade may pay network and pool fees, and the pool can move between transactions. Compare the expected output after all fees before choosing.
For most readers, the better choice is to reduce the trade size or wait for a better quote when the displayed minimum is unacceptable. Do not raise slippage simply to force a trade through: that setting allows a wider gap between the quote and what you receive. If a small swap still fails, check the error and network status before blaming liquidity.