Why Does MetaMask Show a Zero Balance After Adding a Custom Token?

24 September 2026

MetaMask shows a zero balance after adding a custom token because the token has not actually been transferred to your wallet, or because you have added the token using incorrect contract details. Adding a custom token to your MetaMask interface does not mean you own it - it simply tells the wallet to display that token's balance if it exists on your address. A zero balance means the blockchain records zero of that token for your account.

The token was never sent to your address

The most common reason is straightforward: you never received the token. People often add a custom token after seeing it mentioned in a post, a group chat, or a scam website. The token contract address is copied, pasted into MetaMask, and the token appears in the list - but with a balance of zero. This is not a bug. It is the correct behavior. You have no balance because no one sent that token to your wallet.

If you believe you should have received the token (for example, from an airdrop, a purchase, or a transfer), check the transaction history on a block explorer like Etherscan or BscScan. Enter your wallet address and look for any incoming transfers of that token. If none exist, the token was never sent.

You used the wrong token contract address

Each token on a blockchain is identified by a unique contract address. If you add a token using an incorrect or spoofed address, MetaMask will look at that contract for your balance. If the real token was sent to you under its correct address, but you added a different (possibly fake) address, MetaMask will show zero because the contract you added has no record of your balance.

How to check: - Find the official token contract address from a trusted source - typically the project's verified website, CoinGecko, CoinMarketCap, or Etherscan's token list. - Compare it character by character with the address you added in MetaMask. Even one wrong character means a different token. - Remove the incorrect token from MetaMask and add the correct one.

The Token Is on a Different Network

MetaMask manages multiple blockchain networks (Ethereum, Binance Smart Chain, Polygon, Avalanche, etc.). Each network is independent. If you added a token contract address that exists on Ethereum, but your wallet is set to Binance Smart Chain, the balance will show zero. The same applies if the token was sent to you on Polygon but you are viewing the Ethereum network.

Fix: Switch the network in MetaMask to the one where the token actually exists. If you are unsure, check the transaction that supposedly sent you the token - it will display which network was used.

The token contract has a custom decimal setting

Every token has a "decimals" parameter that determines how its balance is displayed. Most tokens use 18 decimals, but some use 6, 8, or other values. If you added the token manually and entered the wrong decimal count, MetaMask may display your balance incorrectly - often as zero or an extremely small number.

Solution: When adding a custom token, MetaMask usually auto-fills the decimals from the contract. If you override this field, re-check the correct decimal value from the token's page on a block explorer. Remove and re-add the token without changing the decimals field.

MetaMask Hasn't Finished Syncing or Has a Cache Issue

Occasionally, MetaMask's cached data for a token can become stale or corrupted. This is rare but can cause a zero balance display even when the blockchain says you hold tokens.

Fix: 1. Close MetaMask completely (close the browser tab or mobile app). 2. Reopen and refresh the page. 3. If the balance is still zero, try switching to another network and back. 4. As a last step, reset MetaMask's account activity: Settings > Advanced > Clear activity tab data. This does not affect your funds - it only clears local transaction history.

The Token Is a Scam or Has No Liquidity

If you received an unsolicited token (a "dusting" attack or a scam airdrop), the token may be designed to appear worthless or to trick you into interacting with a malicious contract. A zero balance after adding such a token is normal - the token may have been designed to never show a balance, or it may have been removed from your wallet by the scammer after you approved a transaction.

Do not interact with unknown tokens that appear in your wallet. If you did not request or purchase the token, treat it as suspicious.

Summary of Steps to Diagnose a Zero Custom Token Balance

1. Confirm the token was actually sent to your address - check a block explorer.
2. Verify the token contract address you added matches the official address exactly.
3. Ensure you are viewing the correct blockchain network.
4. Check the token's decimal setting - do not override the auto-filled value.
5. Restart MetaMask or clear cached data.
6. If none of these resolve it, the token likely does not exist in your wallet.

Back to metamask