# Custom IPFS URI

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.

<figure><img src="https://3026745716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsfdCMm7uC0GmVAWnxMdG%2Fuploads%2Fgit-blob-ff732c172d7ec1719406e8c0d5fd8c9a85f27e46%2Fipfs%20uri%20metadata%20nfts2me.png?alt=media" alt=""><figcaption><p>IPFS URI tab selected creating a project</p></figcaption></figure>

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:

<figure><img src="https://3026745716-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsfdCMm7uC0GmVAWnxMdG%2Fuploads%2Fgit-blob-c568ff813b874fe18c6e2e3e14929254b11077c1%2FCaptura%20desde%202023-10-18%2012-38-33.png?alt=media" alt=""><figcaption></figcaption></figure>