How to Import a Token to MetaMask on Polygon (2026)
MetaMask doesn’t automatically display every token that exists on Polygon. It shows a default list of well-known tokens, and anything outside that list needs to be added manually. When I created RizeCoin, it wasn’t in any default list. Searching by the symbol “RZC” found nothing. The only way to add it was through the contract address.
When I did that, MetaMask showed a warning: this is an unknown token, proceed with caution. That warning still appears today because RizeCoin isn’t a verified token on any major list. For a new or custom token, this is normal. Understanding what that warning means — and when it’s safe to proceed — is what this guide covers.
Why Tokens Don’t Appear Automatically
MetaMask maintains a list of verified tokens with known contract addresses, names, and symbols. Any token on that list appears automatically when you receive it. Any token not on that list is invisible until you import it manually.
This isn’t a bug. It’s a security measure. If MetaMask automatically displayed every token sent to your wallet, scammers could flood your wallet with fake tokens designed to look like real ones. By requiring manual import, MetaMask puts the responsibility of verification on you.
Step 1 — Find the Token’s Contract Address
You need the exact contract address of the token you want to import. This is a 42-character string starting with “0x” that uniquely identifies the token on Polygon.
PolygonScan: Search the token name on polygonscan.com. The contract address appears on the token’s page.
DexScreener: Search the token on dexscreener.com. The contract address is listed on the token’s trading page.
The project’s official source: If you received the token from a specific project, get the contract address from their official website or documentation.
Fake tokens with identical names exist. Importing the wrong contract address means you’re importing a completely different token. One wrong character in the address and you’re looking at a scam token. Always cross-check the address before importing.
Step 2 — Open MetaMask and Go to Import Tokens
Open MetaMask and make sure you’re on Polygon Mainnet. Scroll down on the main screen past your token list. At the bottom you’ll see “Import tokens” — click it.
On mobile, you may need to tap the token list area and scroll to find the import option.
Step 3 — Enter the Contract Address
Paste the contract address into the “Token contract address” field. MetaMask will attempt to look up the token automatically.
Verified token: MetaMask fills in the token name and symbol automatically. Review and confirm.
Custom or new token: MetaMask shows a warning — “This token isn’t verified. Only import tokens you trust.” The name and symbol fields may be blank or need to be filled in manually. This is what happened with RizeCoin.
When I import RizeCoin using its contract address, MetaMask shows the custom token warning. This doesn’t mean RizeCoin is a scam — it means MetaMask hasn’t verified it against its approved list. Any new or small token will trigger this warning.
The question to ask yourself when you see this warning: do I know and trust the source of this contract address? If yes — you got it from PolygonScan, from the official project page, or from a source you verified — it’s safe to proceed. If you’re not sure where the address came from, stop and verify first.
Step 4 — Review and Confirm
Review the token details — name, symbol, and decimal places. If they match what you expected, click “Import.” The token will appear in your MetaMask wallet with its current balance.
What to Do If the Token Still Doesn’t Show a Balance
If you’ve imported the token but the balance shows zero:
2. Confirm you’re on Polygon Mainnet in MetaMask — not Ethereum or a testnet.
3. Check that you imported the correct contract address. If the address was wrong, remove the token and import again with the correct address.
4. Try refreshing MetaMask or restarting the app. Sometimes balances take a moment to load.
Comments