NMKR Docs
ProductsContact
English
English
  • Welcome to NMKR Docs
  • Introduction
    • About NMKR
    • Powered by NMKR
    • What is an NFT?
      • What is IPFS?
    • Why Cardano?
  • NMKR Studio
    • Introduction - NMKR Studio
    • Features Overview
    • 🖥️Learn NMKR Studio in 3 minutes
      • Basic Workflow
    • How to - Quick Start Tutorials
      • Quickstart Full Video Tutorial
      • Guidelines Planning a Project
      • How To Add Tokens
      • How to set up Metadata
      • How To Sell Tokens
      • How To Set Up Sales Conditions
      • How To Do a Reveal
      • How To Burn Tokens
      • How To Enable Royalties
      • How To Enable DIDs
      • How To Set up Whitelisting
      • How to Airdrop Tokens
    • Pricing
    • Account
      • Registration & KYC
      • Security
      • Wallets
      • Mint Coupons
      • Dashboard
      • Transactions
      • Invoices
      • API Keys
    • Project
      • Policy
        • Managing policies
      • Create
      • Edit
      • Metadata Template
      • Statistics
      • DID - Decentralized Identifier
      • Notifications
      • Royalties
      • Additional Payout Wallets
      • Affiliate links
      • Export Metadata as Zip
      • Export NFT as csv
      • Mint and Send Jobs
      • Export placeholder.csv
    • Token
      • Manage Tokens Tab
      • Upload
        • Upload single tokens
        • Bulk Upload Files and Metadata
          • Bulk Upload via Drag and Drop
          • Bulk upload via SFTP
      • Edit
      • Metadata
        • Add Token-specific Metadata
        • Fingerprint (Metadata preview)
        • Metadata Check
        • Metadata Standard for fungible Tokens
        • Fully on-Chain NFTs
          • Partial URL-Encoding
        • CIP-68
      • Duplicate
      • Delete
      • Burn
      • Update (Edit after Mint / Reveal)
    • Set up Sales
      • Manage prices / Pricelist
        • Create new Prices
        • Free Drops
        • Custom Token payment
        • Discounts
      • Sales Conditions & Whitelisting
        • Sales conditions depending on policy ID or stake pool
        • Whitelist with Count
        • Blacklist
        • Test Sales Condition
      • Block Tokens
      • NMKR Pay
        • Set up NMKR Pay
        • MultiSig Payment
        • Website Integration
        • Specific Payment Links
        • Manual sending in NMKR Pay
        • FIAT ETH and SOL Payment
      • Pay-In Address
      • Auction
    • Minting
      • Minting on Demand
      • Manual Minting
      • Airdropper
        • Airdrop with random distribution
        • Airdrop with specific distribution
    • Tools
      • Managed Wallets
      • Split Addresses
      • Direct Sales
      • Policy Snapshot
      • Integrations & Plugins
        • NFT Pal
        • Zapier
    • Testnet
      • Create Testnet Account
      • Testnet Wallet & tADA
      • Testnet API Swagger
  • NMKR Studio API
    • Introduction - NMKR Studio API
    • API Features
    • Swagger API Endpoints
    • Get started with the API
    • API Swagger
      • Get Started with the Swagger
      • Swagger Responses and Error Codes
    • API Examples
      • Users
        • Payout Wallets
        • Subcustomers
      • Project
        • Create Project
        • Upload File and Metadata
      • Payment
        • Create unique NMKR Pay Link for random Token sales
        • Create NMKR Pay Link for specific Token sales
        • Get Payment Address for single NFT sales with native Tokens
        • Create NMKR Pay Link for a multi-specific Tokens sale
      • Minting
        • Manual Minting
      • Smart Contract
        • Secondary Sales via NMKR Pay
    • API Open Source Contributions
  • NMKR Mint
    • Introduction - NMKR Mint
    • Mint single NFTs
    • Mint Collection
  • NMKR Playground
    • Introduction - NMKR Playground
    • ADA Payment Link
    • Paperwallet
  • NMKR Pool
    • What is Staking?
    • Stake with NMKR Pool
  • Helpful Links
    • Cardano NFT Ressources
    • Cardano Resources
    • Cardano Wallets
    • Open Source Repositories
    • Security Practices
    • Deal with Bots
Powered by GitBook
On this page
  • Upload in the correct order
  • Naming of the files
  • Main files
  • Subfiles
  • Metadata JSON
  • Metadata with placeholder.csv
  1. NMKR Studio
  2. Token
  3. Upload

Bulk Upload Files and Metadata

NMKR Studio allows you to upload files in bulk directly from the user interface.

PreviousUpload single tokensNextBulk Upload via Drag and Drop

Last updated 8 months ago

Upload up to 1000 files directly from the user interface using drag and drop, or upload larger batches in bulk using SFTP. However, both options require proper file naming and uploading the files in the correct order. or

Upload in the correct order

  1. Main file first (image or animated gif)

  2. Subfiles next

  3. Metadata (renamed JSON or Placeholder.csv) last. Maintain this order even if you modify the project, especially with the placeholder.csv method.

Naming of the files

For instance, uploading a file named "Token #0001.jpeg" will result in the following naming:

  • The asset_name/token name of the file will be "token0001".

  • The display_name (the name of the NFT) will be "Token #0001".

Main files

After a correct naming of the files you can start to upload the files

To add a subfile to an existing File/Token with the name "Token #0001", you need to upload a file named "Token #0001.subfile.1.png". This file will be added to the NFT as the first subfile.

If you want to add more subfiles, you can name them "Token #0001.subfile.2.png" for the second subfile, and "Token #0001.subfile.3.png" for the third subfile, and so on.

Metadata JSON

Metadata with placeholder.csv

To make sure everything works correctly, you need to name your files in a certain way. The names of the files will determine the and for the token. It's important to name subfiles and metadata properly too.

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 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 of an asset does not correlate in any way with the and is randomly generated. Please use the to override the display names of your tokens. The reason for that is simple; if you are going to use in your project, the buyer could see the (not the ) 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.

The uploaded metadata must be in the correct . 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 .

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).

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

asset_name
display_name
subfile
asset_name / token name
display_name
placeholder.csv method
MultiSig Payment
asset_name
display_name
Subfiles
Metadata Structure
add ipfs hashs of externally uplaoded files
metadata override
placeholder.csv method
Klick here if you want to learn how to use the User Interface
here if you want to learn how to set up the SFTP Upload.