Cloudflare R2 drops the fee for moving data out

The workload

Serving files to end users has historically meant paying twice: once to store the data, and again every time it leaves the network to reach a browser. Cloudflare R2 is an object-storage product built to remove the second charge. The workload it targets is architectural, not administrative: a founder choosing where to store uploads, backups, or static assets must weigh a flat egress-free model against the metered egress this batch documents for AWS CloudFront and the partly-metered model documented for Backblaze B2. Cloudflare's own R2 pricing page, last updated 7 August 2026 and retrieved 16 September 2026, states this choice directly, as verified vendor text: "There are no charges for egress bandwidth for any storage class."

What the documents show

The pricing page's verified figures: Standard storage costs $0.015 per GB-month and Infrequent Access costs $0.01 per GB-month. Operations are billed by class: Class A, writes and list-type calls, cost $4.50 per million requests on Standard and $9.00 on Infrequent Access; Class B, reads, cost $0.36 per million on Standard and $0.90 on Infrequent Access. A free tier applies to Standard storage only: 10 GB-month, 1 million Class A operations, and 10 million Class B operations monthly. The page states the no-egress claim as its own, not a third party's characterisation. A second document, the R2 S3-compatible API reference, adds a verified qualification for migration workload: R2 "implements the S3 API to allow users and their applications to migrate with ease," but states plainly that "Cloudflare has removed some API operations' features and added others," naming gaps including bucket-owner validation headers, ACL permissions, and object locking.

The operating cost

For a workload storing 100 GB on Standard storage with 2 million Class A and 20 million Class B operations monthly, the page's own rates put storage at $1.50, Class A (1 million billable after the free tier) at $4.50, and Class B (10 million billable) at $3.60, roughly $9.60 that month, labelled an estimate built from the stated per-unit prices applied to an illustrative workload. Retrieval of Infrequent Access data carries an additional $0.01 per GB on read or copy, per the same page.

The stop condition

The documents state no data-volume ceiling at which R2 becomes unavailable; pricing is metered indefinitely by the stated rates. Editorially, the stop condition for choosing R2 over an egress-charging alternative is the point at which read volume is high enough that the zero-egress savings exceed any gap in feature compatibility the API document names, a threshold each founder must calculate against their own access patterns.

• Does the app's S3 client library call any operation the compatibility page lists as unimplemented or partial?
• How much of this workload's prior cost was egress fees, and does R2's flat operations pricing beat that specifically?
• Is Infrequent Access storage's lower per-GB price worth its added retrieval fee for this access pattern?

R2's zero-egress claim and its S3-compatibility caveats are both stated in Cloudflare's own documents as retrieved on 16 September 2026; nothing here asserts R2 is a full drop-in replacement for S3 beyond what that documentation itself states.