Why Is My Token Not Showing in MetaMask?

A token not showing in MetaMask means the wallet interface does not display a token balance that the user expected to see. This can happen after receiving tokens, swapping on a DEX, claiming an airdrop, bridging assets, importing a custom token, switching networks, or sending funds to a wallet address. The token may be present on-chain but hidden in the wallet display, or the transaction may not have completed as expected. For the broader concept, read Why Token Does Not Appear in Wallet.

This issue matters because MetaMask can only show token balances for the selected wallet address and selected network. A token on Ethereum is not automatically visible on BNB Smart Chain, Base, Arbitrum, Polygon, or another EVM-compatible network. The token contract, network, wallet address, transaction status, and explorer result should all match before assuming the token is missing. For network basics, read What Is a Blockchain Network?.

This guide will help you check whether the token exists on-chain, confirm the correct network, verify the wallet address, compare the token contract with an official source, import the token safely, understand pending or failed transaction cases, and avoid fake token or recovery scams. The goal is not to trust the wallet screen alone. The goal is to verify the token from the correct explorer before signing another wallet request.

Quick fix answer

A token is usually not showing in MetaMask because the wallet is on the wrong network, the token contract has not been imported, the transaction is still pending or failed, the token was sent to a different wallet address, the token exists on another chain, MetaMask or the RPC endpoint is delayed, or the token contract is fake or unsupported. The safest first step is to check the wallet address, network, transaction hash, and token contract on the correct block explorer before importing anything.

Fast checklist: Confirm the MetaMask account address, select the correct network, open the wallet address or transaction hash on the correct explorer, verify the token contract from an official source, import the token only if the contract is correct, and stop if any page asks for a seed phrase or private key.

Simple example: You swapped for a token on Polygon, but MetaMask is still showing Ethereum Mainnet. The token may not appear until you switch MetaMask to Polygon and import the verified Polygon token contract. Before importing, check the transaction and token contract on the Polygon explorer.

Before you try to fix it

Many missing-token problems look like MetaMask bugs, but the real cause may be a wrong network, missing custom token import, delayed RPC response, pending transaction, failed swap, wrong token contract, wrong receiving address, bridge delay, or a token that exists only on another chain. The wallet interface is useful, but it is not always the final source of truth. For important checks, use the block explorer for the correct network.

A safe fix starts with observation, not action. Do not immediately connect to a random recovery page, approve a new contract, sign a message, import a token from a comment, or follow a support link from social media. First identify whether the issue is only a display problem, a pending transaction, a wrong network, a wrong contract, a bridge delay, or a scam token. For link safety, read How to Check Official Links.

Why this problem matters

Token display fixes can involve real wallet actions. Importing a token contract changes what appears in the wallet interface. Switching networks changes which chain MetaMask is viewing. Approving a contract can grant spending permission. Signing a message can authorize app-level actions. Because of this, users should verify the token and network before trusting a claim page, swap page, token page, or support instruction.

The larger risk is that missing-token users often become targets for fake support and recovery scams. A scammer may say the token must be “synced,” “validated,” “unlocked,” or “manually restored” by entering a seed phrase, approving a contract, signing a message, or sending a fee. A normal token display fix should not require revealing secret wallet information. If a page or person asks for wallet secrets, review How to Avoid Crypto Scams before continuing.

Useful next step: If network names, token contracts, gas tokens, and explorers feel confusing, read What Is Blockchain? and Why Wallet Network Matters first. Most MetaMask display issues depend on knowing which network the token actually belongs to.

The basic fix idea

The safest way to troubleshoot a token not showing in MetaMask is to separate wallet display from on-chain balance. MetaMask may not automatically list every token on every network. The block explorer can show whether the wallet address actually received the token, which token contract was involved, and whether the transaction succeeded, failed, or is still pending.

1. Identify the correct network first

Start by checking which network MetaMask is currently showing. A token on Ethereum, BNB Smart Chain, Base, Arbitrum, Polygon, Avalanche, Optimism, or another EVM-compatible network must be checked on the matching explorer. Same-looking wallet addresses can exist across many networks, but balances and token contracts are separate. For a deeper explanation, see Why Wallet Network Matters.

2. Check the wallet address on the correct explorer

Copy the exact MetaMask account address and search it on the explorer for the network where the token should exist. Review token transfers, contract interactions, and balances. If you have a transaction hash, open it directly and check the status, token transfer events, sender, recipient, token contract, amount, and timestamp.

