IPFS Dedicated Gateways: Using IPFS Dedicated Gateways in Metadata Files
Using IPFS Dedicated Gateways in Metadata Files.
Filebase’s IPFS Dedicated Gateways offer a way to create unique, branded IPFS gateway URLs that can be used in place of public IPFS gateways, like ipfs.io.
An IPFS-dedicated gateway can be used in a metadata file to ensure that the content referenced in the metadata file can be accessed reliably and efficiently.

Gateway names are subject to the same naming restrictions as bucket names. All gateway names must be lowercase, between 3-63 characters, and must be unique.

Then, IPFS CIDs can be retrieved using this gateway, such as:
https://my-gateway.myfilebase.com/ipfs/IPFS-CID
We’ll start by uploading 3 images to Filebase for us to use.
Select ‘Create Bucket’ in the top right corner to create a new bucket for your NFTs.

Bucket names must be unique across all Filebase users, be between 3 and 63 characters long, and can contain only lowercase characters, numbers, and dashes.


Once uploaded, they will be listed in the bucket.

Choose the method you prefer, and take note of the IPFS CID.

{
"name": "NFT #1",
"description": "The first NFT in my collection",
"image": "https://my-gateway.myfilebase.com/ipfs/IPFS_FILEBASE_CID",
"attributes": [
{
"trait_type": "Rarity",
"value": "Average"
}
]
}
Replace IPFS_FILEBASE_CID with the CID for each NFT image you uploaded to Filebase.
If you have any questions, please join our Discord server, or send us an email at [email protected]