Introduction
This guide explains how to add Layer 2 networks to MetaMask and how to transfer funds between networks using MetaMask as your hot wallet. I write from hands-on use: I add L2s to MetaMask regularly and move small test amounts before committing larger sums. Short version: adding networks is straightforward, moving assets requires a bridge (or an exchange) and a careful checklist.
Want practical steps for "add L2 to MetaMask" and for "how to transfer between networks on MetaMask"? Read on.
What is a Layer 2 and why use one with your software wallet?
A Layer 2 (L2) is a scaling solution that processes transactions off the Ethereum mainnet (or other main chains) to save time and gas fees while still benefiting from mainnet security (depending on the L2 design). Think of it like taking the commuter lane for faster travel. Short transactions cost less and confirm faster on most L2s. For routine DeFi interactions and frequent swaps, using L2 can make sense.
In my experience, the practical benefits are lower gas fees for swaps and faster confirmations. But there are trade-offs (withdrawal mechanics, different native gas tokens), which I cover below.
How to add L2 to MetaMask (step-by-step)
This section shows the two common ways to add L2 networks to MetaMask: an automatic prompt (via a dApp) and manual configuration.
- Open MetaMask (extension or mobile app). Short step.
- Click the network dropdown at the top (it typically says "Ethereum Mainnet" or current network).
- Option A — Automatic: Visit a reputable dApp for the L2 (bridge or exchange) and accept the "Add Network" prompt. MetaMask will prefill the fields.
- Option B — Manual: Choose "Add network" → "Add a network manually" and enter the required fields:
- Network Name
- RPC URL (get from the official L2 docs)
- Chain ID
- Currency Symbol (ETH, MATIC, etc.)
- Block Explorer URL (optional)
- Save and switch to the new network.
A screenshot here would show the network-add form in MetaMask (placeholder). 
Tip: always copy RPC and chain ID from official L2 documentation. Phantom RPCs can steal funds (yes, really). And test with a small amount first.
How to transfer between networks on MetaMask (bridging L1 → L2)
Important: MetaMask doesn't move tokens between networks internally. Networks are separate ledgers. To move value across them you must use a bridge or a centralized exchange. Here's a practical step-by-step for a typical Arbitrum/Optimism/Polygon transfer using a bridge dApp.
Step-by-step: Arbitrum/Optimism/Polygon transfer (general)
- Switch MetaMask to the source network (usually Ethereum mainnet). Confirm you have enough ETH there to pay gas.
- Open a reputable bridge dApp (see our bridging overview). Connect MetaMask.
- Select the token and destination network (Arbitrum/Optimism/Polygon). Enter an amount.
- Approve the token allowance in MetaMask if prompted (this is a smart contract approval). I recommend approving only the needed amount when possible.
- Confirm the deposit transaction in MetaMask. Pay the L1 gas fee.
- Wait for the bridge to complete. Then switch MetaMask to the destination L2 network.
- If the token doesn't appear, add it via Add custom token using the L2 contract address.
That's the core flow for "arbitrum metamask transfer" and for "optimism metamask transfer". Bridges vary in UX and trust assumptions; read the bridge's FAQ and check tx status before moving larger sums.
Arbitrum, Optimism, Polygon — quick practical differences
| Network |
Gas token on L2 |
Typical bridge path |
Practical notes |
| Arbitrum |
ETH (on Arbitrum) |
L1 → Arbitrum bridge |
EVM-compatible, lower gas than L1; withdrawals often use optimistic mechanisms (different finality guarantees). |
| Optimism |
ETH (on Optimism) |
L1 → Optimism bridge |
EVM-compatible; similar trade-offs to Arbitrum; check bridge withdrawal timing before moving large amounts. |
| Polygon (PoS) |
MATIC |
L1 → Polygon PoS bridge |
Different security model (commit/ checkpoint), widely used for cheap swaps and NFTs; gas token is MATIC on Polygon. |
Note: wording above is intentionally general. Bridge mechanics and withdrawal times change as protocols upgrade. Check the bridge docs and our transfer times page if you need specifics.
Moving between L2s and back to L1 (options and trade-offs)
Want to move from Arbitrum to Optimism? You usually use a cross-L2 bridge (some exist), or you move back to L1 then forward to the other L2. That can be slower and costlier. Alternatively, a centralized exchange can accept deposits/withdrawals on both L2s and act as a fast router — but then custody changes.
Trade-off: speed vs security vs cost. Fast bridges may sacrifice some decentralization. I tend to use small test transfers when trying a new route.
Mobile vs desktop: what changes in daily use
MetaMask mobile includes an in-app dApp browser and supports WalletConnect for external dApps. On desktop, you typically use the browser extension and visit bridge sites directly. Mobile convenience is higher (one app), but I prefer the desktop when I need to paste contract addresses or inspect transaction hex. But the mobile dApp browser can auto-trigger an "Add network" prompt which is handy.
See MetaMask mobile guide and WalletConnect guide for setup details.
Common transfer problems and troubleshooting
- Token not showing on L2: add the token contract address via add custom token.
- Bridge stuck or pending: check the bridge UI and tx on the block explorer. Consult network transfer issues.
- Sent to the wrong network: this is often irreversible unless a bridge/centralized service supports recovery.
If a transaction fails, check gas settings (EIP-1559 settings are used by MetaMask; see gas fees EIP-1559).
Security tips and best practices for L2 use
- Backup your seed phrase (store offline). Read seed phrase backup and recovery.
- Use hardware wallet integration for large balances (MetaMask supports connecting hardware devices).
- Revoke unlimited token approvals after use. See revoke approvals.
- Test bridges with small amounts first. Always.
What I've found: a single accidental unlimited approval once cost me time to revoke. I now always confirm the allowance amount in the approval popup.
Who MetaMask suits — and who should look elsewhere
Who this software wallet is for:
- Users who interact with many EVM-compatible dApps and L2s.
- People who value direct dApp connections (extension or mobile dApp browser).
Who might look elsewhere:
- Users who want built-in custody with insurance or fiat rails (use exchange services separately).
- Holders of very large balances who prioritize offline security first (consider hardware-only workflows).
FAQ
Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets are convenient for everyday DeFi and swaps. They increase attack surface compared with cold storage. I keep small active funds in my hot wallet and store the majority in a hardware wallet or other cold option.
Q: How do I revoke token approvals?
A: Use MetaMask to disconnect dApps and then visit tools that read your approvals. You can revoke approvals per token or per contract (see revoke approvals).
Q: What happens if I lose my phone?
A: Restore MetaMask on a new device with your seed phrase. If you lose the seed phrase, you lose access. See seed phrase backup and recovery for steps.
Conclusion & next steps
Adding L2s to MetaMask and moving funds between networks unlocks much cheaper DeFi activity. But bridges are the bridge between convenience and new risks. Test carefully. I encourage you to add an L2, move a very small test amount, and verify token visibility (then scale up).
Next reading: bridging overview, add custom token, and transaction simulation for safer transfers. Happy swapping — and double-check the network before you hit confirm.
