Cloudflare R2 is the better 2026 choice when egress fees are your main problem, while Amazon S3 is still safer for deep AWS integration, compliance tooling, and mature storage controls. For many teams, the decision is not about raw storage price. It is about what happens when users, apps, or AI jobs start pulling data out at scale.
TLDR: Cloudflare R2 remains highly competitive because it charges about $0.015 per GB per month for storage and does not charge traditional outbound data transfer fees. Amazon S3 Standard is often around $0.023 per GB per month, but egress can add serious cost, such as roughly $900 per month for 10 TB of outbound transfer at common public internet rates. A small SaaS storing 5 TB and serving 20 TB monthly could pay far less on R2 than on S3, assuming its workload does not require AWS-native features.
Cloudflare R2 pricing in 2026: the core numbers
Cloudflare R2 pricing is simple by object storage standards. That is part of the appeal. As of planning for 2026, the public pricing model is generally built around these items:
- Storage: about $0.015 per GB per month.
- Class A operations: about $4.50 per million requests, usually writes, lists, and creates.
- Class B operations: about $0.36 per million requests, usually reads and object retrieval actions.
- Egress: no conventional Cloudflare R2 data transfer fee for serving data out.
- Free tier: typically includes monthly allowances for storage and operations, useful for testing and small projects.
These numbers make R2 especially attractive for media delivery, backups, software downloads, AI datasets, log exports, and user-generated content. The catch is that “S3 compatible” does not mean “identical to S3.” Some AWS-specific workflows, event flows, and controls may need redesign.
Cloudflare R2 vs Amazon S3: where the bill changes
Amazon S3 is still the industry reference point for object storage. It has strong durability, many storage classes, lifecycle rules, replication, event integrations, analytics, inventory tools, and tight links to AWS services. That maturity matters.
But S3 pricing can feel like a puzzle. You pay for storage, requests, retrieval in some classes, replication, management features, and data transfer. Egress is the part that often hurts. A workload that looks cheap during development can become expensive when traffic grows.
A basic comparison for common “hot” object storage looks like this:
- Cloudflare R2: lower storage cost than S3 Standard in many cases and no standard egress fees.
- Amazon S3 Standard: higher storage price, strong AWS integration, and outbound transfer charges.
- Request pricing: S3 and R2 are broadly similar for many simple workloads, though exact operation patterns matter.
- Feature set: S3 wins for advanced enterprise storage features and AWS-native automation.
For example, assume a company stores 10 TB and serves 30 TB per month to customers. On R2, storage would be roughly $150 per month, plus request fees. On S3 Standard, storage alone may be around $230 per month. Add egress, and the S3 bill may move into thousands depending on region and transfer tiers. Honestly, it feels like bandwidth charges are where teams get punished for success.
When Cloudflare R2 makes the most sense
R2 is strongest when objects are read often by users or external systems. If your app hosts images, videos, downloadable files, model assets, or public archives, R2 can cut the part of the bill that grows with popularity.
Good use cases include:
- Image and video delivery behind Cloudflare CDN.
- Backup storage for systems that need predictable outbound costs.
- Static asset hosting for apps, games, and documentation.
- AI and data workloads where files are pulled by many workers.
- Software distribution where downloads exceed stored volume by a wide margin.
R2 also fits teams already using Cloudflare Workers, Pages, WAF, DNS, or CDN. Keeping storage close to that edge stack can reduce operational friction. It can also reduce the number of vendors involved in delivery.
Where Amazon S3 still wins
S3 is not expensive by accident. It is broad, stable, and deeply connected to AWS. If your data pipeline runs on Lambda, Glue, Athena, ECS, EKS, CloudFront, KMS, Macie, Security Hub, and IAM policies, S3 may still be the practical choice.
S3 is often better for:
- Large regulated environments with strict AWS controls.
- Complex lifecycle policies across hot, cool, archive, and deep archive tiers.
- Data lake workloads using Athena, Redshift, EMR, or Glue.
- Multi-region enterprise replication with mature policy controls.
- Teams already standardized on AWS security and monitoring.
Expect to waste time on small compatibility checks if you move from S3 to R2. SDKs usually work, but edge cases matter. Multipart uploads, signed URLs, event triggers, bucket policies, object metadata, and third-party backup tools should all be tested before migration.
Object storage alternatives to compare in 2026
R2 and S3 are not the only serious options. The right choice depends on traffic shape, region needs, vendor risk, and staff experience.
- Backblaze B2: Often attractive for low storage pricing. It is popular for backups, archives, and media workflows. Check download rules and partner integrations before assuming all egress is free.
- Wasabi: Simple pricing and no standard egress fees under fair-use terms. Watch minimum storage duration rules and minimum capacity assumptions.
- Google Cloud Storage: Strong for analytics and Google Cloud workloads. Pricing varies by region, class, operations, and egress.
- Azure Blob Storage: Good for Microsoft-heavy companies. Hot, cool, cold, and archive tiers provide flexibility, but retrieval and transfer charges need careful review.
- DigitalOcean Spaces: Easy for smaller teams and simple apps. Bundled storage and transfer make costs readable, though it may not fit very large enterprise needs.
- Oracle Cloud Object Storage: Worth checking where free outbound transfer allowances and Oracle infrastructure fit the stack.
How to estimate your real monthly cost
Do not compare only the price per GB. That misses the point. Build a simple usage model first.
- Stored data: average TB stored during the month.
- Outbound transfer: TB delivered to users, apps, partners, or other clouds.
- Request volume: PUT, GET, LIST, DELETE, and multipart operations.
- Data pattern: many tiny files can cost more in requests than expected.
- Operational needs: audit logs, replication, encryption, lifecycle rules, and recovery targets.
Here is a practical rule. If outbound transfer is higher than stored data, R2 deserves a serious test. If AWS services process the data constantly, S3 may save engineering time even if the invoice is higher.
Final recommendation for 2026 buyers
Choose Cloudflare R2 if you need S3-compatible object storage with predictable delivery costs and heavy public or cross-cloud reads. It is especially good when egress charges are blocking growth.
Choose Amazon S3 if your storage is part of a larger AWS system, or if you need the richest set of enterprise storage features. The higher bill can be justified when it reduces risk and engineering work.
For most teams, the best move is not a full migration on day one. Start with one bucket, one workload, and one month of measured traffic. Compare the actual bill, latency, error rates, request patterns, and developer effort. The winner will be obvious once real usage replaces estimates.