Cow swap

Cow swap fees: Network Costs, Trade Charges and Settled Output

Cow swap fees include network costs and protocol charges that affect the amounts exchanged. An integration can add a partner fee, while approvals or native-token preparation can require separate transactions. Compare the final quoted amounts before signing, then reconcile the executed amounts and received tokens afterward. The network estimate alone doesn’t describe the complete cost of the exchange.

A useful comparison keeps the selected tokens, trade amount and destination consistent. Changing those inputs changes the exchange itself. It also helps to distinguish explicit charges from price impact and the price movement that your signed order permits.

Cost inputs for the same exchange

Total cost combines charges embedded in the exchange with any transactions that you pay for separately. Network costs fund settlement. Protocol charges follow the applicable fee policy. A partner fee applies when the integration adds one. Liquidity conditions also affect the exchange rate, even when they don’t appear as a separate charge.

For a fixed sell amount, compare the expected output after included fees. For a fixed buy amount, compare the required input. Keep separately paid gas alongside that comparison. Don’t subtract an embedded fee again from an amount that already includes it. This distinction prevents an apparently detailed calculation from counting the same expense twice.


Quoted amounts and signed limits

The quote describes proposed trading amounts, while the signed order sets the boundaries that execution must respect. A sell order fixes the input and specifies a minimum output. A buy order fixes the requested output and specifies a maximum input. Fees and slippage adjustments therefore affect different sides of these orders.

Raw quote data can differ from the final amounts presented for signing. Integrations must account for applicable partner fees and slippage when preparing the order. For a cost comparison, use equivalent amounts at the same stage. Comparing one interface’s preliminary output with another’s final minimum mixes an estimate with an execution boundary.


Does gasless trading mean the swap is free?

Gasless trading means the regular signed-order flow avoids a trader-submitted settlement transaction; execution still has a cost. Solvers submit settlements and recover network costs through the exchange. Paying through the traded tokens changes how the expense reaches you, rather than removing it.

The quote response’s feeAmount field represents network costs in sell-token units. Protocol charges also affect the quoted trading amounts, so that field isn’t a total-fee figure. Network demand, execution complexity and the conversion into the sell token influence the network estimate. A refreshed quote can therefore show a different amount.

Protocol charges and their calculation bases

Protocol fees use different calculation bases, so a percentage without its basis doesn’t explain the charge. Volume-based charges relate to order volume. Improvement-based charges relate to value gained against a specified price benchmark. Applicable factors, caps and classifications can change; the order’s fee policy determines the relevant calculation.

Trade volume

A volume fee scales with the value traded under the applicable asset classification. Its calculation doesn’t require positive price improvement. The quoted protocol-fee parameter helps explain this component, while the final trading amounts show its effect on the exchange.

Improvement against the quote

A quote-improvement fee applies to positive execution improvement over the quoted price. This policy covers market orders and applicable in-market limit or scheduled orders. The improvement is the calculation base, subject to the policy’s cap; it isn’t a percentage charged against every token received.

Surplus above a limit

For eligible out-of-market limit orders, surplus measures execution improvement relative to the order’s limit price. Applicable discrete scheduled orders can fall into this category too. The benchmark differs from quote improvement, which explains why identical-looking percentages needn’t describe identical charges.


Is slippage a fee?

Slippage tolerance is an execution allowance, not a fee that the protocol automatically collects in full. It sets how far execution may move against the reviewed price within the signed conditions. The expected output and minimum received amount consequently serve different purposes.

A wider tolerance permits a worse execution outcome without guaranteeing a fill. A tighter tolerance can leave an order unfilled when available execution no longer satisfies its terms. Neither setting establishes the protocol’s fee rate. Similarly, a difference between quoted and received tokens doesn’t by itself identify a fee: price movement and execution improvement also affect the result.

Approval and native-token preparation costs

Preparation can create a separate network expense before any swap settles. The relevant cost depends on existing permissions, token support and the way the order enters the protocol.

Spending approval

A sufficient existing allowance can avoid another approval transaction. A regular on-chain approval consumes gas and grants spending permission; it doesn’t confirm a completed exchange. Supported gasless approvals offer another path, subject to token and wallet compatibility. The documented gasless approval flow excludes smart contract wallets.

Wrapping or Eth-flow

Native-token selling supports separate wrapping or the Eth-flow contract’s combined wrapping and order placement. Wrapping requires an on-chain transaction. Eth-flow also requires upfront gas, which isn’t refunded if the order fails. Its interface support applies to swaps and excludes smart contract wallets. Repeated trades and a single trade therefore have different preparation-cost considerations, without establishing a universal cheaper choice.


Liquidity costs and repeated execution

Liquidity affects how much output a given input can purchase, independently of the displayed network charge. Price impact describes the effect of the trade itself on available pricing. A route with a lower network estimate can still deliver less after its liquidity costs.

Splitting execution changes that balance. A time-weighted average price order, or TWAP, spreads trading across scheduled parts. Smaller parts can reduce price impact, while each execution carries its own cost and encounters its own market conditions. The comparison concerns aggregate input and output across executed parts, together with preparation expenses. A lower cost on one part doesn’t establish a lower cost for the complete order.

