Tokens not showing in MetaMask after adding a network can be displayed by importing each token’s contract address. First confirm the tokens are held by your address on that network; adding a network supplies MetaMask with a chain ID, RPC endpoint and native currency, not a token list. In Chainlist, the chain ID and block explorer help you verify the network and locate your holdings. Compare the explorer balance with the balance after import; matching amounts mean MetaMask is displaying your on-chain tokens.
Why Are Tokens Missing After Adding a Network?
Missing ERC-20 tokens usually reflect absent token detection, a different chain, or an RPC endpoint behind the current block.
Token detection has not listed the token. The tell is a visible native currency but no token row, while the block explorer shows that ERC-20 holding for your address. MetaMask’s automatic token detection runs only on supported networks. Adding a custom network through Chainlist connects the wallet to that chain; it does not extend token detection to it. On most custom networks, waiting will not add the token automatically. Even on supported networks, less common tokens may remain unlisted.
Search your public wallet address on that network’s explorer. Open the holding under Tokens and copy the token contract address from its page. This identifies the token on that chain; it differs from your wallet address, and the same symbol can refer to different contracts. In MetaMask’s Tokens view, open Import tokens, or open Manage tokens and choose Add custom token. Paste the contract address, review the details and confirm Import. Its displayed balance should match the explorer. Repeat for each missing token. On a supported network, you can also enable Basic Functionality under Settings > Privacy and refresh the asset list.
The tokens are on another chain. The tell is zero on the new network’s explorer but a holding on the chain used in the transfer or bridge. As an illustrative case, say USDC arrived on Base but you added Polygon: filtering the Tokens view to Polygon will not show the Base holding. Read the transfer’s network and recipient, select the correct network in MetaMask, and import that network’s token contract. The balance should match its explorer. A contract copied from another chain can point to the wrong asset or fail to import.
The RPC is lagging. The tell is an explorer holding but an old or zero balance in MetaMask after import. An RPC endpoint supplies blockchain state to MetaMask; one behind the latest block can report an older balance. If Chainlist shows the endpoint’s block height, compare it with the explorer’s latest block. If it trails, choose another RPC for the same chain ID with a current height. Edit the network’s RPC URL in MetaMask and refresh the token view. A matching balance identifies stale RPC data as the cause.
When none of these signs fits, compare the public address in MetaMask with the explorer address. Inspect the transaction hash on the chain used to send the tokens: look for a successful transfer to that address. No explorer holding means you need to trace the transfer or its recipient, since importing cannot create a balance. If the holding exists but MetaMask still differs after import and an RPC change, verify the contract again and contact MetaMask support with the network, public address and transaction hash.
Related Questions
How Do I Remove a Token From MetaMask?
To remove a token from MetaMask’s view, open it and choose Hide from its menu; on mobile, press and hold it. Hiding changes the display, not your on-chain balance. The native currency cannot be hidden.
Why Does a Token Show No USD Value in MetaMask?
A token can show its unit balance without a USD value because MetaMask has no price for it. Compare the contract and trading markets before relying on an outside price. The missing dollar estimate does not change the number of tokens held.
Start with your address on the correct block explorer: its token holding tells you which contract to import and which balance MetaMask should show.