Upload ZIP format

Each NFT needs one image and one JSON metadata file with the same base name.

Folder structure

collection.zip
├── images/
│   ├── 1.png
│   ├── 2.png
│   └── 3.png
└── metadata/
    ├── 1.json
    ├── 2.json
    └── 3.json

The numeric filenames determine token order. Do not skip or duplicate numbers.

Metadata example

{
  "name": "Hood #1",
  "description": "Part of the Hood collection.",
  "attributes": [
    {
      "trait_type": "Background",
      "value": "Lime"
    }
  ]
}

The image URI is assigned during upload, so it does not need to be included in the input JSON.

Before a large upload

• Validate a small sample first.
• Keep the original ZIP until the edition is deployed.
• Use unique numeric filenames beginning at 1 for each new edition.
• Keep every individual image within the upload limit shown in Launchpad.
• Do not rename or modify the ZIP while an upload is paused.

Download the sample ZIP

Resume behavior

Completed batches are checkpointed after storage verification. If you refresh:

1. Return to the same draft.
2. Select the original ZIP.
3. Confirm that the displayed total and secured count are correct.
4. Resume the remaining items.