Add Polygon (Matic) Network to MetaMask
Quick overview
This guide shows, step by step, how to add the Polygon (Matic) network to your MetaMask wallet so you can interact with EVM-compatible DeFi apps, swaps, staking dashboards, and NFT marketplaces that run on Polygon. I use MetaMask daily for cross-chain activity, including Polygon — so these are instructions I’ve tested firsthand. And yes, the mobile flow is different from the desktop extension; both are covered below.
Why add Polygon to your MetaMask wallet?
- Lower gas fees for many contract interactions compared with the Ethereum mainnet. Short sentence.
- Faster block confirmations (practical when you’re moving money or minting NFTs).
- Access to Polygon-native tokens and dApps directly inside MetaMask (once you switch networks).
Why bother? Because if you plan to bridge assets to Polygon or use Polygon-native DeFi, you need MetaMask to speak to the Polygon chain (that is, to send transactions and sign approvals on chain 137). But don’t mistake lower gas for zero risk — you'll still pay gas in MATIC and still face the same token-approval risks you know from Ethereum.
What you need before you start
Step by step: Desktop extension (how to add Polygon)
- Open the MetaMask extension and unlock your wallet.
- Click the network dropdown at the top (it usually says "Ethereum Mainnet").
- Select "Add network" or open Settings → Networks → Add a network.
- Choose "Add a network" and fill the Custom RPC form with the values in the table below. (Alternatively, a dApp may prompt MetaMask to add the network — verify the details before approving.)
- Click Save. MetaMask will switch to the Polygon network and show MATIC as the native currency.
Screenshot (placeholder): 
If tokens don’t appear automatically, add them manually (see how-to-import-token).
Step by step: Mobile app (how to add Polygon)
- Open MetaMask mobile and unlock.
- Tap the menu (top-left) → Settings → Networks → Add Network. (Some versions let you tap the network name directly to add.)
- Enter the same RPC details from the table below and save.
- Switch to the network from the network selector.
Mobile has an in-app browser. If a dApp asks to add Polygon via the Wallet RPC method (wallet_addEthereumChain), MetaMask mobile will prompt you. Pause and verify the RPC details before you accept. But if you prefer control, add the network manually.
Screenshot (placeholder): 
Polygon network RPC details (paste these)
Use a reputable RPC endpoint. These are the typical values I use when I add Polygon to MetaMask:
If you prefer a different public RPC, pick a well-known provider — or host your own node. (Public RPCs can go down; keep an alternative handy.)
Desktop vs Mobile: quick comparison
| Feature |
Desktop extension |
Mobile app |
| Adding network UX |
Settings → Networks (more clicks) |
Menu → Settings → Networks (faster on phone) |
| In-app browser & dApp prompts |
Works if dApp runs in browser |
Built-in browser makes dApp prompts smoother |
| WalletConnect |
Usually used from mobile to desktop dApps |
Can both initiate and accept WalletConnect sessions |
| Recommended for |
Heavy trading, hardware wallet connection |
Daily use, on-the-go swaps and dApp checks |
Common issues and fixes
- Tokens not showing? Add the token contract manually. See how-to-import-token and tokens-management.
- Transactions keep failing? Make sure you have MATIC in the Polygon account (fees are paid in MATIC) and that the network is set to Polygon (chain 137).
- RPC errors or “could not reach network”? Switch RPC URL to an alternate public endpoint or try again later.
- Sent tokens to the wrong chain? This happens when you use the same address across chains but pick the wrong network on the target chain. Contact the bridge or exchange guide for recovery steps, and read move-from-exchange if relevant.
If a dApp asks you to add multiple networks at once, slow down and verify — malicious sites sometimes inject fake RPCs that direct you to phishing explorers or ask you to sign risky transactions.
Security checklist when adding networks
- Verify RPC details from official documentation or trusted sources. Don’t copy RPCs from random pastebins.
- Never enter your seed phrase into a website or dApp. MetaMask will never ask for it to add a network.
- Watch token approvals on Polygon the same as on Ethereum. Revoke unlimited approvals if you don’t trust a contract (see revoke-approvals).
- Consider using a hardware wallet for large balances; connect it through MetaMask (see connect-ledger).
- Cloud backups are convenient but increase attack surface; weigh convenience vs risk. See backup-and-recovery-options.
But remember: a malicious RPC can't steal your private keys, but it can mislead you (fake balances, fake explorers, or censored data). So double-check.
Who this is for — and who should look elsewhere
Who this guide is for:
- Users who want to interact with Polygon dApps from MetaMask (swaps, staking, NFTs).
- People who use MetaMask as their daily hot wallet and need multi-chain support.
Who should look elsewhere:
- People holding large sums long-term who prefer cold storage (see hardware-best-practices).
- Users who want an auto-managed multi-chain experience without manual RPCs (use dedicated wallets or custodial services for that). I believe self-custody is worth the effort, but it’s not for everyone.
FAQ
Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets are convenient. They are not as secure as hardware wallets. For routine DeFi activity on Polygon I use a hot wallet for small amounts and a hardware wallet for larger positions (see security-best-practices).
Q: How do I revoke token approvals on Polygon?
A: Use a token-approval manager or a block explorer's token approvals tool and revoke unnecessary allowances. See revoke-approvals for a step-by-step guide.
Q: What happens if I lose my phone?
A: If you have your seed phrase backed up securely you can restore the wallet on another device. If you relied solely on a phone backup, recovery may be harder. See backup-and-recovery-options.
Conclusion & next steps
Adding Polygon to MetaMask is a small one-time setup that opens cheaper transactions and many Polygon-native DeFi and NFT opportunities. Follow the steps above, verify RPC details, and treat token approvals like real permissions (revoke when uncertain). In my experience, a cautious approach saves you from most common mistakes.
Read more: Add a custom network, How to import a token, or troubleshoot common issues at stuck-pending-transactions. Want a focused how-to with screenshots? See how-to-add-polygon.
If you want help picking which networks to add next, check networks-multi-chain or compare wallet flows at walletconnect-and-mobile-browser.
