How to Bridge From BNB Chain

I bridge assets off BNB Chain a couple times a month, and the process still trips people up. Not because it's hard. Because one wrong dropdown and your USDT lands on a chain you didn't mean to use, or worse, your wallet screams about a network you've never heard of.

So here's the whole thing, start to finish. No fluff.

What bridging actually does

A bridge doesn't teleport your coins. It locks (or burns) your asset on BNB Chain and mints an equivalent on the other side. If you want the mechanics, I wrote a longer piece on how bridges work. Short version: your BNB stays on BNB Chain, and you get a representation of it elsewhere.

This matters for one reason. The token you receive on Ethereum is not the same contract as the one you sent. Treat it as a new asset.

Official bridge or third‑party aggregator?

You've got two flavors.

Official bridges are run by the destination protocol or by Binance itself. They're narrow. They usually support a handful of routes and assets, and they tend to be the safest choice for stablecoins and blue‑chip tokens. The trade‑off is fewer options and sometimes slower speed.

Third‑party aggregators (Jumper, Bungee, Stargate, LI.FI‑powered tools) scan dozens of routes and pick the cheapest or fastest. They're wildly convenient. You pay a small routing fee, and you're trusting an extra layer of smart contracts. For everyday moves I use an aggregator. For a five‑figure transfer I lean official.

One thing people forget: aggregators still settle on the underlying bridges, so the safety of the route depends on which protocol they route through, not just the front end.

The step‑by‑step

Here's the flow I follow every single time. Don't skip the fee check.

1. Choose a bridge or aggregator that supports BNB Chain. Jumper, Bungee, and Stargate all do. If you want the official route, the Binance Bridge or the destination chain's own bridge works too.
2. Connect your wallet. MetaMask, Rabby, or a WalletConnect mobile wallet. Approve the connection and make sure the address shown is the one holding your funds.
3. Set BNB Chain as the source network. This is the number‑one mistake. If your wallet defaults to Ethereum, switch it now, or the bridge will quote you the wrong gas and the wrong balance.
4. Pick the destination chain, the asset, and the amount. Choose where you're going (Ethereum, Polygon, Arbitrum, wherever), select the token you're sending, and type the amount. Leave a little behind for gas.
5. Check the fees, and remember gas is paid in BNB. The interface will show a source‑side network fee, a destination fee, and any protocol cut. The BNB Chain gas is tiny, but the destination gas (especially Ethereum) is where the real cost sits.
6. Confirm and sign. You may need two signatures: one to approve the token spend, one to execute the bridge. Read what you're approving. Reject any request for unlimited allowance you didn't expect.
7. Wait for finality. Watch the bridge's progress tracker. Most transfers clear in a few minutes; some take 15 to 30 depending on the route and confirmations required.
8. Verify the funds arrived. Switch your wallet to the destination network and confirm the balance. If the token doesn't show, add its contract address manually, then check the destination explorer to confirm it settled.

That's it. Eight steps, and step three plus step five are where nearly everyone slips.

Fees, in plain terms

You pay gas on the source side in BNB. Always. Even if you're sending USDT, the transaction fee comes out of your BNB balance, so if you're at zero BNB you're stuck before you start. Keep 0.002 to 0.005 BNB around as a buffer.

The BNB Chain side is cheap, often pennies. The expensive part is wherever you're landing. Bridging into Ethereum during a busy afternoon can cost several dollars in ETH gas. Polygon or Arbitrum? Fractions of a cent. If cost is your worry, I compared routes and speeds in my guide on bridging from Polygon, and a lot of the same logic applies here.

Aggregators add a routing fee, usually well under a percent. Worth it for the convenience most days.

The pitfalls that actually cost people money

Let me be blunt about the traps.

Wrong network. If your wallet is on Ethereum when you meant BNB Chain, the whole quote is garbage. The balances won't match. Switch first, always.

BEP20 versus ERC20. This is the big one. A BEP20 token on BNB Chain is a different contract than the ERC20 version on Ethereum. They are not interchangeable by copy‑pasting an address. If you send a BEP20 token to a plain Ethereum wallet address expecting it to arrive as ERC20, it won't. It stays a BEP20 asset, and if the destination doesn't recognize it, you've got a mess. A real bridge handles the conversion. A raw transfer does not.

Sending to an exchange without checking the network. Exchanges sometimes accept only ERC20 deposits for a given token. Send the BEP20 version to that address and support tickets are in your future. Confirm the deposit network on the exchange first.

Running out of BNB mid‑flow. No gas, no transaction. Keep a buffer.

Phishing front ends. Fake bridge sites are everywhere. Bookmark the real URL. Don't click bridge links from Telegram or a random tweet.

When it looks stuck

Nine times out of ten a 'stuck' bridge is just slow finality. The source transaction confirmed, the destination is waiting on block confirmations, and you're staring at a spinner. Give it 30 minutes.

If the source transaction failed outright, your funds never left, so check your BNB Chain balance and try again with the network set correctly. If the source succeeded but nothing arrived after half an hour, grab your transaction hash and paste it into the bridge's tracker or their support channel. Keep that hash. It's your proof.

Bridging isn't scary once you've done it a few times. Set the source network, check the gas in BNB, mind the BEP20 versus ERC20 gap, and verify on the other side. Do those four things and you'll almost never have a bad transfer.