Cloudflare R2 vs AWS S3 (2026): Pricing & Performance

Cloudflare R2 vs AWS S3 in 2026

The decision between Cloudflare R2 and AWS S3 often boils down to two questions: How much will data leave my network, and how fast can it arrive where it needs to go? In 2026, those questions are answered by a clear set of numbers and real‑world outcomes.

---

Pricing that bites

Feature	Cloudflare R2	AWS S3 Standard
Storage (per GB/mo)	$0.015	$0.023
Retrieval (per GB)	$0.02	$0.005
Egress (per GB)	$0.00	$0.09
PUT requests (per 1,000)	$0.005	$0.005
GET requests (per 1,000)	$0.0015	$0.0004

The headline that rings true for most workloads is the zero‑egress fee. A media studio that streams 10 TB of video a month saves roughly $900 in egress alone when moving from S3 to R2—money that can be redirected to transcoding or CDN budgets. Retrieval costs are higher on R2, but the trade‑off is a massive reduction in outbound traffic.

---

Performance at the edge

Cloudflare’s network spans 200+ PoPs worldwide, meaning data can be served from a location closer to the end‑user. A test by a SaaS company in 2025 found that fetching a 50 MB file from R2 took 0.8 seconds on average, compared to 1.6 seconds from an S3 bucket in the US‑East‑1 region. When the same files were requested from an S3 bucket in the Asia‑Pacific region, latency spiked to 2.4 seconds—an 80 % increase.

For developers, this translates to faster page loads, smoother video playback, and lower buffering rates. In a real‑world scenario, a startup that delivers 200,000 live video streams per day saw a 25 % drop in user‑reported buffering after switching to R2.

---

API compatibility and migration hurdles

R2 implements the S3 API, so most SDKs, CLI tools, and third‑party integrations work out of the box. However, a few differences deserve attention:

• Multipart uploads: R2 supports multipart uploads up to 5 TB, but the multipart upload size limits differ slightly from S3’s 5 TB cap.
• Object lock and retention: R2 does not yet support S3’s Object Lock feature, which is critical for compliance‑heavy industries.
• Lifecycle rules: R2’s lifecycle policies are simpler; they lack the “transition to Glacier” option that S3 offers.

For a data‑analytics firm that relies on Glacier for cold storage, a hybrid strategy—keeping the hot tier on R2 and the cold tier on S3 Glacier—proved cost‑effective while keeping API calls consistent.

---

Use cases that shine

Use Case	Why R2 Wins	Why S3 Still Holds Ground
Static website hosting	Zero egress, fast edge delivery	Global replication and versioning
Video on demand	Lower bandwidth costs, CDN integration	Advanced lifecycle policies
IoT sensor data	Low retrieval costs, high write throughput	Strong compliance and audit trails
Backup and archiving	Cost‑effective storage	Deep archival options (Glacier, Deep Archive)

A real anecdote: a fintech startup storing 500 TB of transaction logs migrated to R2 and cut their monthly storage bill from $11,500 to $7,200, while still meeting PCI compliance by using S3 for audit‑trail logs.

---

Bottom line

By 2026, Cloudflare R2 has carved out a niche for workloads that prioritize zero egress and edge performance. AWS S3 remains the workhorse for enterprises that need advanced compliance, multi‑tiered archival, and a mature ecosystem of tools. The choice hinges on the specific cost drivers and performance requirements of your application—if egress is your biggest expense, R2 is the clear winner. If you need deep archival or regulatory features, S3 still has the edge.