Pancakeswap fees are divided between LPs and protocol operations

Open the route preview before signing the swap

The PancakeSwap route preview shows every pool, hop, fee tier, and expected output before execution. That route determines the platform charge for the proposed trade. Start on the intended chain, select the input and output tokens, and enter the exact amount. Keep enough of the chain's native asset outside the trade for gas.

Expand the Route and Fee details before opening MetaMask or Trust Wallet. Record the input amount, estimated output, fee amount, price impact, and minimum received. A CAKE-to-USDC quote might use one V3 pool, several pools, PancakeSwap Infinity, StableSwap, or a market-maker quote. Each source follows its own fee logic.

An ERC-20 or BEP-20 token sometimes needs an approval transaction before its first swap. Approval consumes network gas but carries no liquidity-pool trading fee. The swap is the next transaction. After settlement, match the wallet receipt against the quoted route and the tokens that actually entered the wallet.

V3 fee tiers set the charge for each pool hop

Pancakeswap fees in EVM V3 pools use four defined tiers: 0.01%, 0.05%, 0.25%, and 1%. The selected pool's tier applies to the amount passing through that hop. A 0.01% pool collects one basis point, while 0.05% collects five basis points. The 0.25% and 1% tiers collect 25 and 100 basis points, respectively.

Pool creators select a tier when establishing V3 liquidity. Stable pairs such as USDC and USDT gravitate toward lower tiers when deep liquidity supports tight execution. Volatile pairs such as CAKE and BNB support higher tiers where LPs require greater compensation. The Smart Router chooses among available pools by expected output, not by fee tier alone. A lower percentage loses its advantage when the corresponding pool has materially less active liquidity.

The fee split determines who receives each collected unit

The V3 EVM fee split sends defined portions to active liquidity providers, CAKE buyback and burn, and the PancakeSwap treasury. The allocation ratio changes across the four standard tiers. For a 0.25% PancakeSwap V3 EVM pool, 68% of the fee goes to active LPs, 23% funds CAKE buyback and burn, and 9% goes to the treasury.

That 0.25% tier therefore assigns an effective 0.17% of trade value to LPs, 0.0575% to buyback and burn, and 0.0225% to treasury. At the 0.01% tier, the split is 67%, 15%, and 18%. Those shares equal 0.0067%, 0.0015%, and 0.0018% of trade value. The 0.05% tier uses 66%, 15%, and 19%, producing effective slices of 0.033%, 0.0075%, and 0.0095%.

The 1% tier returns to a 68%, 23%, and 9% split. Its effective slices are 0.68%, 0.23%, and 0.09%. Only V3 positions whose configured price ranges contain the active market price earn the LP portion. The eligible positions divide it in proportion to their active liquidity; an out-of-range position receives none from that swap.

Pool depth raises execution cost without changing the tier

Pool depth changes price impact, while the posted fee tier remains fixed. A large order consumes liquidity across the pool's pricing curve and receives a progressively different exchange rate. This economic cost appears in the output quote rather than as a payment to the treasury or LPs.

A 0.05% route can deliver less output than a 0.25% route when the cheaper pool is thinner. Slippage tolerance serves another role: it sets the largest quote movement accepted before the transaction reverts. It is not an additional charge. Minimum received translates that tolerance into an output floor. Compare the final token amount, not a fee percentage detached from liquidity. Token contracts that deduct a transfer charge add another distinct cost, which the pool tier does not absorb, as explained in Working with pancakeswap.

Infinity makes fee design a permanent pool setting

Even so, PancakeSwap Infinity pools choose a static or dynamic fee model at creation, and that choice stays fixed for the pool. Static fees remain constant. Dynamic fees require a hook that updates the charge through pool logic before a swap. This architecture means the route preview, rather than a universal Infinity tier list, supplies the trader-facing rate.

For static Infinity pools, the protocol fee equals 33% of the LP fee and is capped at 0.4%. The published schedule pairs a 1% LP fee with a 0.33% protocol fee. A 2% LP fee reaches the cap, so its protocol component is 0.4%. Dynamic-fee pools carry a 0% protocol fee under this schedule, although their hook controls the LP fee.

Hard limits also depend on the pool manager. Concentrated Liquidity AMM pools permit a static fee up to 100%, while Liquidity Book AMM pools cap it at 10%. Those ceilings accommodate specialized designs; they are not typical trading targets. PancakeSwap's official Dynamic Fee Hook applies its own 5% maximum. Read the pool type and hook alongside the displayed fee before execution.

Network gas sits outside the pool's percentage

Network gas pays the blockchain that executes a PancakeSwap transaction, not the pool or PancakeSwap treasury. BNB Smart Chain charges BNB, Ethereum charges ETH, and Solana charges SOL. The wallet estimate changes with computational work and network pricing. One gwei equals 0.000000001 of an EVM chain's native asset.

On an EVM network, gas cost equals gas used multiplied by the effective gas price. A token approval and a later swap are two transactions, so each receives its own receipt and charge. A reverted transaction still consumes gas because validators performed the computation, while the atomic swap state and pool fee roll back.

