The Batch Mint feature on NFT.io allows you to create and mint multiple tokens at once by uploading a Comma-Separated Values (CSV) file. This feature is designed for:

• Advanced creators who have token media and metadata ready and hosted externally, or

• Users who want to mint additional supply for existing tokens.

Note: Batch minting is used to create and mint multiple tokens within an existing collection. It does not create new collections or multiple collections at once.
 

CSV File Structure

To batch create or mint tokens successfully, the CSV file must follow the correct format. Each row represents a single token action (creating or minting), and each column defines a required parameter.

Your CSV file must include the following columns in this specific order:

1. Token ID: A unique identifier for the token, combining the collection ID and token ID, separated by a hyphen. Format: CollectionID-TokenID (for example: 119669-50).

2. Mint Quantity: The number of tokens to mint.

3. Metadata JSON URL: The URL pointing to the token’s metadata file. This defines details such as the token’s name, description, media, attributes, and other metadata properties.

   This field is intended for advanced creators who already have token media and metadata prepared and hosted externally — either in their own servers or in the cloud. The URL must point directly to a valid and publicly accessible JSON file that follows the Metadata Standard.

   To learn more about metadata and how to create or host it dynamically, see:

   • Enjin Documentation – Metadata Standard

   • Enjin Documentation – Dynamic Metadata

4. Recipient Address: The wallet address that will receive the minted tokens.

5. Supply Type: Defines the token's supply type. For details, see: Token supply types

   • INFINITE – No maximum supply; additional tokens can be minted indefinitely. 

   • FIXED – A defined maximum supply that cannot be increased. 

   • COLLAPSING – Supply decreases when tokens are destroyed (melted). 

6. Max Supply: The maximum number of tokens that can ever exist for that token ID. This value cannot be changed once the token is created. This field is not editable if the Supply Type is set to INFINITE.
    

How Batch Minting Works

Based on the Token ID provided in each row, the system automatically determines whether each row in the CSV represents creating a new token, or minting an existing token.
 

Creating New Tokens

If a Token ID in a row does not yet exist in the collection, the system will create a new token using the information provided in that row. For a successful creation, you must fill out all the necessary columns.

Required Columns for Creating a Token:

• Token ID

• Mint Quantity

• Metadata JSON URL

• Recipient Address

• Supply Type

• Max Supply (not editable if Supply Type is INFINITE)
   

Minting Existing Tokens

If a Token ID in a row already exists within the collection, the system will mint additional tokens for that ID. When minting, the system only requires the Mint Quantity and the Recipient Address. Any information in the other columns for that row will be ignored.

Required Columns for Minting a Token:

• Token ID

• Mint Quantity

• Recipient Address

You can perform both creation and minting actions within the same CSV file. The system processes the file row by row. This means you can even create a new token in one row and then, in a subsequent row, mint more of that same token to a different address.
 

Sample CSV File

Below is an example of a properly formatted CSV file to help you get started. (or download the sample file here)

119669-50,1,https://cdn.enjin.io/mint/meta/119669-mystic.json,enBWrZ4htQnWRE4cNonQLRXLozKbnkZPokmkQHjAof4qfqvyN,Fixed,100
119669-51,4,https://cdn.enjin.io/mint/meta/119669-soldier.json,enBWrZ4htQnWRE4cNonQLRXLozKbnkZPokmkQHjAof4qfqvyN,Collapsing,10
119669-52,5,,enBWrZ4htQnWRE4cNonQLRXLozKbnkZPokmkQHjAof4qfqvyN,,
119669-53,10,https://cdn.enjin.io/mint/meta/119669-cyber.json,enBWrZ4htQnWRE4cNonQLRXLozKbnkZPokmkQHjAof4qfqvyN,Infinite,
119669-53,100,,enEVjSTWg6z1X85bwf6KJFjMj4XmvQ8sJPi1FLfnqqzoiWiHe,,

Explanation of the example:

• Row 1 & 2 (Token IDs 50 & 51): These tokens do not exist yet, so they will be created with the specified properties and the initial quantity will be minted to the respective recipient addresses.

• Row 3 (Token ID 52): This token already exists in the collection 119669. The system will mint 5 additional tokens to the recipient address enBWr.... The other columns are left blank as they are ignored.

• Row 4 (Token ID 53): This token does not exist yet. It will be created as an INFINITE supply token, and the first 10 will be minted to the recipient address efBWr....

• Row 5 (Token ID 53): Since token 53 was created in the previous step, this row mints an additional 100 tokens to a different recipient address, enEVj....

The final result would look like so:

Need More Help?

For additional support, visit Enjin Support.