Cloudflare R2 Pricing in 2026: What You Actually Pay

Cloudflare markets R2 on one word: egress. There are no fees to move your data out, ever, on any storage class. That single line is why teams migrate off Amazon S3, and it is also why the R2 bill confuses people. When the biggest line item on every other object store disappears, the costs that are left over, operations and storage, suddenly dominate. And those are the ones nobody budgets for.

This is the arithmetic behind Cloudflare's R2 pricing page, current as of July 2026, with three real 30-day bills and the operations trap that generates threads titled "does Cloudflare really charge $9.00 for a single R2 request?"

Cloudflare R2 is an S3-compatible object storage service that charges for stored data and for operations, but never for egress bandwidth. That last part is the whole pitch, and it changes how you budget.

What Cloudflare R2 costs in 2026

R2 has two storage classes, Standard and Infrequent Access, and bills three things: storage, Class A operations (writes, lists, most mutations), and Class B operations (reads). Egress is free on both classes. Here is the full rate card, verbatim from the pricing page in July 2026.

Two details on that table matter more than the headline numbers. First, Infrequent Access halves your storage rate but doubles both operation rates and adds a retrieval fee. Second, Cloudflare rounds usage up to the next billing unit. Do 1,000,001 Class A operations and you are billed for two million. That rounding, not a per-request charge, is what the "$9 for a single request" threads are actually describing: on Infrequent Access, one million Class A operations cost $9.00, and if you trip one operation into the next million, you buy the whole next million.

The free tier covers more than you think

Every R2 account gets a permanent monthly free allowance on Standard storage: 10 GB stored, 1 million Class A operations, and 10 million Class B operations. For a side project serving a few thousand files, that is often the entire bill: zero. The free tier is why R2 feels free at small scale and then surprises you exactly when your writes cross one million a month.

Why your R2 bill is operations, not gigabytes

On S3 you learn to think in terabytes because egress is priced by the gigabyte and it dwarfs everything else. R2 removes that line, so the mental model has to change. Storage is cheap ($0.015/GB-month is $15 per terabyte). The bill is usually dominated by Class A operations, because every upload, overwrite, and multipart part counts, and they are the most expensive meter by far at $4.50 per million.

A useful reframe: R2 charges you for touching objects, not for holding them or for serving them. Hold a petabyte and read it a billion times over free egress, and you still only pay storage plus the read operations. Rewrite ten million small objects every night and the storage is a rounding error next to the Class A bill. It is the same trap as any usage-metered infra bill; we walked through the hosting version in our Vercel pricing teardown.

Standard vs Infrequent Access: when IA actually wins

Infrequent Access looks cheaper because the storage rate is a third lower. It is a trap for the wrong workload. IA doubles Class A operations to $9.00 per million, doubles Class B to $0.90 per million, adds a $0.01/GB retrieval fee, and charges a 30-day minimum storage duration even if you delete an object after a day.

IA wins only when data is genuinely cold: written once, read rarely, kept for at least a month. Think compliance archives, old backups, raw logs you might never touch. The moment a workload writes often or reads often, IA costs more than Standard, not less. Bill 3 below shows exactly how badly that goes.

Three real 30-day bills

Prices are the July 2026 rate card. S3 comparison figures use the widely cited economics from Last Week in AWS: roughly $0.023/GB-month S3 Standard storage and about $0.088/GB egress ($23 and $90 per terabyte). AWS rates vary by region and tier, so confirm current numbers on the AWS S3 pricing page.

Bill 1: an image and asset host (egress-heavy)

A SaaS storing user uploads: 100 GB stored, 5 million writes a month, 40 million reads a month, and 2 TB served to browsers.

• Storage: (100 - 10 free) = 90 GB x $0.015 = $1.35
• Class A: (5M - 1M free) = 4M x $4.50 = $18.00
• Class B: (40M - 10M free) = 30M x $0.36 = $10.80
• Egress (2 TB): $0.00
• R2 total: about $30.15/month

The same workload on S3: about $2.30 storage, plus roughly $171 in egress on the 2 TB (after the first 100 GB free), plus request fees on top. Call it $173-plus before requests. The R2 bill is about $30, the S3 bill is about $175, and the entire $145 gap is one line: egress. On R2 that line is zero, so your cost collapses to operations.

Bill 2: a cold backup (write-once, rarely read)

A 2 TB offsite backup: 2,000 GB stored, 50,000 writes, 200,000 reads, 50 GB pulled back in a month.

Here is the honest part: R2 is not the cheapest place to park cold data. Backblaze B2 stores at $6.95 per terabyte-month (about $0.007/GB), keeps Class A/B/C transactions free, and only bills egress past three times your stored volume. For a 2 TB archive that rarely moves, B2 is less than half the price of R2 Standard. R2 earns its premium when egress is uncapped and unpredictable; for a quiet backup it is not the low bidder. If your files live behind an app database instead, the same egress math drives Supabase's storage pricing.

Bill 3: a write-heavy pipeline (the operations trap)

A nightly job writing 3 million small objects a month into a 200 GB bucket, read rarely. Someone reads "IA storage is cheaper" and switches the bucket to Infrequent Access to save money.

• On IA: storage 200 x $0.010 = $2.00; Class A 3M x $9.00 = $27.00. Total about $29/month, and 93% of it is operations.
• On Standard: storage 200 x $0.015 = $3.00; Class A (3M - 1M free) = 2M x $4.50 = $9.00. Total about $12/month.

Switching to IA to shave a dollar of storage more than doubled the bill, because IA doubles the operation rate and this workload is nothing but operations. IA is for data you write once and barely touch, never for a churny pipeline.

R2 vs S3 vs Backblaze B2 at a glance

Cloudflare R2, Amazon S3, and Backblaze B2 solve the same job with three different pricing philosophies.

The pattern: S3 is priced for you to stay (egress is the moat), R2 is priced to serve (free egress, pay for writes), and B2 is priced to store (cheapest bytes, capped free egress).

The cheaper-lever cheat sheet

• Egress-heavy (images, video, downloads, public assets): R2 Standard, no contest. Free egress is worth more than any storage discount, and R2 storage undercuts S3 too.
• Cold archive that rarely moves: price Backblaze B2 first. It usually wins on storage; R2 only pulls ahead if your egress is large or spiky.
• Write-heavy or many small objects: budget for Class A operations, not gigabytes. Batch writes, avoid tiny objects, and do not switch to Infrequent Access.
• Genuinely cold, read-rarely data: Infrequent Access, but only if objects live at least 30 days and reads are truly infrequent.
• Watch the rounding: operations round up to the next million. A job that trips just over a million pays for the whole next million.

R2's free egress is real and it is the reason to choose it. Just remember that removing the egress line does not make the bill zero. It moves the bill onto operations, and that is the number you now have to watch.

Math check: the egress-heavy asset host costs about $30 on R2 versus about $175 on S3, and every dollar of the $145 gap is egress you no longer pay. Budget R2 by operations, not gigabytes.