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 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.
Screenshot (placeholder):
If tokens don’t appear automatically, add them manually (see how-to-import-token).
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):
Use a reputable RPC endpoint. These are the typical values I use when I add Polygon to MetaMask:
| Field | Value |
|---|---|
| Network Name | Polygon Mainnet |
| New RPC URL | https://polygon-rpc.com |
| Chain ID | 137 |
| Currency Symbol | MATIC |
| Block Explorer URL | https://polygonscan.com |
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.)
| 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 |
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.
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 guide is for:
Who should look elsewhere:
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.
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.