Closing your account
When you're ready to close your Filebase account, you'll need to clean up your data first.
Step 1 — Get under 5 GB
Account closure is gated on usage being 5 GB or less. This means you'll need to delete most of your data before you can close. The cleanup options are:
From the AWS CLI (recommended for large accounts)
Delete a single bucket and all its contents:
aws --endpoint https://s3.filebase.io s3 rb s3://my-bucket --force
The --force flag deletes every object before removing the bucket itself.
To bulk-delete only the contents of a bucket without removing the bucket:
aws --endpoint https://s3.filebase.io s3 rm s3://my-bucket --recursive
From the Filebase Console
- Sign in to console.filebase.com.
- Click Buckets, then click into a bucket.
- Select objects and click Delete.
The console limits batch delete to 1,000 objects at a time. For accounts with more than a few thousand objects, the AWS CLI is significantly faster.
Step 2 — Email Filebase
Once your account is using ≤ 5 GB, send an email to hello@filebase.com from the email address registered on the account, asking to close it. The Filebase team will confirm and process the closure.
What gets deleted
After closure:
- All buckets and their contents are permanently deleted.
- Your access keys are revoked.
- Billing information is retained as required by tax/accounting law (typically 7 years), but the account itself is closed and inaccessible.
If you change your mind before sending the email, you can simply not close the account — having a free-tier Filebase account costs nothing.
Exporting data
Before closing, download anything you want to keep. Filebase does not provide an export bundle service — pull objects via the AWS CLI, an SDK, or the console. The most efficient way for large datasets:
aws --endpoint https://s3.filebase.io s3 sync s3://my-bucket/ ./local-backup/
This downloads every object in the bucket to a local directory, preserving the key hierarchy.