https://gateway.pinata.cloud/ipfs/bafkreih5aznjvttude6c3wbvqeebb6rlx5wkbzyppv7garjiubll2ceym4
What’s going on here exactly? Let’s break it down. First you have the gateway domain. There are lots of different domains out there, like ipfs.io
, gateway.pinata.cloud
, and if you have a Pinata account you get a Dedicated Gateway which might look something like aquamarine-casual-tarantula-177.mypinata.cloud
. Each of these can be used to bridge files from IPFS to HTTPs. Next you have the IPFS path which looks like ipfs/
and this is necessary for a gateway to work. Finally we have the CID at the end, which is the actual IPFS address for our content.
QmWfHgs3nKiyFWx3tFEYvm8DiHTrCsxEHxvDdBh95ZQSLT
and the inside looks something like this:
/pinnie.png
or clouds.json
to the end of our folder path. In the end we would have something like this.
bafkreih5aznjvttude6c3wbvqeebb6rlx5wkbzyppv7garjiubll2ceym4
to the end of Pinata’s Public Gateway: