2026-10-17 06:15 UTC4706bc
Why Swap Fees Drift Between Quote and Execution
Swap fee drift is the gap between a swap’s estimated and final costs, caused by changing pool prices, route fees, network gas and execution conditions.
Crypto Record Editorial4 min read

Swap fee drift is the difference between the cost a swap interface estimates and the fees or value lost when the transaction executes. To understand it, separate the quoted output from the charges: a wallet or exchange estimates a route, the transaction waits to be processed, and the exchange applies its pricing and fee rules when it runs.
What makes up a swap’s estimated cost?
A swap can involve several costs, and an interface may group them together. The liquidity pool charges a trading fee, usually calculated as a share of the amount traded. That fee goes to the pool’s liquidity providers or is distributed under the protocol’s rules. The pool’s reserves also determine the exchange rate: a large trade can move that rate, reducing the output even before network costs are counted.
On a blockchain, the transaction also uses gas. The network fee compensates validators for processing it, and its final amount can depend on the transaction’s complexity and network conditions. A swap through a router may touch more than one pool, adding another trading fee at each step. A cross-chain route can add a bridge charge and a destination-chain transaction cost. These amounts may be shown as one total, even though they go to different parties.
For a fuller look at the moving parts in a Biswap cross-chain swap and transfer, the route matters as much as the fee label: the source-chain swap, bridge and destination step can each affect the result.
Why can the final cost differ from the quote?
The quote is a calculation made from the information available at that moment. Before the transaction executes, someone else may trade against the same pool. Its reserves change, so the same input amount now produces a different output. This is price impact from the user’s own trade plus price movement caused by other trades. The pool’s fee rate may stay fixed while the fee’s value in the tokens being exchanged changes.
There can also be a delay between signing and execution. Network congestion can change the gas price needed for timely processing. A router may select a different path if the original path no longer meets its conditions. On a cross-chain swap, the destination step occurs later than the source transaction, so its exchange rate and gas conditions can differ from the initial estimate.
One analogy helps: a quote is like a fare estimate before a trip, while execution is the meter running on the route actually taken. The analogy stops there. In a swap, pool reserves, token amounts and network fees each have their own rules, and a displayed “fee” may include or exclude some of them.
How can you tell which part drifted?
Compare the quote with the transaction details after execution. Look for the input and output amounts, the minimum output setting, the network fee, and any separately listed pool or bridge charge. If the interface reports only one total, inspect the transaction record or route details to see which costs it combines.
- Output changed: The pool price moved, the trade had price impact, or the route changed.
- Network fee changed: Gas conditions or transaction complexity differed from the estimate.
- Several fees appear: The route used multiple pools or included a bridge and destination transaction.
- Transaction failed: The swap may still consume network gas even if the token exchange did not complete.
Before approving a large swap, check the minimum output and the interface’s slippage setting. Slippage is the allowed difference between the expected and executed output; it is not itself a fee, but it sets how far the result can move before the transaction reverts. A tighter limit can protect the output, while making a transaction more likely to fail if the pool shifts before execution.
Is swap fee drift avoidable?
Some variation is inherent because a quote describes a changing market and a transaction executes later. You can reduce uncertainty by checking the route, comparing the total cost rather than a single fee label, and avoiding unnecessary steps. For most users, the better choice is a clear route with a predictable final output, even if its headline fee looks slightly higher. The useful question is not only “What is the fee?” but “What will I receive, after every step?”