NFT import errors: personal address detected
A “personal address” import error commonly means the contract field contains a wallet address or an address without the expected contract on the selected network. Verify the role and network before trying again.
Worked example
| Symptom | Possible cause | Check |
|---|---|---|
| Personal address detected | Owner address copied | Use collection contract |
| Contract not found | Wrong network or unsupported contract | Select correct chain and inspect code |
| Token not found | Wrong ID or different variant | Read item details |
| Unsupported NFT | Wallet support limitation | Read wallet’s current documentation |
Work from the item backwards
Find the item on the correct explorer, read the contract and token ID, then compare them with the wallet’s import fields. The owning wallet address can be perfectly valid EVM syntax while still being the wrong value for the contract field.
Importing changes display
Importing an NFT normally helps the wallet display an already owned asset; it does not create ownership or move it between chains. A legacy collection or ERC-1155 asset may require different wallet support from a standard ERC-721 token.
Common pitfalls
- Do not pay a fee to “activate” a public lookup.
- If import still fails, verify current wallet support; do not assume the token is missing.
Related references
Primary sources
- MetaMask NFT documentation
- Etherscan contract page guidance
- ERC-721 specification
- ERC-1155 specification
Examples explain identifiers. They are not investment recommendations.