Skip to main content

NFT Backup

Legacy: This page documents Filebase's IPFS tier. For new deployments, use the S3-compatible object storage tier with the s3.filebase.io endpoint.

NFT Backup mirrors NFT media and metadata files from on-chain references to a Filebase IPFS bucket — guarding against the original hosting going offline and the assets becoming inaccessible.

How it works​

  1. You point NFT Backup at a contract address.
  2. Filebase walks the contract's tokens, extracting each token's tokenURI / metadata.
  3. For every metadata file and every media file referenced from metadata, Filebase pins the content to your IPFS bucket.
  4. New mints are processed continuously.

The result: a complete IPFS-pinned mirror of your collection's media, addressed by stable CIDs, that doesn't depend on the original hosting provider staying up.

Use cases​

  • Long-term preservation of an NFT collection's media.
  • Insurance against the original hosting (Pinata, Infura, an HTTP server) going down.
  • Ensuring a CID-only chain reference (ipfs://...) remains resolvable indefinitely.

What's next​