Legacy IPFS storage

Legacy section. This area documents Filebase's IPFS storage tier. New deployments should use Filebase's primary S3-compatible object storage, which uses the s3.filebase.io endpoint and offers free egress.

This section is preserved for existing customers using IPFS-backed buckets, the IPFS Pinning Service API, IPNS names, dedicated IPFS gateways, Filebase Sites, and NFT Backup.

Endpoint distinction

The two tiers use different S3 endpoints:

Tier	S3 endpoint	Region
S3-compatible object storage (recommended)	https://s3.filebase.io	auto
IPFS storage (legacy)	https://s3.filebase.com	us-east-1

If you're configuring a new application, you almost certainly want s3.filebase.io. The s3.filebase.com endpoint is for existing IPFS bucket workflows.

What's in this section

• IPFS concepts — what IPFS is, CIDs, pinning, gateways.
• IPFS pinning — pin files via the S3 API or the Pinning Service API.
• IPNS names — managing IPNS records.
• Dedicated IPFS gateways — running your own IPFS gateway on Filebase.
• IPFS RPC API and Pinning Service API — the two HTTP APIs specific to IPFS workflows.
• Filebase Sites — host static sites on IPFS with IPNS.
• NFT Backup — back up NFT media and metadata to IPFS.

When IPFS is the right choice

Use IPFS storage when:

• You need IPFS CIDs for content addressing (e.g., NFT metadata that references CIDs).
• You're building applications that interoperate with the broader IPFS ecosystem.
• You're maintaining an existing IPFS-based system.

For everything else — straightforward private buckets, public asset hosting, application storage, backup workflows — use the S3-compatible object storage tier.