Quick, practical instructions for adding the Polygon (Matic) network to your MetaMask extension or mobile app. I use this setup daily to interact with Polygon DeFi and can tell you when to be careful.
Polygon is an EVM-compatible chain that runs many DeFi apps with far lower gas fees than Ethereum mainnet. If you use DEXs, bridges, or staking services on Polygon, adding the network to your MetaMask account makes those dApps connect directly (no extra wallets required). Short story: faster and cheaper testing and trading. Switch networks and you're done.
Why does this matter? Because interacting with Polygon from the wrong network leads to failed transactions and, sometimes, lost funds.
And always test with a tiny amount first. But don't skip the backup step.
You can add Polygon manually by entering these values into MetaMask's Add Network form. These are the common, public values used by most nodes:
| Field | Value |
|---|---|
| Network Name | Polygon Mainnet |
| New RPC URL | https://polygon-rpc.com/ |
| Chain ID | 137 (decimal) / 0x89 (hex) |
| Currency Symbol | MATIC |
| Block Explorer URL | https://polygonscan.com/ |
If you'd rather use MetaMask's built-in chain list, there's usually an option to search and add Polygon automatically. Manual entry uses the same fields as the custom RPC guide.
I prefer the manual RPC method. It avoids odd third-party RPC endpoints. In my experience, entering the RPC URL yourself reduces surprises.
Mobile UX is slightly different. The fields are identical, but the navigation is app-based rather than a browser popup. If you're connecting to mobile dApps, WalletConnect is often used as an alternative (see /walletconnect-and-mobile-browser).
Common confusion: "Do I need a Polygon Matic contract address in MetaMask?"
Short answer: No for native MATIC. MATIC is the native chain token on Polygon and doesn't require a contract address to receive. For ERC-20 tokens on Polygon (WMATIC, USDC, etc.) you do need the token contract address — copy it from a verified source (for example, Polygonscan) and paste it in MetaMask's Import Token form. See /how-to-import-token and /token-management for step-by-step instructions.
Pro tip: if your balance is zero after switching to Polygon, check the token list and add the token contract address manually. It happens all the time.
You can use a hardware wallet to sign Polygon transactions through MetaMask. Connect the Ledger via USB (desktop) or through supported mobile workflows, then open the account in MetaMask (see /how-to-connect-ledger). If you use Ledger, MetaMask acts as the interface while signing stays on the device.
Security notes (short, actionable):
And if you're unsure about a dApp, test with a tiny amount first.
| Symptom | Likely cause | Fix |
|---|---|---|
| No balance after switching | Token not added to MetaMask | Add token contract address via Import Token; check /not-showing-balance |
| Transactions pending forever | Wrong network selected or low gas | Confirm you're on Polygon; increase gas if needed; see /stuck-pending-transactions |
| A dApp won't connect | Provider mismatch (WalletConnect vs injected) | Use the correct connect option on the dApp or open site in MetaMask's browser; see /connect-to-dapps |
If transactions fail repeatedly, export logs and compare the network and gas settings (see /transaction-troubleshooting).
Who this setup fits:
Who should look elsewhere:
In my experience, combining MetaMask with a hardware wallet gives a reasonable balance between convenience and safety.
Q: Is it safe to add Polygon to MetaMask? A: Yes, adding a network is low-risk. The main risks are using malicious RPC endpoints or connecting to phishing dApps. Verify RPCs and only connect to vetted dApps.
Q: How do I find the Polygon/MATIC contract address to add a token? A: Use Polygonscan or the dApp's verified documentation. Remember: native MATIC doesn't need a contract address; only tokens do (WMATIC, USDC, etc.).
Q: Why is my MetaMask address the same on Ethereum and Polygon? A: Both are EVM-compatible networks that use the same keypair format. Your account address is derived from your private key, so it's identical across EVM chains if you use the same account.
Q: Can I use Ledger with Polygon in MetaMask? A: Yes. Connect your Ledger and open the Polygon account via MetaMask's hardware wallet flow. See /connect-ledger and /how-to-connect-ledger for details.
Q: What if I lose my phone? A: Restore with your seed phrase on another device (see /backup-and-recovery-options). If you used a hardware wallet for signing, that changes the recovery steps.
Adding Polygon to MetaMask is fast and gives you access to cheaper DeFi activity (swaps, staking, bridges). Start by adding the RPC values above, switch to Polygon, and send a tiny test transaction. Test first. Be careful with token approvals and RPC endpoints.
Useful follow-ups: Add Polygon network (alternate guide), bridging tips, and token management.
Ready to add Polygon? Follow the desktop or mobile steps above and confirm with a small transfer. What I've found: small tests catch most mistakes early.