Cloudflare Stream Pricing 2026: Live & VOD Cost Breakdown

At $1 per 1,000 minutes of stored video and $5 per 1,000 minutes of delivered video, Cloudflare Stream pricing looks deceptively simple. But once you layer in live input minutes at $0.75 per 1,000, SRT/RTMPS ingest overhead, and the hidden multiplier of adaptive bitrate renditions on your storage bill, that simplicity evaporates fast. A mid-size VOD library of 50,000 minutes with moderate delivery can clear $350/month before you touch a single live event. This article gives you the exact cost model, a head-to-head comparison with the alternatives that matter in 2026, and a workload-profile decision matrix you will not find in the Cloudflare docs or anywhere else in the current top 10 results for "cloudflare stream pricing."

Cloudflare Stream Pricing Model as of Q2 2026

Cloudflare Stream operates on a consumption-based model with three billable axes. There are no tiers to choose between and no bandwidth charges in the traditional CDN sense. Every Cloudflare account with Stream enabled pays against these meters:

The $5 subscription plan that bundles 1,000 storage minutes and 5,000 delivery minutes is still available as of Q2 2026 and serves as a useful sandbox. But it caps out quickly; exceeding those included minutes rolls into the per-unit rates above with no volume discount unless you negotiate an enterprise contract directly.

Where Cloudflare Stream Cost Actually Spikes

Storage Multiplier from Transcoding

When you upload a 60-minute 4K source, Cloudflare transcodes it into multiple ABR renditions (typically 360p, 480p, 720p, 1080p, and sometimes 1440p). Each rendition counts against your storage minutes. A single 60-minute upload can register as 240–300 stored minutes depending on the rendition ladder. That $5 per 1,000 minutes adds up faster than the headline rate suggests.

Live Input Minutes During Idle Streams

If your encoder stays connected between segments of a multi-hour broadcast — commercials, halftime, green-room holds — you are still accruing live input minutes at $0.75/1,000. A 24/7 live channel consumes roughly 43,800 input minutes per month ($32.85 in input alone) before a single viewer joins.

Delivery at Scale

Delivery at $1 per 1,000 minutes sounds modest until you run the numbers on a live event. 10,000 concurrent viewers watching a 90-minute stream equals 900,000 viewed minutes, or $900 in delivery for a single broadcast. Scale that to 50,000 concurrent viewers and you are looking at $4,500 per event in delivery charges alone.

Cloudflare Stream Live vs VOD Pricing Breakdown

The economic profiles of live and VOD workloads diverge sharply on Cloudflare Stream. Here is what the monthly bill looks like for two representative workloads modeled at May 2026 rates:

Live delivery dominates the bill. VOD is storage-heavy but delivery-cheap at moderate viewership. If you are running both workloads, the combined cost can justify evaluating whether your delivery layer needs to live entirely inside Cloudflare Stream or whether a dedicated CDN handles the byte delivery more economically while Stream handles encoding and player logic.

Workload-Profile Decision Matrix

This is the section missing from every comparison currently ranking for cloudflare stream pricing. Instead of asking "which plan?" ask "which architecture?" The answer depends on four variables: ingest volume, library size, peak concurrency, and geographic viewer distribution.

The hybrid pattern — Cloudflare Stream for transcoding and player embed, an external CDN for high-volume byte delivery — is increasingly common in 2026 among teams running OTT or e-learning platforms at scale. It preserves Stream's developer experience while capping delivery spend.

How Cloudflare Stream Cost Compares in 2026

Direct apples-to-apples comparison is difficult because AWS MediaLive + CloudFront, Mux, and api.video each meter differently. But for a normalized workload of 100,000 delivery minutes and 10,000 stored minutes per month, approximate costs as of Q2 2026:

• Cloudflare Stream: ~$150 ($50 storage + $100 delivery)
• Mux: ~$170 (encoding fees + per-minute delivery at similar rates, plus asset storage)
• api.video: ~$99 on their Scale plan, but capped at 100 hours of encoding; overages add up
• AWS (MediaConvert + S3 + CloudFront): ~$80–$200 depending on region and Reserved Capacity commitments, but requires significantly more operational overhead

