Swap ETH to BNB

Swap ETH to BNB converts two native gas tokens — ETH on Ethereum Mainnet and BNB on BNB Smart Chain — rather than exchanging an ERC-20 or BEP-20 token for its native counterpart. ETH pays for computation on Ethereum; BNB Smart Chain's network docs describe BNB as the gas asset for smart-contract execution on its own network. There is no peg between them. The route sells your ETH-side value and sources BNB from destination-side liquidity at the market rate, minus fees and price impact, so the quote's minimum received matters more than its headline rate.

People make this move when they need BNB for gas on BNB Smart Chain, want to use an application that only exists there, or are rebalancing between the two ecosystems without touching a centralized exchange.

To get in and out, connect an EVM wallet, set ETH on Ethereum Mainnet as the input and native BNB on BNB Smart Chain as the output, then request a route quote. The quote reflects available liquidity, the bridge path, price impact, fees, and a minimum output. After you accept it, you sign one source-chain transaction; the route then swaps and transfers value through bridge contracts or liquidity providers, releasing or purchasing BNB for your recipient address on the other side. A cross-chain bridge is the part that connects the two networks.

A plain bridge may deliver wrapped ETH on BNB Smart Chain, not BNB. A complete cross-chain swap delivers the destination asset you asked for, while wrapped and native tokens are not interchangeable in every application, so the output asset in the quote determines what you receive.

A DEX leg prices the conversion from pool liquidity: the pool takes a fee, an order large relative to pool depth moves the price through price impact, and gas is paid on top; these are standard automated market-maker mechanics. Because ETH is native, it is typically wrapped to WETH inside the swap leg automatically, so you do not need to perform that step yourself.

If the route needs a token approval in addition to the swap transaction, the approval is a separate signature granting the contract spend access. That makes the approval and the swap two distinct on-chain actions.

ETH and BNB are separate native assets of two EVM-compatible networks, with independent balances, transaction histories, and prices; owning ETH gives you no BNB-side gas, and vice versa. They are not versions of the same asset and are not tied by a peg.

WETH and WBNB are wrapped forms that let native assets behave like tokens inside smart contracts expecting a token interface. The ERC-20 token standard defines that kind of contract interface, but wrapped assets remain representations rather than native gas assets: some applications accept them, many gas-related uses do not. To hold and spend on BNB Smart Chain, use native BNB; a DeFi contract asking for WBNB is requesting a different input.

Costs are the ETH required for Ethereum gas, plus the route's protocol or relayer fee, any DEX pool fee, and price impact; compare quotes by minimum received because that figure nets out the fees and impact. Every valid source transaction needs ETH for Ethereum gas, and on a congested day that is often the largest single cost of the whole move.

Destination gas can be supplied as part of the swap, deducted from the output, or required separately. If it is required separately and your BNB Smart Chain address is empty, your BNB arrives but you still cannot move it; the quote's destination-gas treatment tells you which case applies.

Swap ETH to BNB is non-custodial only in the custody sense: funds remain in your wallet between signatures, but the route still depends on its router contracts and bridge verification model. Those models can use validators, oracles, multisignatures, liquidity providers, solvers, or underlying-chain verification; an audit or open-source code does not eliminate their different failure modes.

Before signing, verify the route's contract addresses against the protocol's official documentation, not a search result or chat message. Smart-contract bugs, malicious approvals, shallow liquidity, cross-chain relay failures, and phishing sites imitating known routers remain live risks on BNB Smart Chain and Ethereum. An ERC-20 allowance reference explains the spend-access interface behind token approvals; scope any approval to what the route needs.

Problems after a route usually reduce to a wrong asset or network, delayed cross-chain completion, missing destination gas, or a pending approval; each has a distinct check. If you received a wrapped token instead of native BNB, the route bridged rather than swapped, so you need a destination-side swap to unwrap it into BNB. Check the received token and chain in the BscScan block explorer before diagnosing the balance.

Stuck or slow completion stretches with confirmations, finality rules, liquidity, relayers, or congestion. Verify the source transaction in the Etherscan explorer first; if it confirmed, the delay is on the bridge or destination leg, where the route's status tracker is the right place to look. If BNB arrived but you cannot transact, you need a small amount of BNB for gas; some routes let you add this at quote time. If an approval is pending, remember that approval and swap are two transactions, so signing only the first does nothing yet.