How to add a custom token to MetaMask manually?

Accessing the MetaMask Interface

1. Open the MetaMask browser extension or mobile application.

2. Ensure your wallet is unlocked and you are on the correct network where the token resides.

3. Click the menu icon in the top-right corner and select “Add Token”.

4. Choose the “Custom Token” tab instead of “Popular Tokens” or “Import Token”.

5. Confirm that the network displayed matches the token’s deployment chain — mismatched networks will prevent recognition.

Entering Contract Address Details

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

2. Wait for MetaMask to auto-populate the token symbol and decimals; if it fails, verify the address is correct and deployed on the selected chain.

3. Manually enter the token symbol if auto-detection does not occur — ensure capitalization matches official documentation.

4. Input the correct number of decimals; common values are 18 for most utility tokens, but some stablecoins use 6 or 8.

5. Double-check all fields before proceeding — incorrect decimals may display balances inaccurately without triggering errors.

Finalizing Token Addition

1. Click “Next” after verifying all details are accurate.

2. Review the summary screen showing name, symbol, decimals, and contract address — any discrepancy here indicates a potential scam token or misconfigured deployment.

3. Click “Add Tokens” to confirm and save the custom token to your asset list.

4. The token should now appear under your assets with zero balance if no tokens have been received yet.

5. Never add tokens from unverified sources — always cross-reference contract addresses on Etherscan, TaikoScan, or official project channels.

Verifying Token Authenticity

1. Navigate to the blockchain explorer corresponding to your network — for Ethereum mainnet, use etherscan.io; for Taiko Katla testnet, use katla.taiko.xyz/explorer.

2. Paste the contract address into the search bar and confirm it is verified, has transaction history, and matches the project’s official announcement.

3. Check the “Read Contract” tab to verify standard functions like totalSupply(), name(), and symbol() return expected values.

4. Look for audit reports linked in the contract’s README or project website — absence does not guarantee insecurity but warrants caution.

5. Tokens with no code verification, low holder count, or suspicious transfer restrictions are high-risk and should be avoided.

Troubleshooting Common Failures

1. If MetaMask displays “Invalid address”, re-copy the contract address — invisible Unicode characters or trailing spaces often cause this.

2. If balance remains zero despite confirmed transfers, confirm the token was sent to your exact wallet address on the correct network.

3. If the token appears but shows “Unknown” as name, the contract may lack standard interface implementation or have incomplete ABI exposure.

4. If “Add Token” button remains disabled, check whether decimals field contains non-numeric input or exceeds 36 digits.

5. If the token disappears after wallet restart, ensure the network was active during addition — inactive networks do not retain custom tokens in session memory.

Frequently Asked Questions

Q: Can I add a BEP-20 token to MetaMask while connected to Ethereum Mainnet?A: No. MetaMask must be connected to the BNB Smart Chain network to recognize and interact with BEP-20 tokens. Switch networks first using the network selector.

Q: Why does MetaMask show “Unverified” next to my custom token?A: This label appears when the token contract source code is not verified on the associated blockchain explorer. It does not indicate malicious intent but signals reduced transparency.

Q: Is it safe to add a token whose contract has no external audit report?A: Safety cannot be guaranteed. Unaudited contracts carry risks including minting control, freeze functions, or hidden transfer taxes. Always test with minimal value first.

Q: What happens if I paste the wrong contract address?A: MetaMask will either reject it as invalid or add a non-functional entry. In rare cases, it may point to an unrelated deployed contract — leading to loss of funds if used for transfers.