Cloudflare CDN Pricing in 2026: Real Cost per GB

The most misunderstood line in Cloudflare CDN pricing is the one that says $0. Standard proxied HTTP and HTTPS delivery is not metered by gigabyte on self-serve plans, which means a cache-heavy site pushing 8 TB a month on the $20 Pro plan is paying roughly $0.0025 per GB. That is genuinely hard to beat. The catch, as of 2026, is that almost nobody runs a pure cache-hit workload anymore, and the products bolted around the cache — Argo, Workers, R2 operations, Images, Stream, Spectrum, Logpush — are all metered. This article gives you the effective-cost formula, the 2026 add-on rate card, a worked bill for three realistic workloads, and the volume thresholds at which a per-TB CDN becomes cheaper.

Cloudflare CDN pricing in 2026: the plan tiers

The self-serve ladder has been stable for several years and remains unchanged going into 2026. What has changed is how much of a typical architecture now sits outside the flat-rate portion.

Cloudflare publishes no hard bandwidth cap on these tiers. It does reserve the right to enforce its terms around disproportionate non-HTML content, and that clause is the one that bites large-file and video workloads. If more than a small fraction of your egress is MP4, ISO, MSI, or segment files, expect a conversation about moving to Enterprise or to Stream. That is the single most common reason engineers start pricing alternatives.

The metered layer: where Cloudflare price per GB stops being zero

These are the 2026 published rates for the products most likely to appear on a delivery-shaped bill. Treat them as list price; Enterprise contracts discount most of them.

• Argo Smart Routing: around $0.10 per GB of proxied traffic on top of your plan, with a $5 monthly floor. On a 5 TB month that is roughly $500 — twenty-five times the Pro plan fee.
• Workers Paid: $5 per month base, then roughly $0.30 per million requests beyond the included 10 million, plus CPU-time billing measured in milliseconds.
• Workers KV: separately metered reads, writes, deletes, list operations and stored-GB.
• R2: approximately $0.015 per GB-month stored, Class A and Class B operation fees, and zero egress. R2 remains the strongest cost argument in the portfolio.
• Cache Reserve: storage priced similarly to R2, plus read and write operations — easy to overlook when you enable it to protect an origin.
• Images: billed on stored images and on transformation volume.
• Stream: roughly $5 per 1,000 minutes stored and $1 per 1,000 minutes delivered.
• Spectrum and Logpush: contract or usage-based, and Logpush volume tends to grow silently with traffic.

How to calculate your real Cloudflare CDN cost per GB

The formula is trivial. The discipline is in populating it honestly.

Effective $/GB = (plan fee + all metered add-ons + origin egress) ÷ total GB delivered to end users

Two terms get dropped constantly. The first is origin egress: whatever your cloud provider charges for cache-fill misses, typically $0.05 to $0.09 per GB on the hyperscalers unless you are inside a bandwidth alliance. At a 92% hit ratio on 100 TB, the 8 TB of misses can cost more than the entire CDN plan. The second is Logpush and observability egress, which nobody models until the invoice arrives.

Three worked examples of Cloudflare CDN pricing in 2026

The pattern is clear. Cloudflare price per GB is excellent when bytes are cheap and requests are few. It inverts when you attach compute to every request, because Workers bills on requests and CPU milliseconds, both of which scale independently of the byte count that your capacity planning is built around.

Failure modes that quietly change your Cloudflare CDN cost

Four patterns show up repeatedly in 2026 bill reviews.

• Argo enabled globally instead of selectively. Argo is priced per GB of all proxied traffic, not per GB of traffic it improved. Enabling it zone-wide on a media-heavy zone is the fastest way to turn a $200 bill into a four-figure one.
• Range requests defeating the cache. Players and download managers issuing many small ranges against uncached large objects generate repeated origin fetches. You pay in cloud egress, not in Cloudflare fees, which is why the problem hides.
• Cache Reserve as an origin-shield substitute. It works, but the read operations against it are metered, and a low-hit-ratio zone will hammer it.
• Vary and cookie-driven cache fragmentation. Every distinct cache key multiplies fill traffic. A single misconfigured Set-Cookie on a static path can drop hit ratio ten points overnight.

Instrument two metrics before you renegotiate anything: cache hit ratio by content type, and requests-per-delivered-GB. The second is the one that tells you whether you have a bandwidth problem or a compute problem, and they have completely different cheapest answers.

Cloudflare CDN pricing vs volume-priced alternatives: the crossover point

Below roughly 20 TB per month with no edge compute, nothing beats a $20 or $200 flat plan. Above about 50 TB of large-file or video egress, the economics change, because you are either on an Enterprise commitment or being asked to move to one, and at that point you are negotiating a per-GB rate anyway. That is the moment to price transparent per-TB delivery.

For that profile — software updates, game patches, VOD libraries, large binaries — BlazingCDN's cost comparison is worth running against your own numbers. It delivers stability and fault tolerance comparable to Amazon CloudFront with a 100% uptime commitment, flexible per-zone configuration and fast scaling under release-day spikes, while costing materially less at volume. Pricing starts at $4 per TB ($0.004 per GB) with a $25 monthly minimum and steps down to $2 per TB ($0.002 per GB) at multi-petabyte volume; Sony is among the clients running on it.

Which CDN fits which workload in 2026

FAQ

Does Cloudflare charge per GB for CDN bandwidth in 2026?

Not for standard proxied HTTP and HTTPS traffic on Free, Pro, Business and most Enterprise agreements. Bandwidth is included in the plan fee. Metered charges appear only when you add Argo, Workers, R2 operations, Images, Stream, Cache Reserve or Spectrum.

What is the real Cloudflare price per GB for a typical site?

A cache-heavy site on Pro delivering 8 TB lands near $0.0025 per GB before origin egress, and closer to $0.005 once cache-miss fill costs are included. Attach Workers to every request and the effective figure typically rises into the $0.01 to $0.03 range, driven by request count rather than bytes.

Will Cloudflare throttle or ask me to upgrade for video delivery?

The terms of service restrict disproportionate use of non-HTML content on self-serve plans. In practice, sustained large-file or video egress triggers a move to Enterprise or to Stream. Budget for that outcome rather than assuming unlimited free bandwidth.

Is Argo Smart Routing worth $0.10 per GB?

Only for latency-sensitive, low-volume, cache-miss-heavy traffic such as APIs and dynamic pages. Enabling it across a zone that also serves large static assets means paying $0.10 per GB on bytes that were already being served from cache at full speed. Scope it with rules rather than switching it on globally.

When does a volume-priced CDN beat Cloudflare on cost?

Broadly above 50 TB per month of large-object egress with no edge compute requirement. At that point per-TB rates in the $2 to $4 range produce a lower and far more predictable bill than an Enterprise commitment plus metered add-ons. Below 20 TB, the flat plans remain the cheaper option.

How do I compare Cloudflare CDN cost against another vendor fairly?

Normalise everything to effective dollars per delivered GB including origin egress, log shipping and any compute charges, then compare against the other vendor's total on the same traffic mix. Comparing sticker plan prices to per-GB rate cards produces the wrong answer almost every time.

Run this benchmark this week

Pull last month's total delivered GB, then divide your full Cloudflare invoice plus your cloud provider's egress line into it. That single number is your real cost per GB, and most teams find it is two to five times the figure they quote internally. Then compute requests-per-delivered-GB: if it is above roughly 20,000, you have a compute-priced workload and should optimise request volume before shopping for bandwidth. If it is below 2,000, you have a bandwidth-priced workload and should be getting per-TB quotes. Post your two numbers to your platform channel and see whether anyone can defend the current architecture.