A Series NFT collection is group of individual NFT artworks, where each artwork and its associated metadata can vary while still being part of the larger collection. In this context, "series" refers to the collective grouping of NFTs, allowing for flexibility in the content and characteristics of each piece. While the artworks within the collection can have their own distinct features, they share a common thread, such as a theme, style, or artistic vision.
To deploy a Series collection, upload a .zip file that contains your series. The .zip file should be 3.5GB or less. It should contain:
- 1.The folder named "images" should hold the artwork for each token. Supported file formats are as follows: Image: PNG, JPG, GIF, WEBP Video: MP4 Audio: MP3
- 2.A .json file named "metadata.json" The metadata.json file should contain an array of objects, where each object represents a token. Each token object should contain the following entries: "metadataId": An integer that identifies this token. Metadata IDs must start at 1 and be sequential. Note that a token with a given metadata ID may have a different token ID when it is minted if you have a random mint mechanic in place (see the price and distribution step for details). "imageRef": The name of the image asset to use for the token (for example: "image-1.png") "animationRef": The name of the animation asset to use for the token (for example: "animation-1.mp4"). This entry is optional and only necessary if you want to use a separate animation asset. "name": The name of the token. This will appear as the token’s name on marketplaces. "description": The description of the token. This will appear as the token’s description on marketplaces, and is distinct from your collection's description (specified in the collection details step). You may add additional entries that specify any custom traits for this token, for example: "Background Color": "Red" "Height": 7.2 "Shiny": false Note: there is a maximum of 100 unique traits. Series data can be reviewed once uploaded.
- 3.Optional: A folder named "animations" (only necessary if your series uses .gif, .mp4, .webm, or .webp files for animations) This folder contains any animation assets used by your tokens. We currently support .gif, .mp4, and .webm files for animations.
Use the following examples to ensure that your files are in the correct formats. If you’re not sure how to create a .json file, you can easily convert a .csv spreadsheet (which you can export from Excel, Google Sheets, etc.) to .json format using this tool.
Please zip by selecting the images folder, animations folder (if relevant), and metadata.json file themselves, not a folder containing them.
After uploading your artwork, preview the tokens to ensure that your artwork and metadata have been uploaded correctly.
Enter the details of your collection in the following steps. Note that you don't have to wait for the artwork to upload to enter in the collection details.
- 1.Set the specific blockchain your collection will run on.
- 2.Name your contract.
- 3.Input your collection name, description, and logo. The logo will appear as the cover image of your collection.
- 4.Toggle for transferability, which makes your collection "soul bound". This means the NFT cannot be traded or exchanged but is instead tied to the collector's wallet address.
- 1.Enter the price of your token. Don't worry, you can change this later from the token management page.
- 2.Enter the mint start and end date. This can also be updated on the token management page.
- 3.Choose your mint style. Collector's choice means the collector can view all the different artwork and pick one to mint. A random mint means that token artwork will be revealed randomly after minting.
- 4.Apply a gate to your collection. This can also be changed post collection deployment so that different collectors can access your mint at different points.
- 5.Input your primary and royalty payout addresses.
- 6.Specify the number of mints per wallet.
Review and deploy your collection once all the details have been set and finalized.