Skip to content

Add a network to MetaMask

Pick a chain and press the button — MetaMask opens a confirmation with the correct chain ID, RPC endpoint and block explorer already filled in. Every endpoint below is a public, keyless node, last checked on 2026-09-14.

What this actually does. The button sends a standard wallet_addEthereumChain request. Your wallet shows you the parameters and nothing happens until you approve. It never touches your keys, your balances or your permissions.

Layer 1 networks

Layer 2 rollups

Testnets

Chains you cannot add

These come up constantly, and most guides about them are wrong. MetaMask cannot connect to them at all — here is what to use instead.

Common questions

Is it safe to add a network to MetaMask?

Adding a network only tells your wallet where to send requests. It does not give anyone access to your funds and cannot move anything on its own. The risk is a malicious RPC endpoint that shows you wrong balances or censors transactions, which is why every endpoint on this site is a public node published by the chain itself or by a known infrastructure provider.

Why does MetaMask say the chain ID does not match?

MetaMask asks the RPC endpoint which chain it serves and compares it with the chain ID being added. A mismatch means the RPC URL belongs to a different network, usually because it was copied from an out-of-date guide.

Can I add Tron, Solana or Cardano?

No. MetaMask implements the Ethereum JSON-RPC interface and only understands EVM chains with 0x addresses. Those three use entirely different address formats and protocols, so no custom-network setting will work.

My tokens disappeared after switching networks.

They did not move. Each network holds its own balances, and the same address exists on every EVM chain. Switch back to the network the tokens live on and they reappear.