NFT metadata is information associated with a non-fungible token, such as a name, description, or reference to media. It is distinct from the token’s blockchain record and from any referenced media file. What metadata contains and how it is retrieved depend on the implementation, so a reference alone does not establish what a particular NFT contains or whether its information will remain available.
What NFT metadata is
Metadata is descriptive information associated with something else. In an NFT context, it may identify or describe a token, provide attributes, or point to related content. It does not necessarily contain that content itself.
The exact fields and format are not universal. ERC-721, for example, allows an optional metadata interface through which a token ID can be associated with a URI; the referenced JSON may contain a name, description, and image URI. This is a possible arrangement, not a requirement that every NFT use the same structure. Other implementations may expose different information or use different retrieval methods.
Applications can retrieve metadata and display it in a human-readable form. That display is not the token record: it is a presentation of information associated with the token. To understand what a display represents, separate the blockchain record, the metadata document, and any media referenced by that document.
How token data, metadata, and media differ
These three elements serve different roles:
- Token data is the blockchain record associated with a token and its contract context. For an ERC-721 token, the combination of the smart-contract address and token ID uniquely identifies it within an Ethereum chain. A token ID alone is not a global identifier.
- Metadata is information associated with the token. It may provide descriptive fields or references that an application can retrieve and present.
- Media is the content itself, such as an image or other file. A metadata document may point to media rather than include the full file.
The relationship is not necessarily a single bundled object. A token record can be on the blockchain while its metadata is retrieved from another location, and that metadata can in turn refer to a separate media file. The particular storage and retrieval path must be checked for the specific implementation; the token’s name or displayed artwork does not reveal it by itself.
What metadata can contain
Possible metadata includes a name, description, attributes or traits, an image or other media reference, and external links. These are examples, not fields that every NFT is required to contain. Even where a familiar format or field is used, its meaning can depend on the project and implementation.
Attribute labels and values should be read in their documented context. A label such as “type” or “edition” does not acquire a universal meaning merely because the same word appears in another project’s metadata. If the project’s documentation does not explain a field, its intended interpretation may remain unclear.
Metadata also has limits as evidence. A description or attribute is information supplied in association with a token; the field alone does not verify that its contents are accurate or that referenced media is authentic. Likewise, the presence of a link does not establish that the linked file will remain available.
A token record should also not be treated as a complete statement about rights in a linked work or asset. The technical record, any referenced file, and any associated access benefit or license are distinct matters. A metadata field or token label does not by itself determine legal enforceability or the scope of rights. This article describes the technical relationship, not the rights attached to a particular NFT.
How to check where metadata and media come from
For a particular token, use a bounded verification process:
- Identify the token. Record its blockchain, contract address, and token identifier. For ERC-721 on Ethereum, the contract address and token ID together identify the token; do not rely on a collection name or image alone.
- Check the applicable interface. Consult documentation for the token standard and the specific implementation to learn whether and how it exposes metadata. Do not assume that every token uses an ERC-721-style URI or returns the same fields.
- Inspect the reference and response. Determine what the reference returns. If it identifies a metadata document, check whether that document contains descriptive fields, points to media, or does both. Note when the media is reached through a separate reference.
- Establish the storage path. Check whether the relevant information is embedded or stored on-chain, or retrieved from an external location or content-addressed network. A URL or an application display alone may not establish the underlying storage arrangement.
- Compare with documentation. Compare the returned fields and referenced content with the project’s stated documentation. Mark details as unverified when the implementation or available records do not establish them.
This process distinguishes what a token interface exposes from what a project says its fields mean. It also avoids treating a successful retrieval at one moment as proof of permanent storage or continuing access.
Retrieval, changes, and reliability limits
If metadata or media is fetched from an external location, the application’s ability to retrieve it depends on that location and the references involved. A broken reference, service change, or mutable metadata can affect the information retrieved or displayed. The effect depends on the specific implementation; a generic description cannot establish whether a particular NFT’s metadata can change or will continue to resolve.
A content-addressed reference is not a guarantee that content will remain available. It may help identify referenced content, but that alone does not establish that someone will continue to retain or serve it. Similarly, finding an image reference does not by itself show whether the file is stored on-chain, externally hosted, or maintained through another arrangement.
For a named NFT, claims about storage design, mutability, permanence, security, or recovery require implementation-specific evidence. If documentation or inspectable records do not answer those questions, treat the details as unknown rather than infer them from a displayed image or metadata link. The essential distinction remains: the token is a blockchain record, metadata describes or points to associated information, and media is the referenced content when one is provided.