How to View Solana NFT Metadata in Phantom Wallet

Accessing NFT Metadata Directly in Phantom Interface

1. Open the Phantom wallet extension or mobile application and ensure you are connected to the Solana network.

2. Navigate to the NFTs tab located at the bottom of the mobile app or in the sidebar of the browser extension.

3. Tap or click on any individual NFT card displayed in your collection list.

4. The full asset view loads, showing visual representation, name, collection name, and ownership details.

5. Scroll downward until the Details section appears — this contains core metadata fields such as description, attributes, external URL, and creator information.

Understanding Embedded Metadata Fields

1. Phantom renders metadata according to the Metaplex standard used across Solana NFTs, including name, symbol, and uri — a pointer to a JSON file hosted off-chain.

2. The attributes array displays trait types and values, commonly used for rarity scoring and filtering in marketplaces.

3. The seller_fee_basis_points field indicates royalty percentages enforced by creators during secondary sales.

4. Phantom does not parse or display custom keys outside the Metaplex schema unless explicitly included in the base JSON structure.

5. Timestamps like created_at or updated_at may appear if the mint’s metadata includes them, but Phantom does not inject or modify these values.

Verifying On-Chain Integrity of Metadata

1. Phantom does not alter or cache metadata locally — it fetches the URI from the on-chain mint account and retrieves the JSON payload via HTTP GET request.

2. If the URI points to an IPFS hash, Phantom resolves it using its built-in gateway or falls back to public gateways like ipfs.io or dweb.link.

3. Any mismatch between on-chain mint authority and the domain hosting the JSON triggers no warning — users must manually verify signature authenticity using third-party tools.

4. Phantom displays a lock icon next to verified collections only when the collection’s update authority matches a known verified program address registered with Metaplex.

5. No cryptographic signature verification occurs inside the wallet interface; all validation remains user-initiated and external.

Limitations When Viewing Metadata

1. Phantom does not support rendering nested or hierarchical metadata structures beyond flat key-value pairs defined in the base Metaplex spec.

2. Animated or interactive assets referenced in the animation_url field play only if the media format is natively supported by the device’s OS — MP4, GIF, and PNG work reliably; GLB or HTML-based assets often fail silently.

3. Phantom truncates long descriptions after approximately 200 characters in the preview pane, requiring manual expansion via “See more” toggle.

4. Localization fields like name_localized or description_localized are ignored entirely — only default language entries render.

5. Phantom omits metadata fields that exceed 1MB in total JSON size, displaying an error message instead of partial data.

Frequently Asked Questions

Q: Can Phantom display metadata for compressed NFTs (cNFTs)?A: Yes — Phantom supports cNFT metadata retrieval through Bubblegum program integration, but only displays fields available in the leaf node’s asset manifest, not full tree-level aggregations.

Q: Why does my NFT show “No description” even though the JSON contains one?A: Phantom enforces strict MIME-type validation; if the server returns text/plain instead of application/json for the metadata URI, parsing fails and fallback text appears.

Q: Does Phantom store metadata locally after first load?A: No — every metadata view initiates a fresh HTTP or IPFS request; no caching layer exists within the wallet runtime environment.

Q: Can I edit NFT metadata directly from Phantom?A: No — Phantom provides read-only access to metadata; editing requires signing a transaction via CLI tools like Metaboss or Solana CLI with appropriate update authority.