Cloudflare Stream wins on developer simplicity. The single-API upload-to-playback pipeline with built-in player, analytics, and token-based access control eliminates the glue code required in AWS. The trade-off: you have zero control over the transcoding ladder, cache behavior, or delivery topology.

For teams that need delivery cost control at higher volumes — particularly above 500 TB/month of video egress — a purpose-built CDN layer becomes essential. BlazingCDN's media delivery infrastructure offers volume-based pricing that scales from $4/TB at 25 TB down to $2/TB at the 2 PB tier, with 100% uptime SLA and fast scaling under demand spikes. For context, delivering 500 TB through a traditional cloud CDN might cost $10,000–$20,000/month; the same volume through BlazingCDN runs approximately $1,500/month. That delta funds a lot of engineering hours.

What Changed in 2026

• LL-HLS default: Cloudflare Stream now defaults to Low-Latency HLS for live inputs, reducing glass-to-glass latency to under 3 seconds for most configurations without requiring WebRTC fallback.
• SRT ingest GA: SRT input endpoints exited beta in early 2026, giving you a reliable alternative to RTMPS for ingest over lossy networks.
• Clip and trim API: Non-destructive clip creation no longer duplicates stored minutes — a meaningful storage cost reduction for teams that create highlights from long-form content.
• Creator-level analytics: Per-video and per-creator analytics are now available via GraphQL, making internal chargeback models viable for multi-tenant platforms.

FAQ

How much does Cloudflare Stream cost for live streaming per event?

A live event costs $0.75 per 1,000 input minutes plus $1 per 1,000 viewed minutes. A 2-hour event with 5,000 concurrent viewers generates roughly 600,000 viewed minutes ($600) and 120 input minutes ($0.09). Delivery is the dominant expense; input costs are negligible.

What is Cloudflare Stream pricing per 1,000 minutes delivered?

Delivery is $1 per 1,000 minutes viewed, regardless of resolution. This rate applies uniformly to both live and VOD playback as of Q2 2026. There is no volume discount on the self-serve plan; enterprise contracts may negotiate lower rates.

Does Cloudflare Stream charge for ABR storage renditions separately?

Yes. Every rendition Cloudflare creates during transcoding adds to your stored minutes. A 60-minute source uploaded at 1080p typically generates 4–5 renditions, so your stored minutes for that asset will be 240–300 minutes, not 60. This is the most commonly misunderstood aspect of cloudflare stream pricing.

Can I use Cloudflare Stream for encoding and a different CDN for delivery?

Not natively. Stream's playback URLs resolve through Cloudflare's network, and there is no "bring your own CDN" option for delivery. The hybrid approach requires pulling the HLS manifest and segments from Stream's URLs via your external CDN as a proxy origin, which some teams do, but it is unsupported and may break if Cloudflare changes URL structures or token validation.

How does Cloudflare Stream compare to Mux on cost?

At low volumes (<50,000 delivery minutes), Mux and Stream are within 15–20% of each other. Mux's encoding fees make it slightly more expensive for upload-heavy workflows, while Stream's storage-minute model penalizes large catalogs. Above 500,000 delivery minutes per month, both become expensive enough that offloading delivery to a dedicated CDN is worth evaluating.

Is there a free tier for Cloudflare Stream?

No. The entry point is the $5/month subscription that includes 1,000 storage minutes and 5,000 delivery minutes. There is no free trial or freemium plan as of May 2026.

Run the Numbers This Week

Pull your last 30 days of Stream analytics from the Cloudflare dashboard. Export stored minutes, delivered minutes, and live input minutes. Drop them into a spreadsheet against the rates in the table above and compare the total to what you would pay on a per-GB CDN model using your actual bitrate distribution. If your delivery bill exceeds your storage bill by more than 10x, you have a workload that benefits from separating encoding from delivery. If storage dominates, audit your rendition ladder — you may be paying for 360p renditions that no viewer ever selects. Either way, the five minutes of spreadsheet work will tell you whether you are on the right architecture or leaving money on the table.