Lifestyle

Cloudflare open-sources Streamline: a demo of using its cloud services to add graphics to live streams and burn subtitles into videos

On October 2, 2026, Cloudflare launched and open-sourced Streamline, a developer playground showing how developers can combine Stream, Workers, Containers and Durable Objects to build their own video processing pipelines, such as adding graphics to live streams in real time or adding subtitles to videos. This article explains what it is, how it works, its limitations, and what it means for viewers and developers.

About 7 min read

Cloudflare open-sources Streamline: a demo of using its cloud services to add graphics to live streams and burn subtitles into videos
Image: Mokaair (Original editorial artwork)

What Cloudflare announced

Cloudflare published a blog post on October 2, 2026, written by Willi Geiger and Taylor Smith. In it, the company says it has launched a developer playground called Streamline. Cloudflare notes that its Stream platform (Cloudflare's service for live streaming and video hosting) "just works" for many customers. Some tasks need more, such as drawing dynamic annotations on a live stream in real time, or producing a version of an uploaded video with burned-in subtitles (subtitles composited directly into the picture). These require a custom video processing pipeline, meaning a sequence of steps that process video in order. Streamline was designed to demonstrate exactly these kinds of needs.

Cloudflare says it has released Streamline as open source (publicly available code that anyone can view and use) on its GitHub. The code is split into two repositories: the media engine, cloudflare/streamline, and the demo app, cloudflare/streamline-demo. Cloudflare has also deployed a public demo for developers to try.

How Streamline works

According to Cloudflare, the system has two main parts. A "media engine" handles video input, output and processing. A "control app" creates, configures, observes and stops processing sessions (a session is a single video processing job). The media engine runs in Containers, which Cloudflare describes as a long-running execution environment suited to media processing. Inside the engine are a controller written in Go and a processor that does the actual video work. Cloudflare notes the processor currently uses FFmpeg, but says this is an internal implementation detail. The control app is built on Workers (Cloudflare's cloud code execution service, used here to send control commands and to monitor). Durable Objects, a Cloudflare component that helps with orchestration, coordinates sessions, container lifecycles and preview relaying.

Cloudflare says the media engine can pull a live stream from one Stream Live input over RTMPS (a common live streaming transport protocol) and output it to another Stream Live input. It can also read Cloudflare Stream HLS (HTTP live streaming) manifests to use a hosted video as a source, or receive webcam video sent by the control app. The processed result can be output as a live stream. It can also be sent back as fMP4 video segments over WebSocket (a technology that keeps an app connected to a server for continuous data transfer) to give a low-latency preview.

  • filter: apply filters, such as blur or saturation
  • overlay: overlay images, including PNG annotation layers that can be updated while running
  • subtitle: burn subtitles into the picture
  • encode: set output encoding parameters

Cloudflare adds that the engine currently fixes the order in which these operations run. Another key design point is that once a session has started, the controlling app can disconnect and reconnect safely, and the container keeps processing until it is stopped. The system also has a maximum run time, so sessions cannot run indefinitely.

Comparing the three operating modes

Streamline operating modes, compiled from Cloudflare's blog post
ModeAccess controlSession limitsCloudflare's description
Local developmentNo authorization needed for local accessSingle userContainer is local Docker, no Durable Object is used, and preview connects directly to a local WebSocket
Owner deploymentKept private through Workers' Access integrationOnly one session at a time; others cannot stop or replace itDeliberately private; not a security model for a public multi-user service
Public demoUses its own Access configurationOne container identity and one active session per verified userHas global admission control, plus concurrency, media and session limits

Security design and current limitations

Cloudflare says security is part of the design. Only authorized users can create or take over sessions, sessions are isolated from one another, and resource usage is bounded. According to the company, Stream Live Input keys are stored either in Worker secrets or as write-only shared overrides in Durable Object storage. They are never returned by the settings API and are never placed in browser storage.

On limitations, Cloudflare admits the current version processes media on Container CPUs, which becomes a bottleneck at higher resolutions or frame rates. The company says it hopes to extend the architecture with the developer community. Its goals include computer vision pipelines, hardware-accelerated processing, and next-generation real-time protocols such as WebRTC and MoQ, and ultimately native video encoding and decoding in Workers.

What it means for general readers and developers

For ordinary viewers, tools like this could mean more live streams and online videos with real-time processing, such as live subtitles, dynamic graphics or picture-in-picture. Cloudflare also mentions other uses, such as sending factory camera feeds for AI analysis or combining several camera feeds into a single picture. However, this is still a demo project. Whether it catches on depends on developer adoption and future performance improvements.

For developers, according to Cloudflare, the demo app uses an Astro front end to showcase overlays, subtitle decoding, filters and picture-in-picture. It also provides probes for performance metrics and system tracing. The app can run locally, or it can be deployed behind Cloudflare Access to control who can use it. Anyone interested can read the original post first to understand the architecture and limitations, then decide whether it fits their needs.

Cloudflare official blog: original Streamline post

FAQ

Is Streamline an official commercial product?

According to Cloudflare, Streamline is a "developer playground" that demonstrates how to build custom video pipelines on its developer platform, and it is released as open source. The original post does not describe it as a standalone paid product.

What video processing can Streamline do?

According to Cloudflare, it currently supports four types of operations: filters, image overlays (including PNG annotations that can be updated while running), burned-in subtitles, and output encoding settings. The engine fixes the order in which they run.

Do ordinary viewers need to do anything?

No. This is a tool for developers, and ordinary viewers need not take any action. Its impact is more likely to appear indirectly in future live streaming or video services, such as live subtitles or dynamic graphics.

What are Streamline's known limitations?

Cloudflare admits the current version processes media on Container CPUs, which becomes a bottleneck at higher resolutions or frame rates. The company also says the owner deployment can run only one session at a time and is not a security model for a public multi-user service.

Where does this information come from?

Everything in this article comes from Cloudflare's official blog post published on October 2, 2026, and reflects the company's own account.

Browse the latest news in this topic

Latest travel guides

Sources

Lifestyle