Why Swap Route Estimates Differ Across Interfaces
Two swap interfaces can quote different outputs because they may use different pools, route splits, fee assumptions and quote times; compare what each estimate includes.
The Aeterna Sol Editors

Two interfaces can show different estimates for the same swap. That means the displayed output is a quote based on each interface’s route and assumptions, not a universal price.
A route is the path a swap takes through one or more liquidity pools. The interface searches for a way to exchange your input token for the token you want, then estimates what you may receive after the route’s costs and effects.
One interface may use a direct pool, while another may split the trade across several pools or pass through an intermediate token. A more complex route can find more liquidity, but it can also add fees or more opportunities for the final output to change.
If you want a closer look at how route choices shape a quote, the fuller guide to thor swap explains the trade-offs. The same comparison helps when estimates differ across interfaces: look at the route and the amount you are expected to receive.
Why can the same swap use different routes?
Interfaces can search different pools and route combinations, so they may find different ways to fill the same trade. A pool is a reserve of tokens that traders swap against.
For a small trade, a direct pool may offer enough liquidity. For a larger trade, the interface may look for other pools or divide the trade among them. A split can reduce the effect of taking tokens from one pool, though the extra route legs can add their own costs.
Available routes also depend on what the interface can see and how it searches. It may have different pool data, supported networks, token lists or route settings. Even if two interfaces access the same pools, they may choose different paths because their search methods or trade-off settings differ.
Compare the route details when they are shown. Check which tokens the swap passes through and whether it uses one pool or several. The route that looks shortest is not automatically the one with the best expected output.
What makes the quoted output change?
Pool liquidity, trading fees and price impact can all change the amount an interface estimates you will receive. Price impact is the effect your trade has on the pool’s exchange price as it uses available reserves.
When a trade takes a large share of the available liquidity, each part of the trade may execute at a less favourable price. A route through several pools can spread that impact, but every pool may charge a fee. The estimate reflects the combined effect of the route it has selected.
Interfaces can also present costs differently. One may show an estimated network fee separately, while another may emphasize the amount left after its listed swap fees. Check the details rather than assuming that similarly named output figures include the same costs.
Quotes are tied to conditions at the time they are requested. Pool balances and prices can move before you submit the swap, so a refreshed estimate may differ even when you use the same interface and route. Slippage settings set how much the executed result may vary from the quote before the transaction is rejected.
How should you compare two swap estimates?
Compare the expected amount you receive and the assumptions behind it. The headline rate alone can hide route fees, price impact, network costs or different slippage limits.
Use this order when checking two quotes:
- Confirm that both estimates use the same input amount, tokens and network.
- Compare the expected output, including any costs shown separately.
- Inspect the route, its pools and any intermediate tokens.
- Check the quote time and slippage setting before deciding whether to submit.
If the figures still differ, inspect the route details and refresh both quotes. Differences can come from a changed pool state or from each interface finding a different route; the output figure by itself does not show which one is responsible.
For most swaps, the more useful comparison is the expected final amount after the listed costs, alongside the route and slippage setting. A route is a means to that result, not a quality score on its own. Choose the estimate whose assumptions you can understand and accept.