tl;dr: MetaMask ships with Ethereum only, so any other chain — Polygon, BNB Chain, Avalanche, Cronos, Fantom — has to be added by hand or through Chainlist. This guide walks you through both methods, the exact RPC details you need, how to avoid the "wrong network" mistakes that lose funds, and where to go next for each specific chain.
You installed MetaMask, funded it, and then tried to send tokens on Polygon or BNB Chain — only to find the network isn't even there. That's normal. MetaMask defaults to Ethereum Mainnet and nothing else. Every other EVM chain is something you add yourself.
The good news: adding a network takes about a minute once you know the drill. The bad news: one wrong RPC URL or Chain ID and your transaction lands nowhere. This guide covers the safe way to add any EVM network, the details that actually matter, and the per-chain guides for when you want the exact steps.
Why MetaMask Only Shows Ethereum by Default
MetaMask is an EVM (Ethereum Virtual Machine) wallet. It speaks the same language as dozens of chains — Polygon, BNB Chain, Avalanche C-Chain, Cronos, Arbitrum, and more — but it only ships pre-configured for Ethereum Mainnet. Everything else is opt-in.
Each EVM chain is identified by four things: a network name, an RPC URL (the node your wallet talks to), a Chain ID (a unique number), and a native currency symbol. Get all four right and your wallet connects. Get one wrong and you either can't connect or, worse, you sign transactions against the wrong chain.
Method 1: Add a Network Automatically with Chainlist
The fastest, lowest-risk way is Chainlist, a community-maintained directory of EVM networks. You connect MetaMask, search the chain you want, click "Add to MetaMask," and approve. No manual typing, no Chain ID typos.
Steps:
- Open chainlist.org and click "Connect Wallet."
- Search for your chain (for example "Polygon" or "Cronos").
- Click "Add to MetaMask" on the correct result.
- Approve the prompt in MetaMask.
One caution: Chainlist lists multiple RPC endpoints per chain, and some public ones are slow or unreliable. If transactions hang, switch to a different RPC for that network. Understanding how the underlying endpoint behaves helps here — it's the same idea behind how the Matic RPC endpoint works on Polygon.
Method 2: Add a Network Manually
When a chain isn't on Chainlist, or you want full control, add it by hand. In MetaMask: open the network dropdown, choose "Add network," then "Add a network manually." Fill in five fields:
- Network Name — a label for you (e.g. "Polygon Mainnet").
- New RPC URL — the node endpoint.
- Chain ID — the unique network number.
- Currency Symbol — the native gas token (POL, BNB, AVAX, CRO...).
- Block Explorer URL — optional, but useful for tracking transactions.
Always source these values from the chain's official documentation, never from a random forum post or a link in a DM. A fake RPC URL can route your requests through a malicious node.
Reference Values for the Most-Added Chains
Here are the mainnet parameters for the chains people add most often. Verify against official docs before use, since RPC URLs change:
| Chain | Chain ID | Currency | Public RPC |
|---|---|---|---|
| Polygon (PoS) | 137 | POL | https://polygon-rpc.com |
| BNB Smart Chain | 56 | BNB | https://bsc-dataseed.binance.org |
| Avalanche C-Chain | 43114 | AVAX | https://api.avax.network/ext/bc/C/rpc |
| Cronos | 25 | CRO | https://evm.cronos.org |
Note on Fantom: the network formerly branded as Fantom has migrated to Sonic (S). If you're following older "add Fantom" instructions, check whether you actually want the legacy Opera chain (ID 250) or the newer Sonic network, and confirm the current RPC from official sources before adding.
Per-Chain Step-by-Step Guides
Once you understand the pattern, the per-chain specifics are quick. For Polygon, the exact fields and a screenshot walkthrough live in our guide on adding the Polygon (MATIC) network to MetaMask. If you're heading to the BNB ecosystem, follow adding Binance Chain to MetaMask. For high-throughput apps on Avalanche, use adding the Avalanche network to MetaMask. And for the Cronos ecosystem, see adding the Cronos network to MetaMask.
Common Mistakes That Cost People Money
Adding a network is simple, but a few errors show up again and again:
- Wrong Chain ID. Two networks with the same name but different IDs will silently fail. Double-check the number.
- Sending to the wrong network. Tokens sent on BNB Chain to an address expecting them on Polygon can be stuck or lost. Confirm the network before every send.
- Unofficial RPC URLs. Only use endpoints from official docs or trusted directories.
- Ignoring gas token. Each chain needs its own native token for gas — you can't pay Polygon fees with ETH.
If you're weighing which chain to build or transact on in the first place, it helps to understand the trade-offs — for example, how Polygon compares to BSC on cost and infrastructure.
Managing Tokens and Wallets Across Chains
Adding networks is only half the job — you also manage assets on each one. Learning how to make use of a token in MetaMask (importing custom token contracts, spotting scam tokens) keeps your portfolio readable. If you outgrow MetaMask's interface, you can look at importing your MetaMask account into Rabby, or compare the best Polygon (POL) wallets for 2026 if Polygon is your main chain — and there's a broader breakdown on choosing the right Polygon wallet for your needs.
When it's time to move value off-chain, our walkthrough on cashing out from MetaMask to your bank covers the safe route. And if you run across chains a lot, comparing multi-chain launchpads across Polygon and BNB Chain shows where the activity is. For a hardware angle, there's also a comparison of everyday-carry hardware wallets.
Frequently Asked Questions
Is it safe to add a network to MetaMask?
Yes, as long as the RPC URL and Chain ID come from official sources. Adding a network doesn't move funds or grant access — it just tells MetaMask which node to talk to. The risk is only from fake RPC endpoints.
Why isn't my added network showing tokens?
Native balances appear once you switch to the network, but ERC-20 style tokens must be imported by their contract address. Custom tokens don't auto-appear.
Can I use the same address on every chain?
Yes. Your MetaMask address is the same across all EVM chains. The balances differ per network, but the address is identical.
What happened to Fantom?
Fantom rebranded and migrated to Sonic (S). Older guides may still reference the legacy Opera network. Confirm the current chain and RPC from official documentation before adding.
Disclaimer: This article is for educational purposes only and is not financial or security advice. Network parameters like RPC URLs and Chain IDs change over time — always verify against each chain's official documentation before adding a network, and do your own research (DYOR) before moving funds.