Mintplex.xyz Docs
  • What is Mintplex?
  • Guides
    • How to create an NFT collection
    • Creating your first Mintplex project
    • Anatomy of a Mintplex project
    • Setup Images and Metadata on IPFS
    • Generating a Contract
      • Project Information
      • Teams and Permissions
      • Contract Features
        • Remove Mintplex Signature
        • Only Owner Minting
        • Allowlisting Mode (aka. Whitelisting)
        • Allow Minting On Deployment
        • Maximum Mints per Transaction
        • Restrict Wallet Mints
        • Limited Token Supply
        • Minting Fee
        • Pre-Reveal Drop
      • Payouts
      • Header Mark
      • Generate
    • Deploying your contract
    • Airdrop a token to someone
    • Listing your NFT collection on a marketplace
    • Minting Embeds and Website
      • How to use the Mintplex embed with custom buttons
  • FAQ
    • My metadata does not pass!
    • How do I deploy to testnet
    • How do I list my NFT contract on OpenSea?
    • How do I mint tokens for myself or team?
  • Mintplex Apps FAQ
    • Shopify Token-Discount Plugin
      • Advanced Setup vs Basic Setup
        • Advanced Setup FAQ
          • How to create a Shopify App Key
          • How to Generate a Price Rule Id
        • Basic Setup FAQ
          • How to Generate a Discount Code
  • Extras
    • 💥Join us on Discord
    • 📚Youtube Tutorial Walkthrough
    • 🐦Follow us on Twitter
    • 📧team@mintplex.xyz
Powered by GitBook
On this page
  • Your Images CID is not set
  • Your metadata files are not named properly
  • Your metadata files do not have a valid image link
  1. FAQ

My metadata does not pass!

PreviousHow to use the Mintplex embed with custom buttonsNextHow do I deploy to testnet

Last updated 2 years ago

If your metadata does not appear to be validating it is highly likely that one or more of the following points are causing your issue. Once fixed you should have no issues with metadata being validated.

Your Images CID is not set

The Images CID should be a folder on IPFS where each image is named after its associated token ID. So token id 1 should have an image in this folder named 1.png token id 2 should have an image in this same folder names 2.png and so on...

You may have an alternative file extension, but the name cannot have any other name other than the token id.

Your metadata files are not named properly

These files must not have any file extension at all.

For Mintplex to work, we must have a metadata folder CID that contains as many files as your token supply will allow. These files must be named in association with their token id

For example, token 1 should have a file in the metadata folder named simply, 1

These files will contain valid JSON data about your token but must have no file extension.

Your metadata files do not have a valid image link

Here is an example of a valid metadata file

{
  "dna": "e11e3dd98eaddac18c28dff55a76ea6d",
  "name": "0x #1",
  "description": "A small NFT example",
  "image": "ipfs://QmZrEceFSWpJSW8yraQbVmcX285PZ77XwNRd3iCcKFWBza/1.png",
  "attributes": [
    {
      "trait_type": "Background",
      "value": "yellow"
    }
  ],
}

Take note of the image attribute and how it contains a valid CID hash + the associated file name. To verify your image is working you can go to: https://gateway.pinata.cloud/ipfs/<YOUR IMAGE CID FOLDER HASH>/1.png

If an image does not load - then it will not work on OpenSea either nor validate with Mintplex