IPFS Dedicated Gateways: Retrieving Your NFTs
Learn how to retrieve NFT assets using an IPFS Dedicated Gateway.
An IPFS gateway is an IPFS peer that accepts HTTP requests for IPFS CIDs. A dedicated gateway provides users with a convenient way to access IPFS content without needing to run an IPFS node themselves. The gateway acts as an intermediary between the user's web browser or application and the IPFS network, retrieving and serving content on behalf of the user.
For a deep dive into IPFS gateways and how they work, plus a full walkthrough of using IPFS gateways on Filebase, see our documentation here:
IPFS dedicated gateways can be used to retrieve and share any IPFS CIDs, even if they are not pinned to your Filebase account. An example might be an NFT you’ve purchased from a collection. If the NFT’s assets, such as its image, are stored on IPFS, you can retrieve and share them using a Filebase IPFS dedicated gateway.
View an NFT that you own. This example uses an NFT minted on Ethereum, but any chain can be used if the NFT’s assets are stored on IPFS.
The location of this detailed data will vary based on the marketplace.
On OpenSea, this Token ID brings up the NFT’s metadata file. This workflow may vary based on the marketplace you are using.
Some marketplaces will display this information using a ‘View Original’ or ‘View Metadata’ button. Please note that this workflow is for NFTs on OpenSea that have been stored on IPFS. If an NFT has its assets stored on another platform like Arweave, this workflow will be different.
The IPFS CIDs will have a file name listed after the CID value (In this example “/3294.png”).
Filebase IPFS Dedicated Gateways are a feature only available to paid users. They are not available for users on the free tier.
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.
gateway-namewith your IPFS Dedicated Gateway name, and IPFS CID with your NFT’s IPFS CID.