Pricing
Filebase bills three things: storage, S3 API operations, and — on the free tier only — bandwidth. Egress is free on every paid plan with no monthly cap. There are no storage classes, no minimum object durations, no minimum object sizes, and no separate line items for encryption, the CDN, or replication. This page is the deep dive on what each bill includes and how it's calculated.
For current plan tiers and self-service sign-up, see the Filebase pricing page.
At a glance
| Component | Rate |
|---|---|
| Storage | $0.015 per GB-month |
| Egress (paid plans) | Free — no per-GB charge, no monthly cap |
| Egress (free tier) | 5 GB / month included; not available beyond cap |
| Class A operations (S3 API) | $4.50 per million |
| Class B operations (S3 API) | $0.36 per million |
| Free operations (S3 API) | DeleteObject, DeleteBucket, AbortMultipartUpload |
| Platform API requests | Free |
| Inbound transfer (uploads) | Free |
| Server-side encryption | Included |
| CDN delivery | Included |
| TLS | Included |
There is one storage class. There is no Standard / Infrequent Access split, no Glacier-style archive tier, no per-object lifecycle billing.
Free tier
Every Filebase account starts on a free tier. No credit card required.
| Free tier | |
|---|---|
| Storage included | 5 GB |
| Bandwidth included | 5 GB / month |
| Class A operations included | 1 million / month |
| Class B operations included | 10 million / month |
| Buckets | 1 |
| API endpoints | All |
The free tier is intended for evaluation and small projects. When you exceed either the storage or bandwidth limit, the account moves to read-only until you upgrade or reduce usage — Filebase does not charge overages on the free tier. Upgrading is a one-click operation in the Billing page of the console.
Storage
Rate
Storage is billed at $0.015 per GB-month of average peak daily usage over the billing period.
How GB-month is calculated
A "GB-month" is calculated by averaging the peak storage observed each day over the 30-day billing period. Storage is measured in binary GB (gibibytes — 1 GB = 2³⁰ bytes; 1 TB = 1,024 GB).
Two worked examples:
Example A — constant usage. You hold 100 GB throughout the entire month.
GB-months = 100 GB × (30 days / 30 days) = 100 GB-months
Charge = 100 × $0.015 = $1.50
Example B — usage that grows mid-month. You hold 1 GB for the first 5 days, then upload another 2 GB and hold 3 GB for the remaining 25 days.
GB-months = (1 × 5/30) + (3 × 25/30) = 0.167 + 2.5 = 2.667 GB-months
Charge = 2.667 × $0.015 = $0.04
What counts as stored bytes
Filebase counts the object body plus user-supplied metadata. System metadata Filebase generates for you (ETags, content-length headers, internal indexes) is not billed.
For multipart uploads, in-progress parts that have been uploaded but not yet committed via CompleteMultipartUpload do count toward your storage until the upload is completed or aborted. Always call AbortMultipartUpload on transfers you don't intend to finish — the console and aws s3api list-multipart-uploads will surface dangling uploads.
No minimum object duration
You can write an object and delete it five minutes later, billed only for the fractional GB-month. There is no 30-day, 90-day, or any other minimum charge.
No minimum object size
A 1-byte object is billed as 1 byte for the period it exists. There is no minimum object-size charge (compare to AWS S3 Glacier's 40 KB minimum or S3 Standard-IA's 128 KB minimum).
Bandwidth (egress)
Paid plans: free, no caps
On every paid plan, outbound data transfer is free of charge with no monthly cap. This includes:
GetObjectresponses and multipart range reads via the S3 API.- Public-bucket downloads served through the Filebase CDN.
- Pre-signed URL downloads.
- Listing responses.
The bandwidth dashboard in the console is provided for visibility only — to help you understand traffic patterns. It does not roll up into your bill on a paid plan.
See bandwidth for the categories the dashboard breaks egress into.
Free tier: 5 GB / month
Free-tier accounts include 5 GB of egress per calendar month. If you exceed it, downloads return 403 Forbidden until the next month or until you upgrade to a paid plan.
Inbound transfer is always free
Uploads — PutObject, UploadPart, CopyObject from another source — never cost bandwidth, on any plan.
Operations
Every successful S3 API request falls into one of three buckets: Class A (state-mutating), Class B (state-reading), or free.
Class A — $4.50 per million
State-mutating operations. Generally these write or change configuration:
ListBucketsPutBucket/CreateBucketListObjects,ListObjectsV2PutObjectCopyObjectCreateMultipartUploadUploadPartCompleteMultipartUploadListMultipartUploadsListPartsPutBucketEncryptionPutBucketCors
A PutObject or a UploadPart is one Class A operation regardless of object size. A 100 GB multipart upload composed of 1,000 parts is roughly 1,002 Class A operations: 1 × CreateMultipartUpload + 1,000 × UploadPart + 1 × CompleteMultipartUpload.
ListObjects and ListObjectsV2 paginate at up to 1,000 keys per page; each page is one Class A operation.
Class B — $0.36 per million
State-reading operations. Generally these are non-mutating reads of objects or metadata:
GetObjectHeadObjectHeadBucketGetBucketEncryptionGetBucketLocationGetBucketCorsGetBucketLifecycleConfiguration
Range reads against the same object are one Class B operation per range request. A video player streaming a 100 MB asset via 100 ranged GetObject calls accrues 100 Class B operations.
Public-bucket reads through the Filebase CDN count as Class B operations, including responses served from the edge cache. There is no separate "edge request" or "cache fill" line item — every fetch the CDN serves on your behalf is exactly one Class B.
Pre-signed URL downloads count as the underlying operation: a pre-signed GetObject URL fetch is one Class B; a pre-signed PutObject URL upload is one Class A.
Free operations
These never count toward Class A or Class B totals, on any plan:
DeleteObjectDeleteObjects(one free op regardless of how many keys you batch into the call, up to the 1,000-key limit)DeleteBucketAbortMultipartUpload
Platform API
Every Platform API endpoint is free of charge, regardless of operation. Class A / Class B billing applies only to the S3 API at s3.filebase.io.
Unauthorized and failed requests
Requests that return 401 Unauthorized, 403 Forbidden, 404 Not Found, or 503 Slow Down do not generate charges of any kind. You're not billed for a request that didn't succeed.
Rate limits
The rate limit of 500 RPS per account applies independently of billing. Excess requests return 503 Slow Down and — as above — are not billed.
Billing cycle and invoicing
- Billing period: monthly, on the calendar day you signed up. A 30-day prorated cycle for partial months.
- Storage: measured continuously; each day's peak feeds into the GB-month average.
- Bandwidth: tracked continuously; not charged on paid plans.
- Currency: USD.
- Invoicing: automatically charged to the payment method on file at the end of each billing period. View past invoices in the Billing page.
Rounding
Storage is billed in fractional GB. Filebase does not round storage up to the next whole GB or whole month — a 2.667 GB-month bills as 2.667 × $0.015 = $0.040.
Operations are billed per million, rounded up to the next whole million. If you make 1,000,001 Class A operations in a month, your billable amount is 2 million; after deducting the 1 million Class A free tier, you'd owe 1 M × $4.50 = $4.50. Workloads that hover near a million-boundary will see step-function changes in their bill — pagination at large page sizes (ListObjectsV2 returns up to 1,000 keys per call) and bulk batching (DeleteObjects covers up to 1,000 keys per free op) keep request counts predictable.
Plan changes mid-cycle
Both upgrades and downgrades take effect immediately and are prorated to the day.
Plans
The published tiers bundle storage, bandwidth, and account features at a fixed monthly rate. All tiers share the same $0.015/GB-month overage rate and the same free-egress benefit.
| Free | Pro | Enterprise | |
|---|---|---|---|
| Storage included | 5 GB | See pricing page | Custom |
| Egress | 5 GB / mo | Free, no cap | Custom |
| Class A free / mo | 1 M | 1 M | Custom |
| Class B free / mo | 10 M | 10 M | Custom |
| Buckets | 1 | 100 | Unlimited |
| Storage overage | n/a | $0.015 / GB-mo | Volume pricing |
| Class A overage | n/a | $4.50 / M | Volume pricing |
| Class B overage | n/a | $0.36 / M | Volume pricing |
| Support | Community | Priority email | Dedicated |
For exact monthly prices and the most current plan inclusions, see the pricing page. For volume pricing on multi-petabyte workloads, contact hello@filebase.com.
Worked billing examples
The examples below assume you're past the free tier (a real Filebase bill subtracts the 5 GB free storage, the 5 GB free egress, the 1 M free Class A, and the 10 M free Class B before any charges apply).
Example 1 — General-purpose object storage
You store 1,000 objects of 1 GB each (1 TB total). Each object is read 1,000 times during the month (1 M total reads). Writes happen once per object at upload (1,000 writes).
| Line item | Calculation | Charge |
|---|---|---|
| Storage | (1,000 − 5) GB × $0.015 | $14.93 |
| Egress | 1,000 GB outbound | $0.00 |
| Class A | 1,000 writes ≤ 1 M free | $0.00 |
| Class B | 1 M reads ≤ 10 M free | $0.00 |
| Total | $14.93 / month |
Example 2 — Asset hosting at scale
You store 100,000 small files (100 KB each, 10 GB total) and serve 10 million reads per day for the month — roughly 300 M reads. Writes are minimal (100 K writes spread across deploys).
| Line item | Calculation | Charge |
|---|---|---|
| Storage | (10 − 5) GB × $0.015 | $0.08 |
| Egress | ~30 TB outbound | $0.00 |
| Class A | 100 K writes ≤ 1 M free | $0.00 |
| Class B | (300 M − 10 M free) × $0.36 / M | $104.40 |
| Total | $104.48 / month |
This workload is dominated by Class B charges. The same workload on AWS S3 would add ~$2,700/month in egress alone (30 TB × $0.09/GB).
Example 3 — Backup destination
A nightly database backup pipeline writes 5 TB to Filebase and reads back ≈ 1 GB per quarter for a restore drill. Each nightly backup is one ~170 GB object uploaded as a multipart with 100 MB parts (~1,700 parts + create + complete = 1,702 Class A per night × 30 nights = ~51 K Class A / month).
| Line item | Calculation | Charge |
|---|---|---|
| Storage | (5,120 − 5) GB × $0.015 | $76.73 |
| Egress | 1 GB | $0.00 |
| Class A | ~51 K ≤ 1 M free | $0.00 |
| Class B | minimal | $0.00 |
| Total | $76.73 / month |
Example 4 — High-traffic media site
A video-on-demand site stores 2 TB of media (20,000 videos averaging 100 MB) and serves 50 TB of egress per month. Players use range requests, averaging 50 ranged GetObject calls per video view; 500 K full views per month → ~25 M Class B operations.
| Line item | Calculation | Charge |
|---|---|---|
| Storage | (2,048 − 5) GB × $0.015 | $30.65 |
| Egress | 50 TB outbound | $0.00 |
| Class A | ~20 K initial uploads ≤ 1 M free | $0.00 |
| Class B | (25 M − 10 M free) × $0.36 / M | $5.40 |
| Total | $36.05 / month |
For comparison, the same egress on AWS S3 would be about $4,608 / month (50,000 GB × $0.09/GB after the first GB free), before AWS request charges.
Example 5 — Burst upload, then delete
You upload 1 TB at the start of the month for batch processing, then delete it after 3 days. The 1 TB lands as 10,000 objects of ~100 MB each, single-PUT (1 Class A per object = 10 K writes). Reads during processing: ~50 K Class B. Cleanup: 10,000 free DeleteObject calls.
| Line item | Calculation | Charge |
|---|---|---|
| Storage | 1,024 GB × (3 / 30) × $0.015 | $1.54 |
| Egress | varies | $0.00 |
| Class A | 10 K ≤ 1 M free | $0.00 |
| Class B | 50 K ≤ 10 M free | $0.00 |
| Deletes | free op | $0.00 |
| Total | ≈ $1.54 / month |
No minimum storage duration penalty, regardless of when you delete.
Example 6 — Free tier, evaluation use
A developer holds 1 GB and downloads 500 MB of test traffic per month while integrating Filebase into a side project, making ~5 K Class A and ~50 K Class B operations.
| Line item | Calculation | Charge |
|---|---|---|
| Storage | 1 GB ≤ 5 GB free | $0.00 |
| Egress | 0.5 GB ≤ 5 GB free | $0.00 |
| Class A | 5 K ≤ 1 M free | $0.00 |
| Class B | 50 K ≤ 10 M free | $0.00 |
| Total | $0.00 / month |
Cost comparison vs. AWS S3
A common reference workload — 10 TB stored, 5 TB egress per month, 5 M Class A writes (PutObject-class) and 50 M Class B reads (GetObject-class):
| Component | AWS S3 Standard | Filebase |
|---|---|---|
| Storage (10 TB) | $235.52 / mo (10,240 × $0.023) | $153.60 / mo (10,240 × $0.015) |
| Egress (5 TB) | $460.71 / mo (5,119 GB × $0.09) | $0 |
| Class A (5 M writes) | $25.00 / mo (5 M × $0.005/K) | $18.00 / mo ((5 M − 1 M) × $4.50/M) |
| Class B (50 M reads) | $20.00 / mo (50 M × $0.0004/K) | $14.40 / mo ((50 M − 10 M) × $0.36/M) |
| Total | ≈ $741 / mo | ≈ $186 / mo |
For workloads with significant egress — public asset hosting, video streaming, large-file distribution — the egress savings dominate. For pure-archive workloads with minimal egress, the lower storage rate ($0.015 vs. $0.023) still gives Filebase a 35% headline advantage on storage, with Class A and Class B rates that are slightly cheaper than AWS as well.
Rates above use AWS public list prices and are accurate as of writing. Always check the AWS S3 pricing page and the Filebase pricing page for current numbers.
Migration tools
Tools for moving data into Filebase from another provider don't add their own line items. You pay the storage rate for whatever lands in your bucket, plus the Class A operations needed to put it there.
- rclone is the recommended migration tool for most workloads — open-source, parallel, resumable. Inbound bandwidth is free; the writes themselves are Class A operations (one per
PutObject, plus the multipart create/parts/complete trio for large files). - AWS S3 → Filebase moves are typically a single
rclone copyoraws s3 syncinvocation. See the migration recipe. - Class A budgeting: a one-time bulk migration of N objects costs roughly N × $4.50 / M in Class A charges (after the 1 M free tier). 100 K objects → free; 10 M objects → ~$45 in writes. Multipart uploads of huge files can multiply this — a 100 GB object uploaded as 1,000 × 100 MB parts is ~1,002 Class A operations.
- Source-side egress (e.g. AWS egress fees during the transfer out of S3) is paid to the source provider, not Filebase. To minimize this, run the migration tool on a host close to the source — for example, an EC2 instance in the same region as the source bucket.
Frequently asked questions
Which S3 API operations are billable?
S3 API operations fall into three buckets:
- Class A ($4.50 per million) — state-mutating:
PutObject,CopyObject,ListObjects,CreateMultipartUpload,UploadPart,CompleteMultipartUpload,PutBucketCors, etc. - Class B ($0.36 per million) — state-reading:
GetObject,HeadObject,HeadBucket,GetBucketCors, etc. - Free —
DeleteObject,DeleteObjects,DeleteBucket,AbortMultipartUpload.
The free tier includes 1 M Class A and 10 M Class B per month on every plan. The Platform API is free regardless of operation. See Operations for the full classification.
Do CDN-served reads count as Class B operations?
Yes. Public-bucket reads served through the Filebase CDN count as Class B regardless of whether they're served from the edge cache or fetched from origin. There are no separate "edge request" or "cache fill" line items.
Is encryption an extra charge?
No. Server-side encryption at rest and TLS in transit are always-on and included on every plan.
Is the CDN an extra charge?
No. The Filebase CDN is included with public-bucket reads on every plan. There are no separate edge-request, cache-fill, or PoP fees.
Are there minimum storage durations?
No. You can upload an object and delete it seconds later — billing prorates to the fractional GB-month it actually existed.
Are there minimum object sizes?
No. A 1-byte object is billed as 1 byte. Filebase has no equivalent of S3 Standard-IA's 128 KB or Glacier's 40 KB minimum object-size charge.
Do failed or unauthorized requests get charged?
No. Requests that return 401 Unauthorized, 403 Forbidden, 404 Not Found, or 503 Slow Down cost nothing — they don't count toward Class A or Class B totals. You don't pay for traffic that didn't succeed.
How is storage measured — binary or decimal GB?
Binary. 1 GB = 2³⁰ bytes (1,073,741,824 bytes). 1 TB = 1,024 GB. This matches what most operating systems and S3 clients report.
Do in-progress multipart uploads count toward storage?
Yes. Parts that have been uploaded but not yet committed via CompleteMultipartUpload are stored — and billed — until the upload is completed or aborted. Always call AbortMultipartUpload on transfers you don't intend to finish.
To find dangling uploads:
aws --endpoint https://s3.filebase.io s3api list-multipart-uploads --bucket my-bucket
Is there a charge for inter-region replication?
Not applicable. Filebase exposes a single global namespace at s3.filebase.io — there are no regions to replicate between. Every bucket is reachable from anywhere in the world, and the CDN handles geographic distribution at the edge.
What happens when I exceed the free tier?
On the free-tier plan, storage and bandwidth limits are enforced as hard caps. If you exceed storage, writes start returning 403 Forbidden. If you exceed bandwidth, reads start returning 403 Forbidden. Existing data is preserved — upgrade to a paid plan and full access is restored. The free-tier plan is never converted into an overage charge without your explicit upgrade.
On a paid plan, the per-month free amounts (1 M Class A, 10 M Class B, plus the included storage in your tier) are deducted from your usage at the end of the cycle. Anything above is billed at the overage rates above. Operations are not capped; they continue serving requests and accumulate charges.
Is there volume pricing for very large workloads?
Yes. For multi-petabyte workloads or commitments above the published tiers, contact hello@filebase.com for an Enterprise quote. Volume pricing typically includes a lower per-GB storage rate, dedicated support, and contractual SLA terms.
How do I downgrade or cancel?
To downgrade from Pro back to the free tier, switch on the Billing page. The change takes effect immediately and free-tier limits apply from that point forward.
To cancel entirely, account usage must be ≤ 5 GB. See closing your account for the full procedure.
What's next
- Service limits — rate limits, plan limits, object size limits.
- Bandwidth — what counts as egress and how the dashboard breaks it down.
- Migrate from AWS S3 — the two-line code change plus a worked data migration.
- FAQ — broader account, API, and tooling questions.