What is an IPFS gateway? Access through the web

An IPFS gateway serves IPFS content over HTTP. A visitor can open a file in a regular browser without running an IPFS node. The content identifier and the web endpoint delivering the content are separate parts of the request.

The gateway must be able to retrieve the content, and its access rules must permit the request. Not every gateway serves every file. An access endpoint alone does not guarantee permanent retention or confidentiality.

Example: A new address, the same file identifier

A project displays an image through provider A's gateway. If A stops operating, the project can switch to gateway B if B can retrieve and serve an available copy for the same CID. The server part of the browser URL changes while the requested content identifier stays the same. Changing gateways cannot solve the absence of any reachable copy.

A gateway in this context retrieves files; it is not a bridge for moving tokens between blockchains. Private access credentials should also be kept distinct from the content identifier itself.

Sources

• IPFS gateways