Select the correct network and account in MetaMask, open its token-management or import option, and enter the token's verified contract address. Review the detected details and import it. This adds a display entry for an existing balance; it does not buy, bridge, or recover tokens.
Prove the token exists at your address first
If the token appears missing after a transfer, obtain the hash and network from the sender. Open the record on the correct explorer and identify the recipient, contract, and quantity. A transfer notification by itself does not establish those details.
If the action was a DEX approval, it may have changed permission without delivering another token. Inspect the actual swap or transfer record before trying to solve the problem by adding an asset.
Compare the recipient with the MetaMask account currently selected. A token held by a different account will not appear merely because you import its contract into this one. Also check that the asset is on the selected chain.
If the public record shows no balance, adding a token entry cannot create it. Resolve the missing transfer or incorrect route with the relevant party. If the record shows the expected balance, a custom display entry may be the appropriate next step.
Find the contract without trusting a copied symbol
The contract address identifies a token on a particular network. Start with the issuer's official documentation or verified project channels and compare that information with the explorer record of the transfer you intended.
An explorer or asset listing can help locate the address, but inspect the exact result. Similar names and symbols can be used by unrelated tokens. A logo or familiar ticker is not enough to establish identity.
The same project can have several deployments or token representations. Confirm the network, intended version, and whether the asset is native or bridged where that distinction matters. An address from one chain is not automatically the right contract on another.
Be particularly careful with unsolicited tokens. A sender can create a token with a misleading name or link to attract interaction. You do not need to visit a website advertised by an unexpected asset merely to understand why it appeared.
If someone claims to have sent a token but cannot provide the network, contract, or transaction hash, treat delivery as unverified. Ask for the public evidence rather than supplying your recovery material to an alleged recovery service.
Import the verified entry
- Open MetaMask and select the account that holds the token. Set the network identified by the transfer record.
- Open the token list's management or import control. Current versions may use Manage tokens, a plus button, or an Import tokens flow.
- Search for the asset if supported. If it is not listed, choose the custom-token option and paste the verified contract address.
- Review the detected symbol and decimal information. Compare with reliable asset data if a field is missing or inconsistent; avoid guessing to make the display look correct.
- Continue through the wallet's import confirmation. This operation should correspond to adding token information, not granting another website spending authority.
- Return to the asset list and compare the quantity with the on-chain balance. If needed, refresh the wallet view after confirming the account and network again.
Understand decimals and valuation
A token contract can represent balances using integer units with a decimal setting for human-readable display. An incorrect decimal setting can make the visible quantity look much larger or smaller than expected.
Use authoritative token data rather than copying a generic default. If the wallet detects the information correctly, there is normally no reason to override it. A manual value should be supported by evidence about that exact contract.
A fiat price is a separate display feature. A wallet may show the token quantity without a reliable market valuation, or may use a source different from another app. Missing price data does not by itself mean the balance is missing.
Likewise, a large displayed valuation does not prove there is real liquidity to sell the asset at that price. If the asset is unfamiliar, investigate the market and token controls independently. Token visibility is not a security endorsement.
Keep the contract and quantity as the basis of reconciliation. This lets you diagnose a display issue without turning it into an unsupported conclusion about the asset's economic value.
When the balance still does not appear
Recheck the account and chain before changing anything else. Inspect the same public address on the correct explorer. If the expected transfer used a different account or network, the custom entry is not the underlying issue.
Look for a stale application view or network connection problem. Follow MetaMask's official troubleshooting instructions and preserve the transaction hash. Avoid clearing data or importing the phrase elsewhere merely because a screen has not refreshed.
Some assets or networks require a different supported wallet or interface. Verify the product's current support instead of forcing every asset into an EVM custom-token field. Bitcoin, for example, should not be treated as an arbitrary ERC-20 contract solely to create a display entry.
A smart-contract account or externally connected hardware account can also have different control and display considerations. Identify which account type actually received the funds before following instructions intended for a standard imported software account.
If the balance exists but transactions fail, investigate that as a separate spending issue. Adding the token again does not repair permissions, fee balances, liquidity, or restrictions in its contract.
Remove clutter without confusing it with disposal
Hiding or removing a custom token from the interface generally changes what you see rather than moving the token on-chain. Keep the public record if you need to prove holdings or investigate an unexpected deposit.
Do not send an unwanted token to an arbitrary address just to remove its display. Such a transaction can incur fees and requires interaction with its contract. Hiding a suspicious entry can be an appropriate display-management step while you investigate.
If a website asks for a token approval during a simple display fix, inspect the request independently. A custom entry does not require revealing your seed phrase. Permissions and transactions belong to different tasks.
Once the correct quantity is visible, record the verified contract and network in a nonsecret note if useful. Refresh that information when a project announces a migration rather than assuming an old display entry will represent every future version.
Reader questions
Will importing the same token twice double my balance?
No. The underlying balance is determined by the network. A display entry does not mint or transfer additional units.
Can a token symbol tell me its contract address?
No. Symbols are not unique identifiers. Use verified network-specific information.
Do I need to pay gas merely to display a custom token?
Adding display metadata in the wallet does not itself require executing a token transfer. Inspect any unexpected transaction request before approving it.