How to Add New Networks to MetaMask

Every EVM-compatible blockchain is added to MetaMask the exact same way — the steps never change, only four network parameters do: the RPC URL, the chain ID, the currency symbol, and the block explorer. Instead of a separate tutorial for every chain, this page gives you the process once and a searchable table with verified parameters for 46 networks.

How to Add a Network to MetaMask (Any EVM Chain)

1. Open MetaMask and click the network selector in the top-left corner.
2. Click Add network, then Add a network manually. (Popular chains also appear in MetaMask’s built-in list — adding them from there is fine and skips the manual form.)
3. Fill in the Network name, RPC URL, Chain ID and Currency symbol from the table below. The block explorer field is optional but recommended.
4. Click Save. MetaMask validates the chain ID against the RPC — if they don’t match, re-check the RPC URL.
5. Switch to the new network via the network selector. Your address stays the same on every EVM chain.

That’s the whole process. Find your chain below — click any RPC URL to copy it.

Network Finder

Chains You Cannot Add to MetaMask Directly

MetaMask only speaks the Ethereum protocol. Chains built on other architectures have no chain ID or EVM RPC to enter — the manual form simply cannot connect to them. Use the chain’s own official wallet instead (or a MetaMask Snap where one exists):

• Solana — see our guide on using Solana with MetaMask via Snaps.
• Tron — see our guide on connecting Tron with MetaMask.
• Sui, Algorand, Celestia, Cosmos Hub, MultiversX, Tezos, VeChain, Polkadot — not EVM-compatible; use the official wallet of each ecosystem. (Cosmos-SDK chains that ship an EVM layer — like Kava, Cronos, Injective, Sei or Dymension — ARE in the table above.)

Verify Before You Add

Wrong RPC details are a real attack vector: a malicious RPC can show fake balances and trick you into signing transactions you don’t intend. The parameters above were taken from each project’s official documentation at the time of writing. RPCs do get rotated — if a connection fails or anything looks off, cross-check against the project’s own docs before saving, and never take network details from a DM or a random Telegram post.