{"id":1184,"date":"2026-07-02T09:45:50","date_gmt":"2026-07-02T02:45:50","guid":{"rendered":"https:\/\/liveapi.com\/blog\/cloudflare-stream\/"},"modified":"2026-07-02T09:46:20","modified_gmt":"2026-07-02T02:46:20","slug":"cloudflare-stream","status":"publish","type":"post","link":"https:\/\/liveapi.com\/blog\/cloudflare-stream\/","title":{"rendered":"What Is Cloudflare Stream? Features, Pricing, and Alternatives (2026)"},"content":{"rendered":"Reading Time: <\/span> 10<\/span> minutes<\/span><\/span>

Adding video to an app used to mean stitching together an encoder, a storage bucket, a transcoding pipeline, and a CDN \u2014 then keeping all of it running. Cloudflare Stream collapses that stack into a single API and a usage-based bill, which is why so many developers reach for it when they need to ship a video feature quickly.<\/p>\n

Cloudflare Stream is Cloudflare’s managed video platform for uploading, storing, live streaming, and delivering video through the same global network that powers its CDN and security products. You hand it a file or an RTMPS feed, and it handles encoding, adaptive bitrate packaging, playback, and analytics.<\/p>\n

This guide covers what Cloudflare Stream is, how it works under the hood, its full 2026 pricing model, features, advantages, and limitations. You’ll also see how to get started with the API and how Stream compares to alternatives like Mux, Bunny Stream, and API-first platforms \u2014 so you can decide whether it fits your project or whether another approach makes more sense.<\/p>\n

What Is Cloudflare Stream?<\/h2>\n

Cloudflare Stream is a video hosting and live streaming service that handles encoding, storage, adaptive bitrate delivery, and playback through Cloudflare’s global edge network. It gives developers a single API to upload on-demand videos or ingest live streams, then serves them as adaptive bitrate streaming<\/a> over HLS and DASH to any device.<\/p>\n

The product sits inside Cloudflare’s developer platform alongside Workers, R2, and Images. Instead of billing for bandwidth, storage, and compute separately, Stream charges on two simple dimensions: minutes of video stored and minutes of video delivered. Encoding and ingest are free.<\/p>\n

Stream exists because building video infrastructure in-house is expensive and slow. A typical team spends months wiring together an encoding cluster, an origin store, a packaging layer, and a CDN \u2014 and then owns the maintenance forever. Stream abstracts all of that behind REST and GraphQL APIs so a developer can add video without becoming a video engineer.<\/p>\n

Here’s a quick snapshot of what Cloudflare Stream offers:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Attribute<\/th>\nCloudflare Stream<\/th>\n<\/tr>\n<\/thead>\n
Type<\/td>\nManaged video hosting + live streaming API<\/td>\n<\/tr>\n
Ingest (live)<\/td>\nRTMPS, SRT<\/td>\n<\/tr>\n
Upload (VOD)<\/td>\nDashboard, TUS resumable, direct creator uploads, upload from URL<\/td>\n<\/tr>\n
Output formats<\/td>\nHLS, DASH, MP4 download<\/td>\n<\/tr>\n
Codec<\/td>\nH.264 (AAC audio)<\/td>\n<\/tr>\n
Adaptive bitrate<\/td>\nAutomatic (360p\u20131080p)<\/td>\n<\/tr>\n
Player<\/td>\nBuilt-in iframe player + any HLS\/DASH player<\/td>\n<\/tr>\n
Pricing model<\/td>\n$5 per 1,000 minutes stored + $1 per 1,000 minutes delivered<\/td>\n<\/tr>\n
Free tier<\/td>\nNone (ingest and encoding are free)<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

How Does Cloudflare Stream Work?<\/h2>\n

Cloudflare Stream follows the same pipeline whether you send it a recorded file or a live feed: ingest, encode, package, deliver. The difference is where the video comes from and how quickly it needs to reach viewers.<\/p>\n

    \n
  1. Ingest.<\/strong> You upload a video file (up to 30 GB) using the dashboard, the TUS resumable protocol, a direct creator upload URL, or an import from a link. For live, you push an RTMP<\/a>-over-TLS (RTMPS<\/a>) or SRT<\/a> feed from OBS or a hardware encoder to a live input you created via the API.<\/li>\n
  2. Encode.<\/strong> Stream transcodes the source into multiple H.264 renditions \u2014 typically 360p, 480p, 720p, and 1080p. This step is free and happens automatically, with no encoding settings to tune.<\/li>\n
  3. Package.<\/strong> The renditions are packaged into HLS<\/a> and MPEG-DASH<\/a> manifests so players can switch quality levels based on the viewer’s connection.<\/li>\n
  4. Deliver.<\/strong> Video is served from Cloudflare’s edge network in hundreds of cities. Playback happens through the built-in Stream Player, a custom HLS\/DASH player, or native mobile players.<\/li>\n
  5. Record (live only).<\/strong> If you enable automatic recording, a live broadcast is saved as an on-demand video the moment it ends, with DVR-style rewind available during the stream.<\/li>\n<\/ol>\n

    The key architectural detail is that ingest and encoding cost nothing \u2014 you only pay once video is stored and once it’s delivered to a viewer. That pricing shape rewards apps with large catalogs and predictable viewership, and it removes the separate egress fees that make many CDN bills unpredictable.<\/p>\n

    Cloudflare Stream Features<\/h2>\n

    Stream packs a full video workflow into one API. These are the capabilities that matter most when you’re evaluating it for a real project.<\/p>\n

    Live Streaming with RTMPS and SRT<\/h3>\n

    You create a live input through the POST \/live_inputs<\/code> endpoint, get back a stream key, and push to it from any RTMPS or SRT encoder. Stream supports automatic recording to VOD, DVR rewind, simulcasting to YouTube, Twitch, and Facebook, and a beta low-latency HLS mode. Live recordings are capped at seven days.<\/p>\n

    Adaptive Bitrate and Multi-Device Playback<\/h3>\n

    Every upload is encoded into multiple quality levels automatically, so viewers on slow connections get 360p while those on fast ones get 1080p \u2014 with no extra storage charge for the extra renditions. Playback works across the built-in player, hls.js, Shaka Player, Video.js, native iOS AVPlayer, and Android ExoPlayer.<\/p>\n

    The Built-In Stream Player<\/h3>\n

    Stream ships an iframe-embeddable video player<\/a> that works on any domain, whether or not the site runs on Cloudflare. Dropping in the Cloudflare Stream embed code takes a single <iframe><\/code> tag, and the player handles quality switching, captions, and thumbnails out of the box.<\/p>\n

    Signed URLs and Access Control<\/h3>\n

    For private or paid content, Stream generates signed URLs with short-lived tokens. You can require signed access per video, associate videos with a creator ID, and restrict playback by domain. Note that Stream uses token-based access rather than full DRM \u2014 there’s no built-in Widevine<\/a> or FairPlay<\/a> support.<\/p>\n

    Analytics and Webhooks<\/h3>\n

    Server-side analytics expose views per video, geographic breakdowns, per-creator metrics, and real-time live viewer counts through the dashboard and a GraphQL API. Webhooks<\/a> fire on processing-complete and error events so you can automate post-upload workflows.<\/p>\n

    Downloads, Thumbnails, and Captions<\/h3>\n

    Stream can generate downloadable MP4 files for offline viewing, produce still-frame thumbnails and animated GIF previews, and accept caption tracks and additional audio tracks through the API.<\/p>\n

    Cloudflare Stream Pricing<\/h2>\n

    Cloudflare Stream pricing is built on two metered dimensions, which makes it easier to forecast than bandwidth-based billing. According to Cloudflare’s pricing documentation<\/a>, the rates as of 2026 are:<\/p>\n\n\n\n\n\n\n\n\n
    Dimension<\/th>\nPrice<\/th>\nBilling model<\/th>\n<\/tr>\n<\/thead>\n
    Storage<\/td>\n$5 per 1,000 minutes stored<\/td>\nPrepaid, in $5 increments<\/td>\n<\/tr>\n
    Delivery<\/td>\n$1 per 1,000 minutes delivered<\/td>\nPost-paid, usage-based<\/td>\n<\/tr>\n
    Ingest (upload)<\/td>\nFree<\/td>\n\u2014<\/td>\n<\/tr>\n
    Encoding<\/td>\nFree<\/td>\n\u2014<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    A few details shape the real cost of Cloudflare Stream pricing per minute:<\/p>\n