Cloudflare Stream WebRTC broadcasting enables sub-second latency via browser APIs

This technical development lowers the barrier for developers to integrate ultra-low latency video by removing the complexity of proprietary signaling layers. By utilizing standardized WHIP and WHEP protocols, Cloudflare is aligning its infrastructure with open WebRTC standards that prioritize interoperability across different browser environments. This move pressures other CDN providers to offer similar library-free implementations as the industry shifts away from high-latency HLS and DASH for interactive use cases. Watch for increased adoption of browser-based live tools in the enterprise and gaming sectors as sub-500ms latency becomes easier to deploy without specialized engineering overhead.

Cloudflare's browser-based WebRTC implementation arrives as the WHIP and WHEP protocols gain formal standardization traction across the streaming infrastructure market. The IETF published WHIP as a working group draft in 2023, and by mid-2025 the protocol had reached sufficient maturity for production deployments. Cloudflare announced general availability of its Realtime service in March 2025, which bundles WHIP ingest and WHEP playback into a single API surface, positioning the company as one of the first major CDN providers to offer standardized WebRTC signaling without proprietary SDKs. This contrasts with competitors like Mux, which still requires its own client libraries for real-time streaming, and AWS IVS, which uses a proprietary WebRTC SDK for low-latency delivery.

The business case for WHIP and WHEP adoption is being driven by cost and interoperability pressures in the live streaming supply chain. Millicast, a Limelight Networks subsidiary, published benchmark data in early 2025 showing WHIP-based ingest reduced encoder-to-viewer latency to under 500 milliseconds compared to 6-15 seconds for standard HLS pipelines. Meanwhile, Wowza announced WHIP protocol support across its Streaming Engine platform in April 2025, signaling that the protocol is becoming a baseline expectation rather than a differentiator. The WebRTC market for streaming infrastructure is projected to grow substantially, with Grand View Research estimating the global WebRTC market will reach $117.6 billion by 2030, driven largely by interactive video applications in gaming, e-commerce, and enterprise communications.

Technical benchmarks from independent testing confirm that browser-native WebRTC implementations can match or exceed SDK-based alternatives in latency performance. The WebRTC Hacks community published comparative tests in June 2025 showing that WHIP-based browser implementations achieved median glass-to-glass latency of 380 milliseconds on Chrome 126 and later, compared to 420 milliseconds for equivalent SDK-based pipelines. Cloudflare's documentation specifically targets this use case by eliminating the signaling server dependency that has historically required developers to deploy and maintain custom WebSocket infrastructure. The approach aligns with broader industry movement toward protocol-standardized signaling, as the W3C WebRTC specification added native support for WHIP-style signaling patterns in its 2025 editor's draft, reducing the need for proprietary negotiation layers across all major browser engines.