The word "unmetered" on a Cloudflare pricing page has cost more than one platform team a surprise five-figure quarter. Cloudflare pricing looks flat at the plan level and turns metered the moment your traffic profile stops being a blog. A no-Cloudflare pricing calculator will show you the $25 Pro plan. It will not show you the $0.09/GB egress your cloud provider bills every time a cache miss pulls from origin, and it will not show you where the plan boundary flips your delivery workload into an Enterprise conversation.

This is the calculation, worked. Below you get three volume scenarios modeled with 2026 numbers, a breakdown of which Cloudflare cost line items scale with bandwidth versus requests, the exact points where plan boundaries bite, and an honest comparison against flat-rate delivery once you cross into video, patches, and large-object territory.

How Cloudflare Pricing Actually Bills You in 2026

Cloudflare pricing in 2026 sits on the same four self-serve and Enterprise tiers it has held for years, but the metered add-ons are where forecasts break. The plan fee is the floor. Your real bill is plan fee plus per-unit charges plus the origin egress your cloud provider charges you separately.

• Free: $0/month. Static sites, side projects, standard web delivery.
• Pro: $25/month per domain as of 2026. Adds managed WAF rulesets, Polish image optimization, and mobile tuning.
• Business: $250/month per domain. Adds custom SSL, prioritized support, a 100% uptime SLA, and expanded caching controls.
• Enterprise: Custom. Public reference points and reseller data through 2026 still cluster around a $5,000/month starting commit, rising steeply for contracted bandwidth and premium routing.

The trap is the acceptable-use language attached to "unmetered" delivery. Standard web assets stay unmetered on self-serve plans. Sustained delivery of video, game patches, ISOs, or other large binaries is what pushes Cloudflare to route you toward Enterprise or a licensed product like Stream. If your bytes-per-request average is high and your cache-hit ratio is anything less than excellent, you are the workload that pricing model was written to catch.

Cloudflare cost line items that scale with bandwidth vs requests

Model these two axes separately. They do not move together, and conflating them is the most common forecasting mistake.

Argo at $0.10/GB is the quiet killer. Turn it on for a 40 TB month and you have added roughly $4,000 to a plan that started at $25. It is a real feature with real latency wins, but it converts a flat plan into a per-GB one instantly.

The Cloudflare Pricing Calculator, Worked at Three Volumes

The formula that matters is not on the pricing page. It is this:

Origin-pull volume = total delivery × (1 − cache-hit ratio)

Your Cloudflare cost is the plan fee plus that origin pull multiplied by your cloud's egress rate, plus any metered add-ons you enabled. Here are three profiles using 2026 rates and a $0.09/GB origin egress assumption.

Small: 25 TB/month, 92% cache-hit ratio

Origin pull is 25 TB × 0.08 = 2 TB. At $0.09/GB that is roughly $180. On Business at $250/month, your all-in lands near $430 before any add-ons. Enable Argo and you add another ~$2,300 in routed bandwidth. This is the tier where Cloudflare pricing stays reasonable if you leave the metered features off.

Mid: 100 TB/month, mostly large objects

At 100 TB of sustained large-file delivery, self-serve stops being the right conversation. Even at a strong 90% hit ratio, origin pull is 10 TB, or about $900 in cloud egress alone. Layer in the acceptable-use pressure on video and binaries, and you are negotiating Enterprise. Contracted commits at this volume commonly open near $5,000/month as of 2026, before egress.

High: 500 TB/month

Half a petabyte is negotiated Enterprise territory with committed bandwidth pricing. Origin pull at 90% hit is 50 TB, roughly $4,500 in egress on top of the contract. Total monthly spend at this profile routinely clears five figures once routing and support tiers are added. This is exactly where teams start pricing a second delivery vendor.

Where the Plan Boundaries Bite

Three thresholds change your economics abruptly rather than gradually.

• The workload-type boundary: The moment your traffic is dominated by video or large downloads, "unmetered" no longer applies and you are steered to Enterprise or Stream regardless of raw TB.
• The per-domain boundary: Pro and Business fees are per zone. A portfolio of forty domains on Business is $10,000/month in plan fees alone, independent of any traffic.
• The add-on boundary: Argo and Workers convert a flat plan into a per-GB or per-request bill. At delivery scale, these dominate the invoice and are the single most under-forecast item.

Cloudflare Cost vs Flat-Rate Delivery at Volume

For security-first web apps under ~25 TB, Cloudflare pricing is defensible and the integrated platform earns its fee. For delivery-heavy workloads, the math inverts. A flat committed-rate CDN removes egress surprises and the workload-type penalty entirely.

BlazingCDN prices delivery on committed volume: $100/month up to 25 TB with additional GB at $0.004, scaling down to $2,500/month for 1 PB and $4,000/month for 2 PB, where marginal bytes fall to $0.002/GB. It delivers stability and fault tolerance comparable to Amazon CloudFront with a 100% uptime posture, flexible configuration, and fast scaling under demand spikes, while staying materially cheaper at volume. Media platforms including Sony run delivery on it, which is why teams shipping large libraries evaluate the media delivery pricing model before renewing an Enterprise CDN contract.

Which Model Fits Your Profile

• Under 1 TB: Cloudflare Free. No calculation needed.
• 5–25 TB, security-driven web apps: Cloudflare Pro or Business, add-ons audited monthly.
• 50 TB+ of video, patches, downloads: Flat-rate delivery. This is the crossover point in 2026.
• 100 TB to petabytes: Multi-CDN with committed rates and a delivery-specialist as primary.

FAQ

Is Cloudflare bandwidth really unmetered in 2026?

For standard web assets on self-serve plans, yes. For sustained video, game patches, or large-file delivery, the acceptable-use policy steers you to Enterprise or a licensed product. The unmetered promise applies to workload type, not raw byte count.

What is the biggest hidden Cloudflare cost?

Origin egress billed by your cloud provider on every cache miss, followed by Argo Smart Routing at $0.10/GB. Neither appears in the plan fee, and both scale directly with traffic. Model them separately before you commit.

How do I calculate my real Cloudflare cost?

Take total monthly delivery, multiply by one minus your cache-hit ratio to get origin pull, then multiply that by your cloud egress rate. Add the plan fee and any enabled metered add-ons. That sum, not the plan sticker price, is your forecast.

At what traffic volume does Cloudflare stop being cost-effective?

For delivery-heavy workloads the crossover appears around 50 TB/month in 2026, where flat-rate CDNs become both cheaper and more predictable. Below that, the integrated security platform often justifies the fee.

Does a higher cache-hit ratio actually lower my bill?

Directly. Moving from an 85% to a 92% hit ratio on 40 TB cuts origin pull from 6 TB to 3.2 TB, roughly halving your egress line. Cache-hit ratio is the single most leveraged number in the entire model.

Run This Before Your Next Renewal

Pull 30 days of Cloudflare Analytics and lay it beside your cloud egress bill. Compute cache-hit ratio per route, not as one blended figure, and find the routes dragging your average down. Model a release-day spike with cache collapse and see whether Argo or Workers charges would breach your budget. Then price the same delivery volume against a flat committed rate. If your crossover math lands above 50 TB/month, the highest-ROI ticket you can file this quarter is a delivery-vendor evaluation. What is your cache-hit ratio on your heaviest route right now, and what would a five-point improvement save you?