How to fix MetaMask "Not showing all tokens"? (Manual Import)

Understanding the Token Visibility Issue

1. MetaMask does not automatically detect every ERC-20, ERC-721, or ERC-1155 token held in a wallet address unless they are explicitly added to its interface.

2. The default token list relies on community-submitted assets and centralized token lists maintained by ConsenSys, which may omit newly deployed or low-liquidity tokens.

3. Tokens deployed on non-Ethereum EVM-compatible chains—such as Polygon, BSC, or Arbitrum—require correct network configuration before visibility becomes possible.

4. Wallet address scanning is limited to tokens with verified contract addresses and standardized interfaces; custom or non-compliant contracts often remain invisible without manual intervention.

5. Caching behavior inside MetaMask can delay updates even after correct contract data is entered, requiring a forced refresh or re-import.

Prerequisites for Manual Token Import

1. A verified and active Ethereum-compatible network must be selected in MetaMask—this includes mainnet, testnets, or Layer 2 rollups like Optimism or Base.

2. The exact contract address of the token must be obtained from a trusted source such as Etherscan, Polygonscan, or the project’s official documentation.

3. The token’s decimal precision (e.g., 18 for most stablecoins) must be confirmed via blockchain explorers to avoid balance misrepresentation.

4. Users must ensure their wallet holds a non-zero balance of the token on-chain, as MetaMask only displays balances—not speculative holdings.

5. Browser extension version must be up-to-date; older versions lack support for newer token standards or chain-specific features.

Step-by-Step Manual Import Process

1. Open MetaMask and confirm the correct network is selected using the top-right network dropdown menu.

2. Click the “Assets” tab, then scroll down and select “Import tokens” at the bottom of the asset list.

3. Switch to the “Custom token” tab and paste the verified contract address into the designated field.

4. MetaMask will auto-populate symbol and decimals fields if the contract responds correctly to standard read calls; otherwise, manually enter them.

5. Click “Next”, review the details, then click “Add tokens” to complete the import.

Common Pitfalls During Import

1. Entering a proxy contract address instead of the implementation address—especially common with upgradeable tokens—results in zero balance detection.

2. Using an incorrect network causes the contract to appear valid but display no balance, since the same address may represent different tokens across chains.

3. Copy-paste errors introducing invisible Unicode characters or extra spaces break contract validation silently.

4. Attempting to import native tokens like MATIC or BNB via contract address fails because they are not ERC-style tokens and require network-level recognition.

5. Some tokens use non-standard ABI functions or restrict balance queries, making them incompatible with MetaMask’s balance-fetching logic.

Frequently Asked Questions

Q: Can I import a token without knowing its contract address?A: No. MetaMask requires a valid, on-chain deployed contract address to fetch balance and metadata. Guessing or using placeholder addresses will fail validation.

Q: Why does MetaMask show “Invalid contract address” even when the address is copied from Etherscan?A: This occurs when the address belongs to a non-token contract, is formatted with checksum mismatches, or resides on a network not currently selected in MetaMask.

Q: Does importing a token expose my private key or seed phrase?A: No. Manual import only reads public blockchain data. MetaMask never transmits private keys or recovery phrases during this process.

Q: Will imported tokens appear in MetaMask Mobile?A: Yes—if the same wallet is connected and the same network is active—but users must repeat the import steps on the mobile app, as token lists are not synced across devices.