NFT metadata, explained locally

A local item record includes a name, the collection description, an image reference, and an attributes array. An optional external_url can be configured when your project needs one. Attributes use trait types and values drawn from the selected groups.

Images are referenced locally as ../images/<number>.png in the exported metadata layout. Numbering follows the configured starting number, so the item name and image reference stay aligned.

• None is a virtual attribute for an optional group; it does not require a missing PNG file.
• Exposed palette or color variants can appear as an attribute when the asset configuration allows it.
• Hidden metadata traits can remain visible in the composition while being omitted from metadata according to the project setting.
• Collection-level files summarize the same run and should be treated as part of the verified package.

collection.json describes the collection-level metadata. traits-summary.json summarizes realized trait counts. generation-manifest.json records the generation and export contract, including the settings and source identities needed to verify the result.

The Generator verifies the package locally before enabling the final download. That check is about semantic consistency, not a promise that a marketplace will accept the files.

The Generator creates local artwork and metadata. It does not mint NFTs, upload files to IPFS, create CIDs, deploy contracts, or automatically create token URIs. If you later publish a collection, you remain responsible for choosing a storage, contract, and marketplace workflow.