DEV Community

Juan Diego Isaza A.
Juan Diego Isaza A.

Posted on

Cloudflare R2 vs S3: What to Choose for VPS Apps

#cloud #vps #aws #cloudflare

If you’re pricing storage for a VPS-backed app, cloudflare r2 vs s3 is the comparison that actually moves your monthly bill—often more than your CPU/RAM choices. Object storage looks “cheap” until egress, request fees, and caching patterns show up in production.

The core difference: pricing model (egress is the fight)

The most practical way to frame this is simple: S3 is the default, feature-rich baseline; Cloudflare R2 is the cost-disruptor built around zero egress fees (when used within Cloudflare’s ecosystem).

Where this matters in VPS hosting:

  • Bandwidth-heavy apps: image-heavy sites, video snippets, software downloads, backups served to clients.
  • Global users: when you don’t want to run multiple VPS edge nodes just to avoid cross-region transfer pain.
  • CDN-fronted storage: the moment you put a CDN in front, “egress” becomes a line item you’ll suddenly care about.

In AWS S3, the sticker price per GB stored is only half the story; egress and requests can dominate. R2’s pitch is basically: store objects, serve them globally via Cloudflare, and don’t get punished for success.

Opinionated take: if your workload is predictable and AWS-native, S3 is hard to beat. If you’re running a lean VPS stack and delivering lots of public assets, R2’s egress economics can be a genuine unlock.

Performance and latency from a VPS perspective

For most VPS-hosted apps, the “performance” question isn’t raw object throughput—it’s end-user latency and cache hit rates.

  • S3: You choose regions explicitly. If your VPS is in the same region (say us-east-1) and your users are mostly nearby, it’s consistent and fast. Multi-region setups add complexity (replication, multi-region access points, etc.).
  • Cloudflare R2: Designed to sit behind Cloudflare’s network. If your audience is global and you’re already using Cloudflare for DNS/CDN/WAF, you can get very good perceived performance with aggressive caching.

A realistic VPS pattern:

  • Host app servers on hetzner (great price/performance in EU) or digitalocean (easy managed VPS experience).
  • Put static assets in object storage.
  • Use a CDN in front.

In that pattern, R2 + Cloudflare CDN can reduce surprise costs while keeping latency competitive. With S3 you can achieve similar latency, but you’ll typically pay for the bandwidth leaving S3 unless you engineer around it.

API compatibility and migration friction

This is where the decision often becomes “how much AWS am I already married to?”

  • S3 is the reference implementation. Every tool, SDK, backup product, and CI pipeline assumes S3 semantics.
  • Cloudflare R2 is S3 API-compatible for many operations, which is the whole point: you can often migrate with minimal code changes.

The gotchas are rarely the basic PUT/GET. They show up in edge behaviors and advanced features:

  • Event notifications, lifecycle rules, object lock, and deep IAM patterns may not map 1:1.
  • Some tools assume AWS-specific endpoints or signature edge cases.

If your VPS app is a typical web stack (Node/Python/PHP/Go) storing user uploads, thumbnails, or build artifacts, R2’s S3 compatibility is usually “good enough” to be boring.

Actionable example: configure an S3-compatible client for R2

Here’s a practical snippet using the AWS CLI (common on VPS boxes) to talk to R2 via an S3-compatible endpoint.

# 1) Configure credentials (use your R2 Access Key + Secret)
aws configure set aws_access_key_id YOUR_R2_ACCESS_KEY
aws configure set aws_secret_access_key YOUR_R2_SECRET_KEY
aws configure set region auto

# 2) List buckets via R2 endpoint
aws s3api list-buckets \
  --endpoint-url https://<ACCOUNT_ID>.r2.cloudflarestorage.com

# 3) Upload a file to a bucket
aws s3 cp ./logo.png s3://my-bucket/assets/logo.png \
  --endpoint-url https://<ACCOUNT_ID>.r2.cloudflarestorage.com
Enter fullscreen mode Exit fullscreen mode

Why this matters for VPS hosting: you can keep your deployment scripts the same (S3 tooling) while swapping the backend storage. That makes it easy to A/B cost and performance without a rewrite.

So which should you pick for VPS hosting?

Choose S3 if:

  • You’re deep in AWS already (IAM, CloudWatch, Lambda triggers, policies, compliance checklists).
  • You need mature features and ecosystem integration more than raw cost predictability.
  • Your egress is low (private data, internal services) or you’ve already optimized delivery.

Choose Cloudflare R2 if:

  • Your VPS app serves a lot of public/static content and bandwidth bills are your enemy.
  • You’re already on Cloudflare for DNS/CDN/WAF and want one network boundary.
  • You want “S3-like” without inheriting every AWS pricing lever.

My opinion: for many indie and SMB VPS deployments, R2 is the more rational default in 2026—because cost predictability beats theoretical feature depth you won’t use. S3 still wins when AWS is the platform, not just the storage.

Final note (soft suggestion): if you’re building a VPS stack on hetzner or digitalocean and already routing traffic through cloudflare, R2 is worth a weekend test. Run the same upload/download paths, watch cache hit rate and egress, then decide with real numbers—not assumptions.

Some links in this article are affiliate links. We may earn a commission at no extra cost to you if you make a purchase through them.

Top comments (0)