During normal operation, PancakeSwap Infinity reduces redundant movement through a singleton PoolManager and flash accounting. EIP-1153 transient storage holds temporary balances for one transaction, while ERC-6909 supports internal multi-token claims. These mechanisms change gas usage, not the pool's percentage. The wallet's fresh estimate remains the usable number at signing.

Multi-hop and split routes change how fees accumulate

A multi-hop PancakeSwap route charges the applicable tier at every pool it crosses. In a two-hop swap, the second fee applies to the output produced by the first hop, not the original input amount. Adding the two displayed percentages against the starting balance therefore gives only an approximation.

Split routing works differently. The Smart Router sends portions of one order through parallel paths, and each pool charges only the portion it processes. It compares V3, V2, StableSwap, PancakeSwap Infinity, and supported market makers. More pools can raise aggregate trading fees and gas while still improving final output through deeper combined liquidity.

Designated market-maker execution has a separate allocation. The trader pays no PancakeSwap trading fee on that fill. PancakeSwap instead receives 0.05% from the market maker on documented non-stablecoin fills and 0.01% on stablecoin-to-stablecoin fills. Those amounts come from the market maker, so they should not be added again to the trader's quote.

A worked quote combines the visible costs into one result

The following worked quote labels every changing input as hypothetical. Assume a hypothetical input of 1,200 USDC, a hypothetical single-hop EVM V3 route, a hypothetical 0.60% curve impact after fees, and hypothetical gas worth 0.04 USDC at one chosen conversion snapshot. The pool's fixed tier is 0.25%, and its fixed allocation is 68% to LPs, 23% to CAKE buyback and burn, and 9% to treasury.

The pool fee is 1,200 × 0.25%, which equals 3 USDC. Of that fee, LPs receive 2.04 USDC, buyback and burn receives 0.69 USDC, and treasury receives 0.27 USDC. After the fee, 1,197 USDC-equivalent remains for the pricing curve. The hypothetical 0.60% curve impact on that amount equals 7.182 USDC-equivalent.

Adding the 3 USDC pool fee, 7.182 USDC-equivalent impact, and 0.04 USDC-equivalent gas gives a hypothetical total cost of 10.222 USDC-equivalent. Rounded to cents, the trade delivers 1,189.78 USDC-equivalent of output and costs 10.22 USDC-equivalent. A live quote replaces all four changing inputs: trade size, route, curve impact, and native-token gas conversion.

V2 preserves a fixed rate and pool-level accrual

Importantly, PancakeSwap V2 applies a fixed 0.25% fee to every swap hop. Its allocation sends 0.17% of trade value back to the liquidity pool, 0.0575% toward CAKE buyback and burn, and 0.0225% to the treasury. The three parts sum to the trader's 0.25% charge.

The LP portion increases pool reserves rather than appearing as a separate wallet payment after each trade. An LP's redeemable share reflects that accumulation. V3 accounting differs because an LP position accrues fees for manual collection while it remains active. The fee rate belongs to the pool version, so a token pair existing in both V2 and V3 can produce two distinct quotes.

Solana and Aptos apply chain-specific fee rules

In the same way, PancakeSwap on Solana publishes 18 V3 concentrated-liquidity tiers: 0.01%, 0.02%, 0.03%, 0.04%, 0.05%, 0.1%, 0.15%, 0.16%, 0.18%, 0.2%, 0.25%, 0.4%, 0.6%, 0.8%, 1%, 2%, 3%, and 4%. Every listed Solana tier allocates 84% of its swap fee to in-range LPs, 8% to burn, and 8% to treasury.

Solana token handling uses SPL accounts and selected Token-2022 assets. A wallet interacting with a token for the first time might need an Associated Token Account. Its SOL funding is a Solana account cost, not a PancakeSwap swap fee, and closing that account can return the reserved SOL.

Within those limits, PancakeSwap V2 on Aptos uses the fixed 0.25% trading rate. Its documented allocation matches V2 elsewhere: 0.17% to liquidity providers, 0.0575% toward CAKE buyback and burn, and 0.0225% to treasury. Chain selection therefore changes both the available pool architecture and the native asset needed for execution costs.

Compare quotes by output after every route component

A complete PancakeSwap quote comparison holds the chain, input token, output token, and input amount constant. It then compares estimated output, minimum received, pool fees, route structure, price impact, and network gas at nearly the same moment. Comparing Pancakeswap fees across different blocks or different trade sizes mixes unrelated conditions.

Normalize gas into the output asset using one clearly timestamped conversion snapshot. Keep the native-asset amount beside it, since that is what the wallet pays. Refresh both quotes immediately before choosing. A lower tier deserves selection only when its final received amount remains higher after gas and route effects.

After execution, preserve the transaction hash, block, input amount, output amount, gas used, effective gas price, and any approval receipt. The on-chain receipt verifies gas, while pool events verify the swap amounts. This small operating record separates estimates from settled values and makes repeated fee comparisons consistent.