Liquidity costs and repeated execution: Splitting execution changes that balance. A time-weighted average price order, or TWAP, spreads trading across scheduled parts. Smaller parts can reduce price impact, while each execution carries its own cost and encounters its own market conditions.; The comparison concerns aggregate input and output across executed parts, together with preparation expenses. A lower cost on one part doesn’t establish a lower cost for the complete order.

View image file

Partner charges and destination delivery

An integration can add a partner fee through the order’s metadata. Using the same underlying protocol therefore doesn’t establish identical charges across interfaces. Compare the final trading amounts and the disclosed partner charge together, without adding that charge again if the amounts already include it.

Cross-chain exchanges add a destination requirement. Their quote breakdown distinguishes swap output from bridge costs and the minimum destination receipt. Source settlement alone doesn’t establish delivery. If the bridge transfer requires a refund, the provider’s rules determine that process; a source-chain swap that already executed remains part of the cost history. Compare the actual destination amount or refund state with the corresponding records.

Cost records through a regular token order

A regular token sell order connects the reviewed cost estimate to the eventual receipt through the following stages. This sequence assumes a same-chain exchange and sufficient funds. Approval is conditional because an existing allowance may already cover the order.

At a glance: Cost records through a regular token order
Stage Cost information Observable record Token control
Quote review Expected output and included charges Quote amounts and validity Requesting a quote doesn’t move tokens
Allowance preparation Separate gas if an approval transaction is required Allowance and any approval receipt Approval grants spending permission
Order signing and submission Final minimum output after adjustments Signed amounts and order identifier The signature authorizes execution within its terms
Solver competition Execution must accommodate costs within the order’s limits Order status and competition data A pending regular order hasn’t itself transferred tokens
Settlement Actual exchanged amounts and execution fees Trade record and settlement transaction Contracts transfer tokens under the authorized conditions
Reconciliation Embedded charges alongside separate transaction expenses Execution details and recipient transfers The receipt identifies the tokens delivered to the recipient
Comparison basis Use the executed exchange amounts, then account separately for transactions paid outside that exchange.

An approval can confirm after the quote expires. At that point, obtain a fresh quote before signing and compare its final output with the earlier estimate. The confirmed approval expense remains incurred. If the new terms aren’t acceptable, stopping before signing avoids authorizing that trade; it doesn’t reverse the approval transaction.

For an accepted replacement quote that proceeds to settlement, the execution record and recipient transfer establish the outcome. Retain the approval receipt alongside them so the preparation expense doesn’t disappear from the comparison.


Do unfilled orders incur execution fees?

A regular signed order that never fills doesn’t incur a successful-swap execution charge. An unsuccessful solver settlement attempt doesn’t turn into a trader-submitted gas transaction. Separately submitted transactions remain a different expense category.

Approval, wrapping and on-chain cancellation can consume gas even when no exchange completes. Eth-flow’s upfront gas expense isn’t refunded when its order fails. Returning deposited trading funds doesn’t return that consumed gas. An off-chain cancellation has no transaction gas charge, but settlement can overtake cancellation. Any completed fill remains an executed trade with its associated costs.

Settled amounts and the next comparison

The executed input and delivered output establish the exchange rate that you actually received.

Order details expose executed sell and buy amounts, together with execution-fee information. The fee breakdown must retain each amount’s token denomination. Settlement accounting also distinguishes network charges from protocol charges through the execution data and applicable fee policies. The transaction’s overall gas expense isn’t automatically the fee attributable to an individual order within its batch.

Don’t label every difference from an earlier quote as a charge. Changes in execution price can improve or worsen the comparison within the authorized limits. Likewise, unrelated wallet transfers can distort a simple before-and-after balance subtraction. Match the order’s transfers to the intended recipient before drawing a conclusion.

For the next exchange, decide whether preparation, order type or destination changes the cost basis. Compare equivalent final amounts and include only additional expenses that aren’t already embedded. That comparison supports a choice between available quotes without treating the smallest network estimate as the cheapest complete trade.

Questions people ask about Cow swap fees

Why can an order show a zero feeAmount even when I paid trading fees?

A zero feeAmount in the submitted order doesn’t establish that the trade was free. That order field differs from the network-cost field in a quote response. Execution embeds fees in the trading amounts, so use the filled order’s execution details to understand the charges.

Does matching directly with another order remove every trading charge?

A direct match can avoid liquidity-pool fees for the matched portion, but it doesn’t remove every applicable charge. Settlement still requires execution, and the order remains subject to its protocol fee policy. A partial direct match can also leave a remainder that uses external liquidity.

How should I compare fees quoted in different tokens?

Compare differently denominated fees only after expressing them in a common unit using a consistent valuation basis. Raw token quantities aren’t directly comparable. Keep the original quantities and valuation time available, since a later price change can alter the converted total without changing the tokens originally charged.

Can a lower network fee make a small order executable?

A lower network cost can improve an order’s execution economics, but liquidity and the signed price limit still constrain settlement. Solvers need an executable route that accommodates costs within those terms. A cheaper network estimate alone doesn’t prove that such a route exists.

· updated