3. Compare the token contract with an official source

Token names, symbols, and logos are not enough. A fake token can copy the same ticker and branding as a real token. Before importing a token into MetaMask, compare the contract address with the official project website, documentation, verified announcement, or trusted contract reference. Do not import token contracts from random comments or direct messages.

4. Import the token only after verification

If the explorer shows the token at your MetaMask address but the wallet does not display it, the token may need to be imported manually. Use the verified token contract on the correct network. After import, confirm that the symbol, decimals, balance, and network match the explorer. For general balance issues, read Why Wallet Balance Does Not Show.

Common causes

A token may not show in MetaMask for several reasons. Some are simple display issues, while others point to a failed transaction, wrong network, wrong address, bridge delay, fake token, or unsafe page. Each cause requires a different safe response.

Cause 1: MetaMask is on the wrong network

MetaMask shows balances for the currently selected network. If the token was received on Polygon but MetaMask is viewing Ethereum Mainnet, the token may appear missing. Switch only to the network where the token actually exists and check the matching explorer. For the full wrong-network flow, read How to Fix Wrong Network in Wallet.

Cause 2: The custom token has not been imported

MetaMask may not automatically show every token. If the token exists on the explorer but not inside the wallet, it may need to be imported using the correct contract address. Only import a token after verifying the contract from an official source. A fake import can make a scam token appear more legitimate than it is.

Cause 3: The transaction is still pending

If the transfer, swap, claim, or bridge transaction is still pending, the token may not appear yet. Open the transaction hash on the correct explorer and check whether it is pending, confirmed, failed, dropped, or replaced. If the transaction is pending, read Why Is My Transaction Pending?.

Cause 4: The transaction failed or reverted

A failed transaction may spend gas without completing the intended token transfer. If the explorer shows a failed or reverted status, the token may not have arrived at all. Review the transaction status, event logs, token transfers, and error message before assuming MetaMask is hiding the token. For error reading, see How to Read Transaction Error Messages.

Cause 5: The token was sent to a different address

A token will only appear in the MetaMask account that actually received it. If the sending app, exchange, bridge, or contact used a different recipient address, switching networks or importing the token will not fix the balance. Compare the recipient address on the explorer with the exact MetaMask account address.

Cause 6: The token exists on a different chain

A token may share the same symbol across multiple networks, but each network can have a different token contract. If a token was bridged, withdrawn, or swapped on a different chain than expected, it may only appear after choosing the correct network and importing the correct contract. If you used the wrong network, read What to Do If You Used the Wrong Network.

Cause 7: MetaMask, RPC, or indexer data is delayed

Sometimes the blockchain already shows the token, but MetaMask or the RPC endpoint has not updated. Refreshing the wallet, switching away and back to the correct network, checking another official explorer, or waiting briefly may help. Avoid sending new transactions just because the wallet display is delayed.

Cause 8: The token came from a bridge and the destination step is delayed

Bridge transfers can involve a source-chain transaction and a separate destination-chain result. If the source transaction succeeded but the destination token is not visible, the bridge may still be relaying, waiting for confirmations, or requiring a manual claim. See Why Bridge Transaction Is Delayed for the bridge-specific flow.

Cause 9: The token contract is fake or unsafe

Fake tokens can appear on explorers and inside wallets. A token that appears in MetaMask is not automatically valuable, official, or safe to interact with. Be cautious with tokens received unexpectedly, tokens that ask users to visit a claim site, and tokens that require suspicious approvals to sell, claim, or unlock.

How to apply the fix in practice

Use this process before importing a token, retrying a transaction, trusting a claim page, or contacting support. It is designed for global MetaMask users across different EVM-compatible networks, explorers, token contracts, DEXs, bridges, and crypto apps.

Copy your MetaMask address: Make sure you are checking the exact account that should receive the token.
Confirm the expected network: Identify where the token should exist, such as Ethereum, BNB Smart Chain, Base, Arbitrum, Polygon, or another supported network.
Open the correct explorer: Search your wallet address or transaction hash on the explorer for that network.
Check transaction status: Confirm whether the transfer, swap, claim, bridge, or withdrawal is pending, confirmed, failed, dropped, or replaced.
Verify the token transfer: Check whether the token transfer event shows your MetaMask address as the recipient.
Verify the token contract: Compare the contract address with an official source before importing it.
Switch to the correct network: In MetaMask, view the network where the token exists. Avoid adding unknown networks from untrusted pages.
Import the token if needed: Use the verified contract address, symbol, and decimals on the correct network.
Check for bridge or withdrawal delays: If the token came from a bridge or exchange, confirm whether the destination transaction has completed.
Verify the final result: After importing or switching networks, compare the MetaMask balance with the explorer balance.

