Polygon to BNB Chain

Two networks with no official connection, two different gas tokens, and a token that exists separately on each. Every quote above is a third-party route, priced by each provider on its own.

3 of 3 sources answered · updated 19:42 UTC · some sources did not answer in time

Quotes for $1,000.00 in USDC from Polygon to BNB Chain
Provider You receive Fee Gas on source network Time Execute
Mayan Lowest total cost999.70 USDC
≈ $999.59
0.04%
$0.41
no data3 s
Across
Powered by Across
999.01 USDC
≈ $998.89
0.11%
$1.11
no data1 s
Symbiosis998.61 USDC
≈ $998.49
0.15%
$1.51
no data32 s

Fee is everything lost between what you send and what you receive. For providers this site executes transfers through — their rows carry a Bridge button wherever transfers are available — our integrator fee is already inside that number; every other provider is quoted at its own price. Gas on the source network is listed separately. Quotes refresh every 60 seconds while this page is open.

Via an exchange

Withdrawal fee to BNB Chain on major exchanges. Depositing to the exchange, trading fees and account requirements are not included.

Exchange Withdrawal fee Minimum Source
Binance0 USDC3 USDCchecked 2026-09-15 over two weeks old — may have changed
Bybit0.2 USDC0.2 USDCchecked 2026-09-15 over two weeks old — may have changed
Gate0.499 USDC0.01 USDCchecked 2026-09-15 over two weeks old — may have changed
WhiteBIT1 USDC10 USDCchecked 2026-09-15 over two weeks old — may have changed

Fee history

Median fee by provider, 2026-09-17 – 2026-10-160.00%0.25%0.50%2026-09-172026-10-16AcrossLI.FIMayanRelaySymbiosis

1 days without data

Risk: Crypto assets are volatile, and transfers between networks can fail or lose funds. Quotes can change before you confirm. Nothing here is financial advice.

Disclosure: We earn a fee when you bridge through this site and may earn from exchange referral links. Routes are ordered by total cost, not by what we earn. Full disclaimer

No official path between them

Polygon’s own bridge connects it to Ethereum, and BNB Smart Chain’s ecosystem bridges do the same for BNB Smart Chain. Nothing official runs directly between the two. The formal route is Polygon to Ethereum — with its checkpoint and claim — then Ethereum to BNB Smart Chain, paying Ethereum gas in the middle. The providers above collapse that into one transfer.

Two gas tokens, neither of them the one you are moving

Polygon takes fees in POL, the token that replaced MATIC (Polygon documentation); BNB Smart Chain takes them in BNB (BNB Chain documentation). You need a little of the first to send and a little of the second to use what arrives. A stablecoin transfer that lands on an empty wallet stays there.

The same address on both sides

Both are EVM networks, so one address string exists on each of them and on every other EVM chain (MetaMask Help Center). The address is not the network. On an exchange withdrawal screen it is the network dropdown, not the pasted address, that determines the outcome.

Or through an exchange

Both networks are well supported for stablecoin withdrawals, so the exchange row is worth reading here. It carries the published fee and the date we checked it, and appears whether or not it beats the bridges.

Questions

How do I bridge from Polygon to BSC?

Neither network has an official bridge to the other — both connect to Ethereum instead — so a direct transfer always goes through a third-party provider. The alternative is two transfers through Ethereum, paying Ethereum gas in the middle.

Do I need POL and BNB?

POL to send, since Polygon charges fees in it, and BNB to do anything with the funds after they arrive on BNB Smart Chain. Neither is covered by the amount you are transferring.

Is the address the same on both?

Both are EVM networks and share one address format, so the same string is valid on each. The network chosen when sending is what decides where the funds actually land.

Why do the quotes differ between providers?

With no official bridge setting a baseline, each provider sets its own price for the route. That is the case for comparing rather than defaulting to one.

Sources

Tokens on this route