Most developers pick S3 by default because it is what they know. That is a reasonable default if you are already deep in the AWS ecosystem, but it costs you real money if your use case is backup archival, high-egress media delivery, or a scrappy startup where every dollar counts.
After writing dedicated deep-dives on each provider, here is the hub article: a decision framework that tells you exactly which provider to use based on four real-world use cases. No hedging. No "it depends." Specific recommendations with the numbers behind them.
The Pricing Landscape at a Glance
Before getting into use cases, here is what you are actually choosing between. These are April 2026 prices. Storage cost is the floor; egress is where bills diverge sharply.
| Provider | Storage / GB | Egress / GB | Free Egress | API Compat. |
|---|---|---|---|---|
| AWS S3 | $0.023 | $0.09 | None | Native |
| DigitalOcean Spaces | $0.020 | $0.01 | 1 TB / month Best | S3-compatible |
| Backblaze B2 | $0.006 | $0.01 | Free via Cloudflare Best | S3-compatible |
| Vultr Object Storage | $0.010 | $0.01 | 250 GB / month | S3-compatible |
The S3-compatible API matters more than most people realize. Every provider except AWS native S3 implements the S3 API, which means you can migrate with a credential swap and an endpoint change. Your application code stays identical. That removes a major switching cost from the equation.
At zero egress (internal backup, archival, rarely-accessed data), B2 is cheapest at $0.006/GB. At moderate egress under 1TB/month, Spaces wins on bundled value. At high egress routed through Cloudflare CDN, B2 + Cloudflare is essentially free for bandwidth. The use case determines the winner.
Use Case 1: Backup and Archival
Winner: Backblaze B2
If you are storing database dumps, server snapshots, log archives, or any data you write once and rarely read, storage price is almost the entire bill. You are not paying egress because you are not retrieving the data regularly.
At $0.006/GB, B2 is roughly 74% cheaper than S3 at $0.023/GB. On 10TB of backup data that is $60/month on B2 versus $230/month on S3. That gap compounds over years. There is no compliance reason to use S3 for internal backups unless you have a specific regulatory requirement that mandates it.
Rclone, Restic, and Duplicati all have native B2 support. Migration from S3 is a configuration change. The full B2 vs S3 breakdown covers the egress math in detail if you want to stress-test the numbers.
B2 has fewer regions than S3. If your regulatory or data residency requirements specify a specific geography, verify B2 has a compatible region before committing. S3's 33 regions are unmatched by any competitor.
Use Case 2: Static Website Assets and CDN
Winner: B2 + Cloudflare or Spaces, depending on your CDN setup
Serving images, fonts, JavaScript bundles, and video from object storage is one of the most common developer workflows. The bill is driven by egress, not storage. This is where CDN integration becomes the critical variable.
Backblaze B2 is part of Cloudflare's Bandwidth Alliance, which means egress from B2 to Cloudflare is completely free. If you are already using Cloudflare for DNS or DDoS protection, adding B2 as your origin costs you only $0.006/GB in storage. Bandwidth is zero. For media-heavy applications this is the cheapest possible architecture.
If you prefer DigitalOcean's ecosystem or you want a simpler setup without Cloudflare in the mix, Spaces is the cleaner choice. The 1TB/month free egress handles most small to mid-size applications, and Spaces CDN is built in with a few clicks. The $25/month base plan (250GB storage + 1TB egress) is predictable pricing with no surprise bills.
The Spaces vs S3 comparison walks through the crossover point where Spaces becomes cheaper than S3 at various storage and traffic levels.
Use Case 3: Application Data Storage in the AWS Ecosystem
Winner: AWS S3
This is the one case where S3's higher price is justified. If your application runs on EC2, Lambda, ECS, or any other AWS service, S3 intra-region data transfer is free. You are not paying $0.09/GB to move data from S3 to your application; it stays inside AWS and costs nothing.
Beyond free internal transfer, S3 integrates with IAM roles, CloudTrail audit logging, S3 Object Lock for WORM compliance, lifecycle policies, Intelligent-Tiering, Glacier, and dozens of other AWS services. No competitor touches this depth of ecosystem integration.
If you need SOC 2 Type II, PCI DSS, HIPAA, FedRAMP, or ISO 27001 compliance documentation, S3 has it. AWS publishes compliance reports via AWS Artifact. Your auditors know AWS. That organizational friction is real cost even if it does not show up on an invoice.
The S3 pricing deep-dive covers the full tier structure, request costs, and how to use Intelligent-Tiering to automate cost optimization without changing your access patterns.
S3 Event Notifications, SQS triggers, Lambda integrations, Athena queries over S3 data, and Macie for data classification: these all require S3. If your architecture depends on any of these, S3 is not a preference but a requirement. Price-shop everything else, but keep application data in S3 when you are AWS-native.
Use Case 4: Startup or Dev Team Watching Costs
Winner: DigitalOcean Spaces or Vultr Object Storage
Early-stage teams need predictable bills, simple tooling, and zero surprise charges. S3 can produce genuinely shocking invoices from request costs, replication fees, data retrieval from wrong storage classes, and egress you did not plan for. This catches developers who are not yet familiar with S3's full pricing model.
Spaces at $25/month is a flat-rate product. You get 250GB storage and 1TB egress. The CDN is included. S3-compatible API means you can migrate out to S3 later if you outgrow it or need AWS compliance features. Spaces is what I would give to a junior developer or a new project without hesitation.
Vultr Object Storage at $0.01/GB with 250GB free egress is the option if you are already running compute on Vultr. The same S3-compatible API applies. Internal transfer between Vultr compute and Vultr Object Storage is fast and cheap. For a small team already using Vultr for VMs, co-locating storage on the same provider simplifies billing and reduces latency.
The S3 alternatives overview covers a broader set of providers if neither Spaces nor Vultr fits your constraints.
The Four Use Cases Side by Side
The One Rule That Simplifies Everything
Egress volume is the deciding variable in every object storage decision. Run through this logic before picking a provider.
If your data almost never leaves storage (backups, cold archives), pick the cheapest storage price, which is B2 at $0.006/GB. If your data gets served frequently and you are using Cloudflare CDN already, B2's Bandwidth Alliance makes egress cost zero, which is the best possible outcome. If you need AWS ecosystem depth or compliance documentation, S3's premium is justified. For everything else, Spaces or Vultr give you S3-compatible simplicity with more predictable pricing than AWS.
The decision matrix is not complicated once you know your egress pattern. Run the numbers against your actual usage before assuming S3 is the right default.
Every S3-compatible provider means you can start on Spaces or B2 and migrate to S3 later if you need it. The switching cost is low: update your endpoint URL and credentials, run a one-time sync with rclone or aws s3 sync, and update your app config. Do not pay for S3 features you do not need yet.