Related guide: If the token appeared after a swap but the swap result is unclear, read Why Did My Token Swap Fail?. If the token came from a suspicious airdrop or claim page, read How to Avoid Crypto Scams.

Detailed troubleshooting checklist

This checklist helps separate a normal MetaMask display issue from a failed transaction, wrong network, wrong address, fake token, delayed bridge, or unsafe support page.

MetaMask account: Confirm that the selected account is the same wallet address that should hold the token.
Network: Confirm the correct chain name, chain ID if shown, gas token, explorer, and MetaMask network selection.
Transaction hash: If available, use the hash to check pending, success, failure, replacement, dropped status, confirmations, and token transfer events.
Recipient address: Confirm that the token transfer event points to your MetaMask address.
Token contract: Compare the contract address with an official source. Do not rely only on token symbol, logo, or name.
Token decimals: Check whether the imported decimals match the verified token contract. Wrong decimals can make balances look incorrect.
Bridge status: If the token came from a bridge, check both the source and destination explorers.
RPC or display delay: If the explorer shows the token but MetaMask does not, refresh carefully and verify the network again.
Wallet request: Do not approve, sign, or connect to a page just because it claims it can make the token appear.
Result: After any import or network change, verify the token balance in both MetaMask and the correct explorer.

What not to do

A rushed missing-token fix can create a larger problem than the display issue. The goal is not to make any token appear at any cost. The goal is to verify the correct wallet, network, transaction, and contract before taking action.

Do not enter a seed phrase, private key, recovery phrase, or secret phrase into any website that claims it can make a token appear in MetaMask.
Do not import a token contract from a random comment, direct message, search result, or social media post without checking an official source.
Do not approve token spending just to view a missing token balance.
Do not assume a token is official because it has a familiar symbol, logo, or name.
Do not send more funds to “activate,” “unlock,” “sync,” or “release” a token balance.
Do not repeatedly retry a swap, claim, withdrawal, or bridge before checking the transaction hash on the correct explorer.
Do not trust fake support accounts that ask for wallet validation, remote access, upfront fees, or secret wallet information.

Common mistakes

MetaMask token display issues are confusing because the wallet shows a simplified version of on-chain data. A user may see a missing token, wrong balance, custom token form, transaction hash, or explorer page and assume it proves more than it actually proves. Safer troubleshooting means checking the same token from the wallet, explorer, and official source.

Mistake 1: Staying on the wrong network

A token received on one network will not appear while MetaMask is viewing another network. Check the network where the transaction happened, not only the network you expected to use. A same-looking address does not mean the same balance across chains.

Mistake 2: Importing the wrong token contract

Importing the wrong contract can display an unrelated or fake token. Always compare the contract with an official project source and the correct network before importing. Token symbols are not unique.

Mistake 3: Assuming a pending transaction already delivered the token

If the transaction is still pending, the token may not have arrived yet. If the transaction failed, the token may never have transferred. Use the transaction hash on the correct explorer to confirm the real status.

Mistake 4: Confusing bridge completion with source-chain success

A bridge source transaction can succeed before the destination token arrives. If the token was bridged, check the bridge status and destination explorer before assuming MetaMask is hiding the token.

Mistake 5: Trusting fake support or recovery pages

Search results, social replies, direct messages, and fake support pages may claim to fix missing MetaMask tokens. Be cautious if the fix requires seed phrases, private keys, remote access, broad approvals, upfront fees, or unclear signatures.

Mistake 6: Thinking every visible token is safe

A token appearing in MetaMask does not automatically mean it is official, valuable, or safe to trade. Scam tokens may appear in a wallet and direct users to unsafe websites. Verify the token before interacting with it.

When to be extra careful

Some missing-token fixes deserve extra caution because the next action can expose funds, permissions, wallet history, or future token access. Slow down if the fix requires a wallet connection, token approval, signature, network addition, custom token import, bridge claim, or support contact.

