Tokens & Standards — ERC-20, BEP-20, adding custom tokens

Quick answer: what tokens does MetaMask support?

MetaMask supports tokens that live on EVM-compatible networks. Short version: ERC-20 (Ethereum), BEP-20 (BSC), and other EVM token standards are usable in MetaMask when you connect to that chain. It does not natively hold non-EVM native coins like XRP Ledger or Stellar — unless you’re dealing with a wrapped token that exists on an EVM chain.

What tokens are supported by metamask? Any token that follows the token standard of an EVM-compatible chain and has a contract address you can add. Which tokens does metamask support in practice? ERC-20, ERC-721, ERC-1155, BEP-20 and equivalents on chains you add as custom networks.

I’ve been using MetaMask daily for swaps and token management across Ethereum, Polygon and BSC (via custom RPC). It works, but you have to be precise about networks and contract addresses.

Supported token standards and chains (quick reference)

Token standard	Type	Typical chains	MetaMask handling
ERC-20	Fungible token	Ethereum, any EVM-compatible chain	Add by contract; shows balance on that network
BEP-20	Fungible token	Binance Smart Chain (BSC)	Same UX as ERC-20 after switching network (/add-bsc)
ERC-721	Non-fungible token (NFT)	Ethereum, Polygon, others	Visible in NFT tab or token list; requires token metadata
ERC-1155	Semi-fungible NFT standard	Ethereum & EVM chains	Supported where metadata is available

(placeholder image: screenshot of "Add Custom Token" flow)

If you want to add BSC, Polygon or Avalanche you may need to add the network first (how to add BSC, how to add Polygon, add-avalanche).

What is my ERC-20 / BEP-20 wallet address in MetaMask?

Short answer: your MetaMask account address (the 0x... address) is your ERC-20 wallet address. It's also your BEP-20 address — the same 0x address is used across EVM chains.

How to copy it (extension):

Open the MetaMask extension and make sure you're on the account you want.
Click the account name (or the address) to copy the 0x address.
Paste into the exchange or app where you’re withdrawing tokens.

Mobile steps are similar; see setup-mobile for screenshots. And double-check you’re on the correct network before you send funds.

If someone asks "what is my tether bep20 wallet address metamask" or "where is your udsc wallet address metamask" (typos aside) — the answer is the same: use your account's 0x address, and make sure the receiving chain expects BEP-20 (BSC) or ERC-20 (Ethereum) tokens. Sending tokens to the wrong chain can make them hard to recover.

Step-by-step: how to add a custom token

Want to add an uncommon token? Follow these concrete steps.

Switch MetaMask to the chain where the token lives (Ethereum mainnet for ERC-20, BSC for BEP-20, etc.). See networks-multi-chain.
Open MetaMask and click "Import tokens" (extension) or "Add token" (mobile).
Choose "Custom token" and paste the token contract address.
Token symbol and decimals will usually auto-fill. Verify them.
Click "Add". Token should appear in your asset list.

For step-by-step visuals see the how-to guide: how-to-import-token.

Important verification steps (do these every time):

Confirm the contract address on the chain’s block explorer (Etherscan, BscScan, Polygonscan). Do not copy addresses from random social posts.
Check the token’s official site or verified token list. If in doubt, don’t add it.

And if you can’t find a contract address: stop. Scams often surface as fake tokens.

Wrapped tokens and non-EVM coins (XRP, XLM, ZIL, XDC, XRC20)

MetaMask does not natively support native chains that are not EVM-compatible (for example: XRP Ledger, Stellar, Zilliqa). That means "xrp metamask support" is technically "not natively supported." What you can do is hold a wrapped version of those coins that exists as an ERC-20 or BEP-20 token on an EVM chain. But wrapped tokens introduce bridging risk.

What about XDC or XRC20? Some chains are EVM-compatible and will work if you add the right custom RPC — but don’t assume compatibility. Verify whether the chain supports EVM and then add via add-custom-network or networks-multi-chain.

Looking for "xrp metamask contract address" or "xrp wallet metamask"? You’ll only find contract addresses for wrapped XRP tokens on EVM chains. Native ledger addresses (XRP Ledger) are different and not compatible.

Token standards explained (short)

ERC-20 / BEP-20: fungible tokens (coins, stablecoins, most tokens you swap). Good for balances and DeFi.
ERC-721: single-instance NFTs (digital art, collectibles).
ERC-1155: batched NFTs (game assets, semi-fungible items).

These standards matter because MetaMask shows tokens by reading the chain via RPC and the token contract. If the contract implements the standard correctly, balances will display. If not, you may need to add the token manually.

Security: common token mistakes and how to avoid them

Mistake: sending a token to the wrong chain address. I did this once on testnet — painful but recoverable. Real funds are harder to get back.

Mistake: adding a token and immediately approving unlimited allowances. Don’t approve infinite allowances unless you understand the contract. Use revoke tools (see revoke-approvals).

Mistake: trusting an unverified token contract. Always verify on the chain’s official block explorer and the token’s official channels.

Quick safety checklist:

Verify contract on explorer before adding.
Switch to the correct network first.
Use small test transfers before moving large amounts.
Keep your seed phrase and private keys offline and encrypted. See backup-and-recovery-options.

But be practical: hot wallets are for active use. I keep trading funds in a hot wallet and larger holdings offline.

Troubleshooting: token balance not showing?

Confirm you’re on the right network. If you sent a BEP-20 token but are on Ethereum mainnet, MetaMask won’t show it.
If the token is new, add it with the correct contract address (see how-to-import-token).
If balance exists on-chain but not in MetaMask, checking the explorer can prove the token exists (and help support recoveries). See not-showing-balance.

FAQ — quick answers to common searches

Q: Is it safe to keep crypto in a hot wallet? A: Hot wallets are convenient and non-custodial, but they expose private keys to devices that can be compromised. Store only what you need for daily activity and use cold storage for long-term holdings.

Q: How do I revoke token approvals? A: Use MetaMask’s built-in token approval UI or a trusted approval-revocation tool. Check revoke-approvals for a step-by-step.

Q: What happens if I lose my phone? A: If you have your seed phrase, you can restore the wallet on another device. (If you used cloud backups, understand their trade-offs.) See backup-and-recovery-options.

Q: Does MetaMask support XRP/XLM/ZIL? A: Not natively. Only wrapped variants on EVM chains are supported. If you see a contract address for a wrapped token, verify it before adding.

Q: What about specific token contract addresses (BTT, XDC)? A: I won’t paste contract addresses here — they change and wrong addresses cost money. Instead, verify each token’s contract on the appropriate block explorer and official project channels.

Conclusion & next steps

MetaMask will hold any token that follows an EVM token standard on a chain you connect to. That includes ERC-20 and BEP-20 tokens — but not native non-EVM coins unless they’re wrapped. Be methodical: switch networks, verify contract addresses, and test with small transfers.

Ready to add a token? Start with the step-by-step guide: how-to-import-token, and manage your tokens from token-management.