NFT data stored by NFT.Storage can be accessed from the decentralized IPFS network from any
peer that has the content. CIDs reference immutable content so you can
be sure the content you access is the content referenced in the NFT.The
data can be fetched directly in the browser using Brave, or via a public IPFS gateway, or by using IPFS Desktop or the IPFS command line.If
fetching content using a public IPFS gateway (e.g., directly using an
HTTP URL or via Brave), note that the availability and speed of
retrieving the content depends on the gateway. In cases where the
gateway is unable to retrieve a given CID (e.g., returns a 429 error),
you can try a different gateway or running and using your own IPFS node
instead.
IMPORTANT
UPDATE: Starting June 30, 2024, at 5 PM EST, NFT.Storage Classic
will no longer accept new uploads. However, rest assured, all data
you've uploaded before this deadline will continue to be safely stored
and accessible via IPFS and the Filecoin Network. Over time, latency and
availability may degrade, but your data is secure. Uploads will no
longer be accepted for: NFT.Storage Classic web app, API, and SDK,
NFTUp, Pinning API
The NFT.Storage Gateway brings the ease-of-use of HTTP IPFS gateways with the performance users expect from modern web infrastructure, leaning into CDNs and smart caching. Anyone can use it to fetch any content stored on NFT.Storage!
When a request is received by nftstorage.link,
it triggers requests to a number of public gateways and "races" them.
In the future, NFT.Storage might also run its own, dedicated gateway on
top of its IPFS infrastructure in this race. The CDN and caching for nftstorage.link
is optimized and will continue to be tweaked to ensure a fast retrieval
experience for users retrieving data stored on NFT.Storage.
