Estimate Bridge Fee Tiers From Net Proceeds

Estimate a bridge fee tier by comparing the amount you send with the amount the destination chain is expected to deliver. The useful figure is net proceeds, not a fee percentage in isolation: a small fixed cost can dominate a small transfer, while a percentage based on liquidity or capital costs can matter more on a larger one. Treat “tiers” as your own comparison bands, since routes and bridge protocols do not share one standard fee schedule.

Start with the same token, route, and amount for every quote. Record the input amount, quoted output, and any costs paid separately on the origin chain. For a practical walkthrough of the transfer flow, see how to move crypto with AcrossBridge. The quote comparison here is about what remains after the route’s costs, not which interface you use.

How do you calculate net proceeds after bridge fees?

Net proceeds are the destination-chain amount you expect to receive after deductions shown in the quote. For a same-token transfer, subtract the quoted output from the input to estimate the bridge’s total fee: total fee = input amount − output amount. Divide that difference by the input amount to express the fee as a percentage. Keep the absolute amount too; percentages alone can obscure the cost of a small transfer.

For example, if a quote takes 100 units of a token and returns 99.4 units, the quoted bridge fee is 0.6 units, or 0.6% of the input. That calculation does not automatically include gas paid separately to submit the source-chain transaction, nor does it account for price movement if the input and output assets differ. Compare values in one unit of account when the route swaps tokens, and label any exchange-rate assumption.

Do not add fee components twice. A quote may show a combined bridge fee alongside details such as relayer gas, relayer capital, and liquidity-provider fees. Use the quote’s total or calculate input minus output; use the component fields to explain the total, not to stack another deduction on top of it. An integrator or app fee may also be charged separately and should be included if it appears in the destination amount or fee breakdown.

What fee tiers make a bridge quote easier to compare?

Build tiers around the net amount delivered for the transfer sizes you actually consider. A simple comparison can classify quotes as low, middle, or high cost by their fee percentage, but set the cutoffs from your own tolerance and route data. There is no universal percentage boundary that makes a bridge “cheap.” Keep a separate view of absolute cost so the tier remains meaningful at different transfer sizes.

• Net output: the destination amount after the quote’s deductions.
• Effective fee rate: input minus output, divided by input, for same-token routes.
• Separate transaction cost: source-chain gas or other cost not included in the quoted output.
• Route status: minimum and maximum amounts, fill-time estimate, and any warning that the amount is too low.

Compare quotes at the intended amount because some fees scale with size and others behave more like fixed costs. A relayer’s destination gas cost can weigh heavily on a small transfer. Liquidity-provider fees can vary with pool utilization and route, so a larger amount may face a different rate. Across documents its relay fee breakdown into relayer gas, relayer capital, and LP fees; the current Swap API quote response is the recommended source for new integrations. These fields describe costs with different causes, but the destination output is the decision figure.

Why do bridge fees change by route and transfer size?

A route determines which liquidity and relayer costs apply. In Across, LP fees reflect pool utilization and whether the relayer’s repayment path requires cross-chain rebalancing; relayer fees account for destination fill gas and the cost of capital tied up until repayment. Gas prices and available liquidity can change, so a quote can move even when the token pair and transfer size stay the same.

Quote freshness matters. Fetch the quote close to submission and use the same route, token addresses, and amount when comparing providers. Check whether the requested amount is below the route minimum or above a stated limit. A quote with a favorable rate is not useful if the amount cannot be filled under the route’s limits. Token decimal mismatches also require care: compare human-readable amounts only after applying each token’s decimals, rather than comparing raw integer units.

For a different-token route, input minus output is not a fee unless both amounts have been converted to a common valuation at the quote’s exchange rate. Separate the swap price from explicit fees where the quote exposes them. Also distinguish expected output from guaranteed output: slippage settings, route execution, and quote expiry can affect the final result.

How should you choose between two bridge quotes?

Choose the route with the better expected net proceeds after including costs you pay outside the bridge quote, provided it meets the amount and timing constraints. If one quote is cheaper but has a longer expected fill time or tighter limits, that is a real trade-off. Recheck the quote just before submitting. The best estimate is the fresh, route-specific output you can actually receive, with every separate transaction cost accounted for.