How to Add a Custom Token by Contract Address in MetaMask?

Accessing the Token Import Interface

1. Open MetaMask extension in your browser and unlock your wallet.

2. Click on the “Assets” tab located at the top navigation bar.

3. Scroll down and select “Import tokens” from the bottom of the assets list.

4. Switch to the “Custom token” tab within the import modal window.

5. Ensure your current network matches the blockchain where the token contract resides.

Entering Contract Address and Token Details

1. Paste the full ERC-20 or BEP-20 contract address into the “Token Contract Address” field.

2. Click “Next” to trigger MetaMask’s on-chain verification request.

3. Wait for MetaMask to fetch the token symbol, decimals, and name directly from the smart contract.

4. Confirm that the retrieved symbol matches the expected token identifier—discrepancies may indicate a scam contract.

5. Manually verify the contract source code on Etherscan or BscScan if the token is unfamiliar.

Finalizing Token Addition

1. After successful validation, click “Add Custom Token” to proceed.

2. The token will appear under the “Tokens” section in your Assets view.

3. If the token does not display immediately, refresh the page or toggle between networks.

4. Check your wallet balance—zero balance does not mean failure; it only reflects absence of holdings.

5. **Never confirm a transaction without verifying the contract address on a trusted block explorer.

Common Pitfalls During Token Import

1. Attempting to add tokens on an incompatible network—e.g., adding a BSC token while connected to Ethereum Mainnet.

2. Copying truncated or mistyped contract addresses containing invisible Unicode characters.

3. Ignoring mismatched decimal places that cause incorrect balance display or transfer failures.

4. Adding tokens with no liquidity or inactive contracts—these may show zero value indefinitely.

5. **MetaMask does not validate token legitimacy—users bear full responsibility for contract scrutiny.

Frequently Asked Questions

Q: Why does MetaMask show “Unable to verify this token”?A: This occurs when the contract fails to respond to standard ERC-20 function calls like name(), symbol(), or decimals(), often due to non-compliance or deployment errors.

Q: Can I add a token with a custom RPC network not listed in MetaMask?A: Yes—first configure the custom network via Settings → Networks → Add Network, then switch to it before importing the token contract.

Q: Does importing a token expose my private key or seed phrase?A: No—token import only reads public contract data; no signing or key exposure takes place during this process.

Q: Why is my imported token balance showing as zero despite holding tokens on-chain?A: This usually results from using the wrong network, incorrect contract address, or the token using a non-standard interface such as ERC-677 or custom mint logic.