Bulk Upload Files and Metadata

The bulk upload via SFTP allows you to drag and drop files directly from your device into the project.
It is very important that the upload of the files happen in the correct order. 1) The mainfile needs to be uploaded first 2) Followed by subfiles 3) The last files you want to add is alsways the Metadata (renamed JSON or Placeholder.csv) Please make sure to keep this order also if you make any changes to your project especially with the placeholder.csv method

Naming of the files

The SFTP upload works this way, that it gives the token that you are herewith going to upload the asset_name/token name and the display_name depending on the file name of your main file. The naming is also very important for adding subfiles and metadata, so please make sure to name your files correctly.

Bulk upload main files

Uploading a file named "Token #0001.jpeg" will result in the following naming: The asset_name/tokenname of the file will be "token0001". The display_name (the Name of the NFT) will be "Token #0001".
The main file must be an image or animated gif, because this file will be taken as thumbnail in wallets, explorers and on secondary merkats. It may make sense to upload a downscaled version here and the full scale version as subfile for a faster loading time on above mentioned platforms.
We recommend that the numbering of your tokens rarities are not related to the token numbers. If this needs to be the case, we recommend that the asset_name / token name of an asset does not correlate in any way with the display_name and is randomly generated. Please use the placeholder.csv method to override the display names of your tokens. The reason for that is simple; if you are going to use MultiSig Payment in your project, the buyer could see the asset_name (not the display_name) in the transaction when he is signing the payment transaction. Therefore, a buyer could decide to cancel the transaction if he sees an "not rare/common number" and start over again.

Bulk upload subfiles

If you upload a file named "Token #0001.subfile.1.png", the previously uploaded File/Token with the name "Token #0001" gets a subfile added. This file will be added to the NFT as the subfile Number 1. If you want to add another subfile, you want to name it "Token #0001.subfile.2.png", the same with a third and following subfiles.

Bulk upload metadata JSON

The uploaded metadata must be in the correct Metadata Structure. It is allowed to contain placeholders like <policyID>, <asset_name>, <display_name>,<ipfs_link>,<mime_type> as these data is already given with the upload of the token and creation of the project. If you want, you could also add ipfs hashs of externally uplaoded files.
It is important that .json files are renamed to .metadata files. Please make sure in the detail info of your file that the suffix is not ".metadata.json." If you upload a file named "Token #0001.metadata", the previous uploaded File/Token with the name "Token #0001" will take this file as metadata (in the metadata override).

Bulk upload metadata with placeholder.csv

The easiest method to upload metadata in bulk is the placeholder.csv method. It allows you to use a spreadsheet that contains all metadata of your tokens to add them to your tokens in your project.