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
  • Edit your NFT or FT
  • Description tab
  • Files tab
  • Metadata override tab
  1. NMKR Studio
  2. Token

Edit

Edit the uploaded and unminted token in NMKR Studio

PreviousBulk upload via SFTPNextMetadata

It is always possible that you made some mistakes like typos or wrong metadata values with your token. That should be updated before you begin the minting process. In NMKR Studio it is very easy to edit specific token details.

Plese note that changes to already minted tokens won't have any effect on the Blockchain as long as you haven't started the .

Edit your NFT or FT

Description tab

Since the recent update of NMKR Studio, the asset_name can hold special characters and spaces.

Static Price with specific sales

Files tab

Metadata override tab

It is important that the metadata added here is complete. It is recommended to use the <asset_name>, <display_name>, <policy_id>, <ipfs_link> and <mime_type> placeholders in there to make sure, that it has the correct values. However, if you want to add metadata that already contains the values for above mentioned placeholders, the metadata override tab is where you want to place them. An asset_name that differs from the token name in NMKR Studio will cause errors when minting. Also make sure to use strings (" ") and not only values. E.g. "traitcount": "12" would be correct. "traitcount: 12 would NOT be correct.

Placeholders for subfiles

If you uploaded files via SFTP or the User Interface to NMKR Studio, but you need to use the metadata override, please make sure to use the correct subfile placeholders:

"files": [
          {
            "name": "<display_name>",
            "mediaType": "<mime_type_subfile_1>",
            "src": "<ipfs_link_subfile_1>"
          },
          {
            "name": "<display_name>",
            "mediaType": "<mime_type_subfile_2>",
            "src": "<ipfs_link_subfile_2>"
          }
        ],

Add externally uploaded files via IPFS hash

            "name": "<display_name>
            "mediaType": "<mime_type>",
            "src": "ipfs://QmZNqgUHhGukXD27pAZtZE5BEkx6VXB1AhQVmK55QCd31y"

Placeholder Data Tab

The button to edit specific tokens can be found in the actions bar of your token on the .

The following window looks almost the same as the one you already know from the process of . It is separated in three main tabs (Description, Files and Metadata override) and one optional tab (Placeholder Data) which only shows up if you specified any .

The description tab is where you change the basic information about your token like the Tokenname, the Displayname(optional) and the description(optional). The Tokenname is related to the in your metadata and should be always matching. Therefore we also recommend to always use the if you use the . It is limited to 32 characters.

We recommend that the asset_name / token name of an asset does not correlate in any way with the display_name and is randomly generate. The reason for that is simple; if you are going to use in your project, the buyer could see the assetname in the transaction when signing the payment transaction. If the numbering of your tokens rarities are related to the token numbers, a buyer could decide to cancel the transaction and start over again.

The is where you want to add special characters and longer names with up to 63 characters (e.g. Landplot #1011). This displayname, if given, will replace the tokenname on explorers like pool.pm. The display name replaces the in your metadata template. The description will replace the in your metadata template. It can also contain special characters and up to 63 characters. if you want to have the same description for all the tokens in your project, it makes sense to replace the with hard values.

By standard, the NFTs price will be taken from the , but you are also allowed to specify a static price for every token manually here, please keep in mind that these prices won't work with and you have to use the of for it.

The files tab of your token allows you to add to your tokens and also shows the (e.g. QmZNqgUHhGukXD27pAZtZE5BEkx6VXB1AhQVmK55QCd31y) of the uploaded and pinned files. Subfiles that are , will also show up here. The functions to submit IPFS hashes directly and upload files via URL are not supported in the current version of NMKR Studio (coming soon). If you want use external IPFS hashes of already uploaded and pinned files, please add them directly to your metadata in the or the .

If you want to add subfiles, please follow the same .

The Metadata Tab allows you to that does not use the .

Add the complete metadata with "721" in the metadata override and click on "save changes". It is recommended to use the afterwards to identify eventual issues.

You can add files to your token that were externally uploaded to IPFS. In order to do this, please just insert the IPFS hash directly to the metadata of your token, as you see in the example below. Don't forget to add the to have the correct file format fetched.

The placeholder tab will only show up if you added any . You are now able to specify the token-specific values via the user interface in the Placeholder Data Tab of each single token that is uploaded to the project.

As this is obviously no suitable way to add metadata values to a higher number of tokens, please use any other to bulk add metadata to your tokens. The easiest for people without much coding experience should be the .

Manage NFT Tab
uploading a token
custom fields in your metadata template
asset_name
<asset_name> placeholder
Metadata override
MultiSig Payment
displayname
<display_name> placeholder
<description> placeholder
<description> placeholder in the metadata template
pricelist
random sales
specific payment links
NMKR Pay
subfiles
IPFS hashes
uploaded via the SFTP
metadata override
metadata that you upload via SFTP
workaround as you would do it when you upload a new token with subfiles
set token specific Metadata
Metadata Template
metadata check
<mime_type> placeholder
custom fields to your metadata template
bulk uploading method
placeholder.csv method
remint & burn process to override the metadata of the token on-chain
The description tab of your token
The files tab of your token
Metadata override
Placeholder Data Tab in the edit section fo your token