NFT metadata URI vs contract address
An NFT contract address identifies the ledger. A metadata URI locates descriptive data; a media URI inside that data points to artwork or other content.
Worked example
| Layer | Illustrative value | Purpose |
|---|---|---|
| Ledger | Chain + contract + ID | Token identity and on-chain state |
| Metadata | ipfs://CID/42.json | Placeholder URI for JSON |
| Media | image field in JSON | Referenced content |
Follow the references carefully
For ERC-721 metadata, tokenURI can return the metadata location for a token. The JSON can contain name, description and image fields. A thumbnail copied from a marketplace is not a replacement for the on-chain identity tuple.
Storage choices affect retrieval
An HTTP URL can depend on a server. An IPFS CID identifies content, while a gateway is one way to retrieve it. Availability, mutability and contract upgrade behavior require collection-specific review; “NFT” alone does not guarantee permanent accessible media.
Common pitfalls
- CID is a placeholder label here, not an actual IPFS identifier.
- Matching artwork does not establish that two contracts are the same collection.
Related references
Primary sources
Examples explain identifiers. They are not investment recommendations.