Backing up NFTs

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

Set up a backup

1. In the console, open NFT Backup.
2. Click New Backup.
3. Configure:

Field	Value
Network	The chain the contract is on
Contract address	The token contract
Destination bucket	An IPFS bucket on your Filebase account
Mode	One-time backup or continuous (new tokens auto-backed-up)

4. Click Start Backup.

Filebase walks the contract, fetches each token's metadata, and pins the metadata plus referenced media files to the destination bucket.

Monitoring progress

The backup row shows progress (tokens fetched, files pinned, errors). Click into the row to see per-token status — any tokens whose metadata or media couldn't be fetched are flagged for review.

Continuous mode

In continuous mode, Filebase watches the contract for new mints and pins their content automatically. Useful for live, growing collections.

Storage cost

Backups consume normal Filebase storage. A typical NFT (one metadata file plus one media file) is small — single-digit MB at most — so even large collections (10,000s of tokens) often fit within a few hundred GB.

What's next

• NFT Backup overview
• Supported chains