Choose the Destination Network First
Start with the application, wallet or service you plan to use after the bridge. The cheapest-looking network is not useful if the destination app does not support it or if the required token is unavailable there.
Bridging ETH is different from swapping it. A bridge moves ETH or another supported asset between networks, while a swap changes one asset into another; choosing the correct destination network is therefore the first decision before any bridge transaction is signed.
Ethereum Mainnet and Layer 2 networks keep separate balances. Moving ETH to Base, Arbitrum, Optimism or another L2 requires a supported cross-network route even when the wallet shows the same account address on both networks.
For a comparison of major networks, see Ethereum Layer 2 networks explained.
Bridge interfaces differ, but the core flow is similar across major L2 networks. Use a verified bridge URL and review the source network, destination network, amount and expected receive result before approving anything in the wallet.
Open the official or otherwise verified bridge for the destination network.
Connect your wallet and make sure the source is Ethereum Mainnet.
Select the Layer 2 destination.
Enter the ETH amount to bridge.
Review the expected receive amount, network costs and any bridge-specific fee.
Confirm the transaction in your wallet and pay the Ethereum gas required for the source transaction.
Wait for the bridge process to complete, switch the wallet to the destination L2 and verify the ETH balance there.
Bridge completion time is not universal. It depends on the bridge, network design, current conditions and direction of travel, so use the live status shown by the bridge rather than a fixed time quoted in an article.
If you need help with the source transaction itself, see how to send ETH safely and how Ethereum gas fees work.
Moving assets from an L2 back to Ethereum is the reverse direction, but the operational path can differ from the deposit path. Withdrawal timing and finalization depend on the network's rollup architecture and the bridge route being used.
Do not assume that a Mainnet-to-L2 deposit time also applies to L2-to-Mainnet withdrawals. Open the network's current bridge, select Ethereum Mainnet as the destination, review the live withdrawal information and keep the transaction references until the funds arrive.
Third-party liquidity bridges can offer different routing and timing from canonical withdrawal mechanisms. They also introduce their own smart-contract, liquidity and counterparty assumptions, so compare the route rather than treating every bridge as equivalent.
There is no single universal bridge fee. The total cost can include source-network gas, bridge or liquidity-provider charges, destination execution costs and a separate withdrawal cost when you later move funds back.
| Cost component | Where it appears |
|---|---|
| Ethereum gas | Paid when the source transaction executes on Ethereum Mainnet |
| Bridge/protocol fee | May be charged by the selected bridge route |
| Liquidity-provider cost | Can apply when a third-party bridge uses liquidity to accelerate routing |
| Destination network cost | Can apply to actions performed after funds arrive on the L2 |
| Withdrawal cost | Can apply when returning assets to Ethereum or another network |
Review the actual bridge preview immediately before signing. Static fee examples become stale quickly because network demand and route liquidity change.
A bridge transaction combines normal wallet security with cross-network and smart-contract risk. Verify the route before approving contracts or sending funds because an official-looking interface does not by itself guarantee the transaction is safe.
A hardware or software wallet cannot automatically determine whether every bridge contract is safe. The Ethereum wallet guide covers wallet selection, while bridge-contract risk must still be evaluated separately.
Use a bridge when the primary goal is to keep the asset while changing networks. Use a swap when the primary goal is to change the asset; some cross-chain swaps can change both the asset and the destination network in one service flow.
| Goal | Example | Best-fit action |
|---|---|---|
| Keep ETH, move to Arbitrum | ETH on Ethereum → ETH on Arbitrum | Bridge |
| Change ETH into ARB | ETH on Ethereum → ARB on Arbitrum | Swap |
| Change ETH into SOL | ETH on Ethereum → native SOL on Solana | Cross-chain swap |
| Return ETH from L2 to Mainnet | ETH on L2 → ETH on Ethereum | Bridge/withdrawal |
For example, the ETH to ARB page changes the asset into ARB, while bridging ETH to Arbitrum keeps the asset as ETH. The ETH to SOL route changes both the asset and the blockchain rather than acting as an ETH bridge.
It means moving ETH between supported networks, such as Ethereum Mainnet and a Layer 2, without the primary goal of changing ETH into a different asset.
There is no single time for every route. Timing depends on the network, bridge, direction and current conditions, so rely on the live bridge status.
When the source transaction is on Ethereum Mainnet, ETH is required for Ethereum gas. The destination network can also require ETH or another gas asset for later activity.
Yes, supported L2 networks provide withdrawal or bridge paths back to Ethereum, but the timing and mechanism can differ from the deposit direction.
No bridge should be described as risk-free. Prefer verified network documentation and understand whether you are using a canonical route or a third-party liquidity bridge.
No. Bridging primarily changes the network while keeping the asset, whereas swapping changes the asset. A cross-chain swap can change both.