SyncSwap trading fees appear in the quoted output after deduction and in the selected pool’s fee details; the wallet’s gas estimate is a separate charge.
A SyncSwap trading fee is the charge applied by the liquidity pool to the swap itself, not the transaction fee paid to zkSync Era. That distinction explains why you may see fewer output tokens than a simple spot-price calculation suggests, without seeing a second fee line in your wallet.
The fee is reflected first in the amount you are quoted to receive. Enter the token pair and input amount, then read the output amount shown by the swap panel. SyncSwap’s quote has already accounted for the trading fee, so do not subtract it again from the displayed output.
Open Syncswap and choose the tokens you want to exchange. After entering the amount, click the price or quote bar to expand the additional trade details. This is where the interface exposes information such as price impact, minimum received, and the route used for the swap.
The pool’s fee itself is checked in the Pools section. That matters because there is no single fee that applies to every SyncSwap trade. Different pools can use different fee rules, and a route passing through more than one pool may involve more than one pool-level calculation.
The trading fee is taken inside the swap calculation rather than presented as a separate wallet deduction. The router sends the trade through the relevant pool, the pool applies its fee rule, and the output transferred to you is the net amount.
That architecture is visible in the protocol’s contracts. SyncSwap uses a Vault for token custody, a Pool Master as a registry, liquidity pools for pricing, and fee-management contracts for pool fee rules. These Solidity Programming Language contracts run on zkSync Era, the Ethereum layer-2 network built by Matter Labs. You can inspect the transaction later, but the explorer will show the result of the calculation rather than a convenient retail-style “fee paid” receipt.
Fees can also depend on the pool model and its configuration. A pool may inherit a default fee or use a custom one. Some configurations support dynamic or directional fees, so the rate can depend on the pool, the direction of the trade, or the conditions used by that pool. Treat the pool details as authoritative for that quote instead of relying on a remembered percentage.
This check saves the long way of reconstructing the fee from token balances, contract calls, and transfer events after the transaction settles. It also prevents the common mistake of treating every difference between the input value and output value as a fee.