Quick overview
This guide explains how to view, send, hide spam, and connect to marketplaces from the mobile software wallet commonly used on phones. I write from hands-on testing on both iPhone and Android, including troubleshooting OpenSea connect issues and cleaning up unwanted NFT airdrops. Expect step-by-step instructions and concrete tips (not just generic warnings). And yes, the spam NFTs can pile up quickly — I know.
How the wallet stores and displays NFTs
The wallet stores private keys locally on your device and reads NFTs from the blockchain metadata that the token contract exposes. Most wallets display common NFT standards: ERC-721 and ERC-1155 on EVM-compatible networks, and certain non-EVM collections when their metadata endpoints are supported. Images and traits are usually loaded from IPFS or public HTTP endpoints, so if a collection’s metadata is offline the NFT may show as blank.
What I've found in testing: missing images are almost always a metadata or RPC issue, not a missing token. You still own the token; the app just can’t fetch the artwork.
If you don’t see an NFT you own, confirm ownership on a block explorer and then try the tips in token-management or the nft-support page.
Step-by-step: View NFTs in Trust Wallet (mobile)
- Open the mobile app and select the account that holds the NFT.
- Make sure you’re on the correct blockchain network (Ethereum, Polygon, etc.). A mismatch hides NFTs.
- Tap the NFTs / Collectibles tab (label depends on app version). If the tab isn’t visible, open Settings and enable NFT/collectibles view.
- Pull to refresh. If artwork doesn’t load, switch from the default RPC to a public RPC or toggle cellular/Wi‑Fi.
- If an NFT still doesn’t appear, copy the contract address and token ID then check on a blockchain explorer.
Screenshot example (placeholder):
Alt: screenshot of NFT list in wallet showing three items and collection names.
Send NFTs: Step-by-step and common mistakes
Step-by-step send
- Select the NFT you want to send.
- Tap Send. Enter the recipient address (or scan a QR code).
- Confirm the network and gas fee. The wallet will show estimated gas fees for the transfer.
- Review the token ID and contract address on the confirmation screen. Approve the transaction.
- Wait for the transaction to confirm on-chain.
Common mistakes and how I handled them
- Sending to an exchange deposit address that doesn't support NFTs. Don’t do this. Ask the exchange first.
- Sending on the wrong network (e.g., ERC‑721 sent to an incompatible chain). Transactions are final. I once paid a refund in time and gas to recover tokens — but recovery isn’t guaranteed.
- Auto-approving a marketplace contract without checking setApprovalForAll permissions. That can give broad transfer rights; see the next section on revoking approvals and token-approvals-revoke.
Always double-check the recipient and the active network. Short sentence. Safer.
Hide spam NFTs — practical methods
Spam NFT airdrops are common. Here are realistic ways to reduce clutter:
- Use the wallet’s built-in hide/ignore feature if present (tap the NFT > menu > Hide). This removes the collection from the visible list but doesn’t change on‑chain ownership.
- Maintain a curated watchlist. Only star or pin collections you care about and toggle off others in the app settings.
- Revoke marketplace approvals for unknown contracts (see token-approvals-revoke). That prevents marketplaces from moving your assets even if a spam NFT appears.
- Use a separate receive address for public interactions (marketplace bids, giveaways) so your primary address stays clean.
But if your app version lacks a hide option, third-party portfolio tools can filter what you display. I believe separating wallets is the most reliable method.
Connecting to NFT marketplaces (OpenSea issues & fixes)
Two common connection paths exist: the wallet's in-app DApp browser or WalletConnect. Which one you use depends on your phone and the marketplace.
Comparison table: viewing and marketplace connection
| Feature |
In-app Browser (mobile) |
WalletConnect (QR/link) |
| View NFTs inside app |
Yes |
Depends on third-party site |
| Connect to marketplace |
Direct (if supported) |
Universal (works with many sites) |
| Works on iPhone? |
Sometimes restricted by App Store |
Yes (recommended) |
| Best when |
You want an integrated flow |
Browser or desktop interaction |
Common issue: "opensea not connecting to trust wallet" or "opensea trust wallet connect iphone". If OpenSea won’t connect on iPhone, try WalletConnect instead of the in-app browser. Open OpenSea → Connect Wallet → WalletConnect → choose the mobile wallet when the QR/link appears. See troubleshooting tips at opensea-issues and how to enable DApp browser on your device at /enable-dapp-browser-iphone or /enable-dapp-browser-android.
If the connection drops, clear the app cache, update the app, and retry. I removed a stale WalletConnect session once and the connection stabilized immediately.
Security checklist: approvals, phishing & backups
- Approvals: When a marketplace asks for setApprovalForAll, it can manage all tokens from that contract. Approve carefully. Revoke suspicious approvals via token-approvals-revoke.
- Phishing: Never sign transactions you don’t understand. Check the destination contract address and the action text (transfer vs approval). See phishing-and-fake-apps.
- Backup: Record your seed phrase offline and never share it. Cloud backup of seeds is convenient but raises risk. See backup-recovery-seed-phrase for secure methods.
Short practical rule: if a transaction asks for an approval and you didn’t start a sale/listing, pause and investigate.
Who this wallet is best for — and who should look elsewhere
Who this is for:
- Mobile-first collectors who want a straightforward NFT viewer and simple send/list flows.
- Users who prefer a non-custodial mobile experience and occasional marketplace interactions.
Who should look elsewhere:
- Heavy NFT traders who need built-in advanced marketplace tools or desktop-first workflows.
- Users who want account abstraction features (gasless txs, session keys) — those are typically provided by smart-contract wallets, not standard hot wallets.
If you rely on NFTs with high value, use a hardware wallet or a multi-sig setup for cold storage.
FAQ
Q: Is it safe to keep NFTs in a hot wallet?
A: Hot wallets are convenient but carry more risk than cold storage. For everyday use it's fine. For high-value collections, secure the seed phrase and consider a hardware wallet or custodial solution.
Q: Why is OpenSea not connecting to Trust Wallet on my iPhone?
A: iOS restrictions can block in-app DApp browsers. Use WalletConnect or follow steps on /enable-dapp-browser-iphone. Also confirm the wallet app is up to date.
Q: How do I hide spam NFTs in Trust Wallet?
A: Use the hide/ignore feature if present, use separate addresses for public interactions, and revoke approvals for unknown contracts. See token-management.
Q: How do I revoke token approvals?
A: Use the in-app revoke tool if available, or use a reputable on-chain approval manager linked with WalletConnect. See /token-approvals-revoke.
Q: What happens if I lose my phone?
A: Restore your wallet using the seed phrase on a new device. Follow the secure restore steps in backup-recovery-seed-phrase and lost-device-recovery.
Wrap-up and next steps
Managing NFTs in a mobile software wallet is mostly straightforward: verify the network, confirm recipient addresses, and keep approvals under control. If OpenSea is not connecting to Trust Wallet on iPhone, try WalletConnect and check the guide at opensea-issues. For more about token visibility and custom tokens, see token-management and the broader nft-support guide.
If you want a step-by-step troubleshooting email or a checklist to carry when listing or sending an NFT, check support-contact for contact options. But don’t rush approvals — take a breath and double-check each screen.
