StackSays
Menu
Decision toolsCompareCategoriesPricing dataMethodologyBuild my stack

Object Storage · billing diagnostic

Why is your object storage bill high?

Direct answer

A object storage bill almost always climbs from a metered unit crossing its free allowance — most often stored data or egress. Check the drivers below in order (biggest lever first), compare each against your plan's free tier in the vendor console, and look for a sudden usage change. These are the common causes, not a reading of your specific invoice.

The usual cost drivers — check in this order

Every provider in this category meters these. Past the free allowance, each is billed per unit — so a spike in any one moves the bill.

  • ·stored data — total bytes at rest in the bucket. This is a metered unit: past the free allowance you pay per stored data.
  • ·egress — data served out to users — the number that quietly wrecks S3 bills. This is a metered unit: past the free allowance you pay per egress.

Tool-specific cliffs (from verified pricing risks)

Documented ways each tool's bill jumps — verify against your own plan and usage.

  • ·Cloudflare R2: Class A operations (writes/lists) cost $4.50/million and Class B (reads) $0.36/million beyond the free tier — heavy small-object workloads add ops cost we don't model here
  • ·Tigris: Class A requests $0.005/1000, Class B $0.0005/1000 beyond free tier — not modeled here
  • ·Backblaze B2: Egress here is modeled at the direct-download rate ($0.01/GB); in practice the first 3x your monthly storage is free, and egress via CDN partners (Cloudflare, Fastly, bunny.net) is unlimited free — so our egress cost is a conservative ceiling
  • ·Bunny Storage: Storage-to-CDN traffic is free but the CDN bandwidth to end users is a separate Bunny bill not modeled here
  • ·Wasabi: 1TB minimum: storing under 1TB still bills the full $7.99 — the worst value at small scale
  • ·AWS S3 Standard: Egress at $0.09/GB is the reason people migrate off S3 — at 2TB/month that alone is ~$171 vs $0 on R2/Tigris
  • ·Supabase Storage: The $25 Pro fee buys the ENTIRE Supabase platform (database, auth, etc.), not standalone storage — only cost-competitive if you already want Supabase

Where to check in your vendor console

  • ·Open the usage/billing dashboard and find the line item that grew — it names the metered unit.
  • ·Compare current usage to your plan's free allowance (the free-tier caps on that tool's pricing page).
  • ·Look for a step change vs a gradual climb: a step usually means a plan change, a new feature, or crossing a free-tier cliff.
  • ·Check egress/bandwidth and idle/always-on resources separately — they're common surprises the headline price hides.

These are the common causes for this category, not a diagnosis of your specific bill. Confirm in your vendor's usage dashboard, and contact vendor support if the numbers still don't add up. Prices and free tiers change — check the dated sources below.

FAQ

What usually makes a object storage bill spike suddenly?

A sudden jump is most often a metered unit (stored data, egress) crossing the free-tier cap, a plan change, or a new feature — a step change rather than a gradual climb.

Can StackSays tell me my exact bill cause?

No — only your vendor's usage dashboard shows your actual usage. This page lists the likely causes and where to verify each; it never claims to read your invoice.

Official sources

Next decision

Which object storage should I use? →