Before importing a token: Confirm the token contract, network, symbol, and decimals from an official source.
Before adding a network: Verify the network details from official documentation or a trusted source, especially RPC URLs and chain IDs.
Before connecting a wallet: Verify the domain spelling, official website, app purpose, and whether a wallet connection is actually needed.
Before signing a message: Read the message content and avoid signatures from pages claiming to “sync,” “validate,” or “restore” missing tokens.
Before approving token spending: Check the token, spender contract, network, amount, and whether approval is necessary for the action.
Before contacting support: Share transaction hashes, addresses, network names, token contracts, and screenshots, but never seed phrases, private keys, passwords, or recovery codes.

How to know the fix worked

A missing-token fix is complete only when the token state is clear. The explorer should show whether the token exists at the wallet address, and MetaMask should show the token on the correct network after import or indexing. If the transaction failed, the fix is understanding that the token never arrived, not forcing the wallet to show it.

For wrong-network issues: MetaMask, the token contract, the transaction hash, and the explorer should all match the same network.
For successful transfers: The explorer should show your MetaMask address as the token recipient.
For custom token imports: MetaMask should show the token using the verified contract, symbol, decimals, and network.
For pending transactions: The explorer should eventually show confirmed, failed, replaced, or dropped status.
For bridge transfers: The destination explorer should show the destination token at the receiving address.
For scam concerns: No fix should require entering a seed phrase, private key, recovery phrase, or secret phrase.

FAQ

Why is my token not showing in MetaMask?

A token may not show in MetaMask because the wallet is on the wrong network, the custom token has not been imported, the transaction is pending or failed, the token was sent to a different address, the token exists on another chain, or MetaMask has not updated its display. Check the correct explorer before importing anything.

How do I check if the token is actually in my wallet?

Copy your MetaMask account address and search it on the explorer for the network where the token should exist. If you have a transaction hash, open it directly and check the recipient address, token contract, amount, status, and token transfer events.

Should I import a custom token into MetaMask?

Only after verifying the token contract from an official source. Importing a custom token can help display a real balance, but importing the wrong contract can make an unrelated or fake token appear in the wallet.

Why does the explorer show my token but MetaMask does not?

MetaMask may be on the wrong network, missing the custom token import, using delayed RPC data, or waiting for indexing. If the explorer shows the token at your address, switch to the correct network and import the verified token contract if needed.

What if my token disappeared after switching networks?

The token may exist on the previous network, not the one currently selected. MetaMask displays balances by network. Switch back to the network where the token exists and confirm the wallet address and token contract on the matching explorer.

What if the token came from a bridge?

Check both the source-chain transaction and the destination-chain result. A bridge may take time to relay, release, mint, or claim the token on the destination network. Read Why Bridge Transaction Is Delayed for the bridge-specific troubleshooting path.

What if the token came from a swap?

Open the swap transaction on the correct explorer and check whether the swap succeeded, failed, or transferred the expected output token. If the swap failed, the token may not have arrived. See Why Did My Token Swap Fail?.

Can a scam token show in MetaMask?

Yes. A token appearing in MetaMask does not prove it is official, valuable, or safe. Be careful with unexpected tokens, fake claim messages, and tokens that direct you to an external website. Review How to Avoid Crypto Scams before interacting with unknown tokens.

What if a website asks for my seed phrase to show the token?

Do not enter a seed phrase, recovery phrase, private key, or secret phrase into any website. A normal MetaMask token display fix should not require revealing wallet secrets. Treat that request as a serious warning sign.

Related concepts

This fix connects to several beginner crypto concepts. Reading these pages can help users understand why MetaMask token display depends on the correct network, wallet address, token contract, transaction status, explorer result, and safe source verification.

Summary

If a token is not showing in MetaMask, the safest response is to verify the token on the correct block explorer before importing anything. The most common causes are wrong network selection, missing custom token import, pending or failed transactions, wrong recipient address, bridge delay, RPC delay, or incorrect token contract. Check the selected MetaMask account, network, transaction hash, recipient address, token transfer event, token contract, symbol, and decimals. If the explorer shows the token at your address, switch to the correct network and import only the verified token contract. If the transaction failed or never reached your address, the token may not have arrived. If the token came from a bridge, check both source and destination networks. Never enter a seed phrase, private key, or recovery phrase into a website claiming it can make a token appear.

The safest troubleshooting habit is to verify before acting. Check the network, wallet address, transaction hash, token contract, wallet request, and final explorer result before approving another action. This reduces the chance of using the wrong network, importing a fake token, trusting a scam support page, approving an unsafe spender, or repeating a transaction unnecessarily.

Eonwell does not recommend any specific wallet, token, exchange, protocol, service, or transaction. This page is for neutral crypto education only.

Topics