NFTs2Me
  • πŸ’‘What is NFTs2Me?
  • πŸ›‘οΈContracts Audit
  • Create and deploy NFT Collection
    • ℹ️Initial Steps
    • πŸ–ΌοΈEditions Collection
    • 🎭Drops Collection
    • 🎨Generative Art Collection
      • 🎎Creating NFT Collection with Subcollections
      • πŸ¦Έβ€β™‚οΈHow to Add 1/1 NFTs to Your Generative Art Collection
    • Ⓜ️Minting types
    • πŸ…°οΈDeploy Advanced Options
      • Initial Phase
      • Mint NFTs at creation
      • Revenue distribution
      • Souldbound collection
      • Metadata public/delayed reveal
    • πŸ’°Minting Page
    • πŸ“œProtocol Fee
  • Features
    • πŸ–ΌοΈArt Generator (no code)
    • ⛓️Multichain
    • πŸ’³Credit Card / FIAT Payments
    • πŸ’ΈERC-20 / Stablecoins minting fee
    • πŸ’±Any-payments
    • πŸ€–DallE-2 + ChatGPT AI NFTs
    • πŸ—οΈCollections as NFTs (Ownership)
    • 🌏Custom mint pages and widget
    • πŸ”ƒIPFS Hosting
    • πŸ–‡οΈCustom IPFS URI
      • πŸ–‡οΈCustom IPFS URI Artwork
    • πŸ”—Custom HTTP URL
      • πŸ”—Custom HTTP URL Artwork
    • πŸ‘€Soulbound (Non-transferable NFTs)
    • πŸšͺToken Gating
    • πŸŒ†NFT Holders Snapshots
    • πŸ“œRedeemable NFTs (POAPs)
    • 🎰Automatic Logo and Banner Generation
    • πŸ™ˆPlaceholder (Delayed Reveal)
    • πŸŽ›οΈMinting Types
      • πŸ”’Sequential Minting
      • πŸ‘†Specify Minting
      • 🎲Random Minting
    • πŸ’°Split Revenue
    • πŸͺ‚Airdrops / free minting with CSV batch sending
    • πŸ“ƒFlexible Whitelist with CSV batch sending
    • πŸ§ͺTestnet deploy
    • πŸ’΅Creator Fee Enforcement (NFT royalties)
    • πŸ“°Decentralized Governance & on-chain voting
    • πŸ—ƒοΈExtend rich metadata
    • πŸ’²Affiliates System
    • β›½Gas efficient contracts
    • 😎ENS domain resolution
    • πŸ‚Farcaster Integration
    • Referral System
  • Dashboard
    • πŸ‘“Overview
    • 🌎Minting Page
    • βš™οΈMint Settings
    • πŸ’²Earnings, royalties and protocol fee
    • πŸͺ‚Airdrops
    • πŸ“„Whitelists
    • 🏑Ownership
    • 🦸Affiliates
    • 🧰Utils
    • πŸšͺToken Gating
    • πŸ’³Credit Card Payments
  • More
    • πŸ”‘Custom Needs
    • πŸ“¬Contact
    • πŸ›£οΈRoadmap
    • πŸ“ˆTrending collections
    • πŸ‘¨β€πŸ«Creator Profile
  • NFT Media types
    • πŸ“‘Media metadata
    • πŸ–ΌοΈImage support
    • πŸ“½οΈVideo support
    • πŸ”ŠAudio support
    • πŸ“”PSD support
    • 🟦3D support
  • Supporters
    • πŸ₯‡Supporter PIN
    • ⬆️Booster Pack
    • πŸ™‹Get Discord roles
Powered by GitBook
On this page
  1. Features

Custom IPFS URI

PreviousIPFS HostingNextCustom IPFS URI Artwork

Last updated 3 months ago

If you have already uploaded your metadata and images to IPFS and you want to enter this information instead of uploading it again to IPFS, you can do using NFTs2Me.

Select "IPFS URI" tab when you are creating a project and then paste your IPFS URI. This mode is active when you create a new NFT project using the "Editions" or "Drop" mode.

The fields that you must fill are:

  • IPFS URI where the metadata is located. At this point it is important to know the format that should be the .json files. For the first token it has to be ipfs://IPFSURI/1.json, the second token would be ipfs://IPFSURI/2.json and so on until the total supply. If total supply is 100 the last token would be ipfs://IPFSURI/100.json. Important about the IPFSURI format of "Content Identifiers" (CIDs), some examples would be:

    • v0: QmdfTbBqBPQ7VNxZEYEj14VmRuZBkqFbiwReogJgS1zR1n

    • v1: bafybeihdwdwdcefgh4dqkjv67uzcmw7ojee6xedzdetojuzjevtenxquvyku

  • Total supply of the collection. It is important that the number coincides with the amount of .json files that have been uploaded. If there is an error, the tool will warn you in case it has failed to find the last json file, and you will see something like this:

πŸ–‡οΈ
IPFS URI tab selected creating a project