8min

Step 3 - Prepare collection artifacts

Once you have edited the 00000.nfts.csv file, it is time to generate all the necessary artifacts on your machine. The generated artifacts are optimized versions of your artworks (beside the original), a meta data and a "record" file per NFT.

To run the commit command you need to be inside your collection folder.

All files are prefixed with a 5-digit incremental number. Files starting with 00000 are auxiliary files, like collection information, progress and log files. By using this pattern, the files can be sorted correctly in File Explorers.

Requires no PIN

Costs: Nothing

Allows Trial Run

Alias: prepare

Shell
|

This command reads the data from the previously edited 00000.nfts.csv file and creates a lot of files per NFTs, if not running in Trial Mode.

It is higly recommended to run the commit command in Trial Mode before running without, as this allows you to entirely validate the provided information in the CSV file. When running without Trial Mode, the process bails out on the first error.

Generated Artifacts

Filename

Description

00000.commit.log

The log file of the commit phase (Appends multiple runs)

00000.commit-progress.json

The progress information used to continue on last successful operation

nnnnn.m.png

The original image. The file respects the original image format, i.e. can be jpg, svg, gif etc. nnnnn ranges from 00001 to 99999 m ranges from 1 to 3

nnnnn.m-social.webp

The optimized image for social media (SEO Cards)

nnnnn.m-thumb.webp

The thumbanil version of the image

nnnnn-metadata.json

The NFTs meta data information

nnnnn-record.json

The related line of the CSV file in JSON format

Examples

This is a Trial Mode run to validate the 00000.nfts.csv

BAT
|

This is a real run that generates the artifacts

Shell
|

As a result you get something like this

Shell
|



Updated 01 Jun 2022
Did this page help you?
Yes
No