How to Fix imToken Displaying UNKNOWN for a Token

When you open your imToken wallet to check your portfolio and spot the dreaded "UNKNOWN" label next to a token you recently swapped, airdropped, or transferred, it’s natural to feel a flicker of concern—after all, clear asset visibility is one of the core reasons people use self-custody wallets. This issue is far more common than most users realize, and it almost never signals a loss of funds or a security breach; instead, it almost always stems from gaps in token metadata, wallet configuration settings, or network sync issues that are simple to resolve with a step-by-step troubleshooting approach. Whether you’re dealing with a newly launched low-cap token, a cross-chain bridged asset, or a well-established coin that suddenly lost its label, working through targeted fixes will usually restore the token’s name, logo, and balance details in minutes, without requiring you to move your funds or compromise your private keys.

The first and most frequent cause of an "UNKNOWN" token label is that the token has not been added to imToken’s official token list, a curated database that the wallet pulls metadata from to display asset information automatically. imToken relies on this list to show token names, logos, decimals, and contract details for popular assets, but newer, niche, or community-launched tokens often take time to be added, or may never be listed if they have low trading volume or limited user adoption. To fix this, you can manually add the token’s details to your wallet by locating its official contract address from a trusted source—such as the project’s verified website, official social media channels, or a reputable block explorer like Etherscan for Ethereum, BscScan for BNB Chain, or Polygonscan for Polygon. Once you have the correct contract address, open imToken, navigate to the wallet home page, tap the “+” icon in the top right corner to access the token management menu, select “Add Custom Token,” choose the correct blockchain network the token operates on, paste the contract address into the designated field, and fill in the token’s name, symbol, and decimal places exactly as they appear on the block explorer or official project documentation. Double-check every detail, as even a single wrong digit in the contract address or a mismatched decimal count can result in incorrect balance displays or a persistent "UNKNOWN" label. After saving the custom token, return to your wallet home page and refresh the asset list by pulling down on the screen; the token should now display its correct name and balance instead of the generic label.

If manually adding the token does not resolve the issue, the next likely culprit is an outdated imToken app version or corrupted local cache that is preventing the wallet from loading or syncing token metadata properly. imToken regularly releases updates that expand the official token list, fix sync bugs, and improve compatibility with new blockchain networks and token standards, so running an older version of the app can lead to missing metadata for even widely used tokens. Start by checking your device’s app store—Apple App Store for iOS users, Google Play Store or the official imToken website for Android users—to see if a newer version of the wallet is available, and install any pending updates before reopening the app to check the token label. If the app is already up to date, try clearing the app’s cache to remove any corrupted temporary data that might be interfering with metadata loading. For Android users, you can clear cache by going to your device’s Settings, selecting Apps, finding imToken in the list of installed applications, tapping Storage, and selecting “Clear Cache” (be careful not to select “Clear Data,” as this will remove your wallet information and require you to reimport it with your seed phrase). For iOS users, offloading the app and reinstalling it will achieve the same effect without deleting your wallet data, as iOS preserves core app data during the offload process. After clearing the cache or reinstalling the app, log back into your wallet and sync your asset list to see if the "UNKNOWN" label has been replaced with the correct token details.

Another often overlooked cause of "UNKNOWN" token displays is incorrect network selection or a failed network sync, especially if you are dealing with tokens on less common layer-2 networks, cross-chain bridged tokens, or assets on alternative layer-1 blockchains. imToken supports hundreds of blockchain networks, but if you are viewing the wrong network tab in your wallet, a token that exists on, say, Arbitrum One will not be recognized if you are browsing your Ethereum mainnet asset list, and it may show up as an unknown asset if it was accidentally added to the wrong network profile. To rule this out, first confirm which network the token is deployed on by cross-referencing the contract address with a block explorer, then make sure you have selected the matching network in imToken’s network switcher menu at the top of the wallet home page. If the correct network is already selected, try refreshing the network connection by switching to a different network and then switching back, or by toggling your device’s Wi-Fi or mobile data off and on to reset the wallet’s connection to blockchain nodes. In some cases, imToken’s default public nodes for a specific network may be slow or experiencing downtime, which can prevent the wallet from fetching token metadata and balance information; you can fix this by adding a custom RPC node for the network from a trusted provider like Alchemy, Infura, or Ankr. To add a custom RPC, go to imToken’s Settings menu, select “Networks,” find the network you are using, tap “Edit,” and replace the default RPC URL with a custom endpoint from your preferred provider. Save the settings and return to your wallet to resync the asset list, which should resolve sync-related "UNKNOWN" label issues.

For users who have received tokens via airdrop, cross-chain bridge, or decentralized exchange swap, the "UNKNOWN" label may also be tied to the token’s compliance with token standards like ERC-20, BEP-20, or ERC-721 for NFTs. Some poorly coded tokens may have missing or malformed metadata fields in their smart contract code, which makes it impossible for wallets like imToken to automatically pull name and logo information even if the token is added manually. In these cases, you can still use custom token settings