Filebase Sites

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

Filebase Sites publishes a static website on IPFS, automatically creating an IPNS name so the URL stays stable across content updates. Each site is reachable at:

https://<site-name>.myfilebase.site

When you push a new build, only the IPNS record changes — the URL stays the same.

How it works

1. You upload your static site as a CAR file (or a folder of files) to a Filebase IPFS bucket.
2. Filebase creates an IPNS keypair for the site.
3. Filebase publishes the latest CID to the IPNS name.
4. Requests to <site-name>.myfilebase.site resolve through the IPNS record to the current CID and serve the content.

When you deploy a new version, the CID changes and Filebase updates the IPNS record. Visitors see the new content within ~1 minute as DNS / IPNS propagation completes.

Use cases

• Marketing pages
• Documentation sites
• Decentralized application frontends
• Portfolios

For ordinary static-site hosting where you don't need IPFS specifically, the S3-compatible object storage tier is simpler and faster.

Plan limits

Plan	Sites allowed
Free	1
Starter	10
Pro	50
Unlimited	100

Site naming

• 3 to 63 characters
• Lowercase letters, numbers, and dashes
• Start and end with a letter or number
• Globally unique

Specifications

Setting	Value
IPNS TTL	5 minutes
IPNS Validity	48 hours
Propagation time	Typically under 1 minute

What's next

• Managing sites
• Custom domains