Prepare component metadata
Token metadata describes one NFT, usually its name, image and attributes. Collection metadata describes the whole collection. Neither is the CAM manifest that defines the app's workflow.
Check the collection's base URI first
The generic registration/editing workflow supplies a complete metadata URI. It expects an empty collection base URI. The current token contract concatenates a nonempty base with the stored token URI; it does not exempt full URLs or data URIs.
For an older collection with a nonempty base, do not paste its resolved tokenURI back into the full-URI editor: that can duplicate the prefix. Use a compatible suffix-aware client or plan a deliberate collection configuration change. Changing the shared base affects existing tokens, not just the one being edited.
Choose a metadata input
Use JSON URL for a complete hosted metadata URL, or Embed JSON for a document encoded directly into the token URI. The active editor supplies the transaction value; there is no separate apply step. Invalid or empty active input cannot prepare a metadata transaction.
For a hosted JSON document, relative image references resolve from its location. When copying it into an embedded document, replace relative image references with complete URLs or embedded images. The editor preserves attributes and extension fields; use Advanced JSON to inspect the whole document before approving.
The editor does not upload a file or image. Host content separately when using URLs. Metadata and its URI are public; do not include private identity or contact information merely because the browser displays an editable field.
Preview, then verify the write
Load preview reads the JSON and image from the resolved token URI. It does not change metadata. Embedded images need no network request; HTTP(S) and IPFS reads use browser access, Download scope and the selected IPFS gateway. Remote servers must permit CORS.
Current preview limits are 256 KiB for JSON and 4 MiB for PNG, JPEG, WebP or GIF images. A successful preview does not establish physical authenticity, and a broken image does not prove that token creation failed.
As the owner or a metadata-authorized workshop, choose Update NFT details, review the actual URI and target, then authorize. After the receipt, refresh and load the preview again. Check both the contract's resolved URI and displayed content.
Local practice
The demo serves metadata under cam/components/. Use an unused serial and make its metadata attributes agree with it. The supplied demo-bike-001.json uses a relative image filename; convert that image reference when embedding the JSON.
Source: base and collection metadata, resolved token URI, and editor and fixture inputs. Continue with registration or owner and workshop tasks.