Video Streaming Protocols Compared: HLS, WebRTC, SRT, RTMP & More

Most live streams use two protocols: 1) get video from the broadcaster to your servers, and 2) get it to viewers. Here is how the main options compare.
Video Streaming Protocols Compared cover with tiles for HLS, WebRTC, DASH, RTMP, SRT, and WHIP around a blue live video icon

TL;DR

  • Most live streams use two protocols: one for ingest (getting video from the broadcaster to your servers) and one for delivery (getting it to viewers).
  • For ingest, RTMP is still the most widely accepted, SRT is built for unreliable networks, and WHIP brings WebRTC to broadcast tools like OBS.
  • For delivery, HLS and MPEG-DASH reach the most viewers but add seconds of delay, while WebRTC delivers video in under half a second for interactive streams. Stream Video accepts RTMP, WHIP, and SRT and delivers over WebRTC or HLS.

Picking a streaming protocol used to mean picking one. Today, almost every live stream combines several. An encoder pushes video in with one protocol, a server repackages it, and viewers pull it out with another. The right combination oscillates based on things like how many people are watching, how much delay they'll tolerate, and whether they need to talk back.

This guide covers the nine protocols you're most likely to choose between, compares them side by side, and answers the head-to-head questions developers search for most.

What Is a Video Streaming Protocol?

A video streaming protocol is a set of rules for moving video over a network. It covers how it's split into pieces, how those pieces are requested or pushed, and how lost data is handled.

It helps to separate three things that often get mixed up:

  • The protocol decides how video travels, like HLS, WebRTC, or SRT.
  • The codec decides how video is compressed, like H.264, HEVC, or AV1. Most protocols work with several codecs.
  • The container decides how compressed audio, video, and metadata are packaged into files or segments, like MP4 or MPEG-TS. CMAF, an ISO standard for fragmented MP4 segments, lets HLS and MPEG-DASH share the same media files.

How a Live Stream Moves From Camera to Viewer

Most live video goes through three stages:

  1. Ingest: The broadcaster's encoder, like OBS or a hardware encoder, sends one high-quality stream to a media server using an ingest protocol such as RTMP, SRT, or WHIP.
  2. Processing: The server transcodes the stream into several quality levels for adaptive bitrate streaming and packages it for delivery.
  3. Delivery: Viewers' players fetch the stream with a delivery protocol such as HLS, MPEG-DASH, or WebRTC, usually through a CDN or a network of media servers.

Twitch is a good example. Its transcoder takes an incoming RTMP stream from the creator and turns it into an HLS stream for viewers.

Video Streaming Protocols Compared

Protocol Main role Transport Typical latency Plays in browsers
HLS Delivery HTTP over TCP 15 to 30 seconds Safari natively, others with a JavaScript player
Low-Latency HLS Delivery HTTP over TCP About 2 to 3 seconds Same as HLS
MPEG-DASH Delivery HTTP over TCP Similar to HLS With a JavaScript player
WebRTC Real-time delivery and calls UDP, with TCP fallback Under 500 ms Yes, in all major browsers
WHIP and WHEP WebRTC ingest and playback HTTP signaling, WebRTC media Same as WebRTC Through WebRTC
SRT Ingest and contribution UDP Sub-second No
RTMP Ingest TCP 2 to 5 seconds No
RTSP IP cameras RTP over UDP or TCP Varies by setup No
Media over QUIC Ingest and delivery (emerging) QUIC Sub-second (target) Through WebTransport

Note: Latency figures come from Cloudflare's engineering blog and Apple's Low-Latency HLS documentation. Real-world latency depends on your segment sizes, player buffers, and network.

9 Video Streaming Protocols to Know

1. HTTP Live Streaming (HLS)

HLS is Apple's HTTP-based streaming protocol and the most widely supported way to deliver video to viewers. The server splits video into short segments listed in a playlist, and the player downloads them over regular HTTP, so HLS works with any CDN. It's documented in RFC 8216.

  • Best for: Delivering live and on-demand video to large audiences on any device.
  • Strengths: Plays natively in Safari and on Apple devices, and everywhere else through players like hls.js. It supports adaptive bitrate streaming, so viewers get the best quality their connection can handle.
  • Watch out for: Latency. Apple recommends 6-second segments, and players buffer several of them, which adds up to 15 to 30 seconds behind real time.

2. Low-Latency HLS (LL-HLS)

Apple introduced Low-Latency HLS in 2019. It splits segments into smaller "parts" and lets players request them before they're finished, which Apple says makes latencies under two seconds achievable at scale. In practice, Cloudflare puts it around three seconds.

  • Best for: Live sports, events, and auctions where viewers need to stay close to real time, but you still want HLS's reach and CDN support.
  • Watch out for: Your packager, CDN, and player all need to support it.

3. MPEG-DASH

MPEG-DASH is an international standard (ISO/IEC 23009-1) that works like HLS: segments described by a manifest, delivered over HTTP. Unlike HLS, it isn't controlled by one company and doesn't require specific codecs.

  • Best for: Large on-demand and live platforms, especially ones that use codecs like VP9 or AV1.
  • Strengths: It's codec-agnostic, widely used by large video platforms, and YouTube Live even accepts DASH for ingest.
  • Watch out for: No browser plays DASH natively, so you need a player like dash.js or Shaka Player. iPhones support it through Safari's ManagedMediaSource API since iOS 17.1, which dash.js added support for in late 2023. Many teams still serve HLS to Apple devices.

4. WebRTC

WebRTC is the real-time protocol built into every major browser. It became a W3C Recommendation in 2021 and grew out of technology Google acquired and open-sourced. It sends media over UDP, so it doesn't wait for lost packets to be resent, and video arrives in under half a second.

  • Best for: Video calls, live shopping, auctions, watch parties, and any stream where viewers interact with the host.
  • Strengths: The lowest latency of any widely supported protocol, and it works in the browser without plugins.
  • Watch out for: WebRTC was designed for peer-to-peer connections, which don't scale to large groups on their own. Apps with many participants route media through a selective forwarding unit (SFU), and running that infrastructure yourself is a big job.

5. WHIP and WHEP

WHIP (WebRTC-HTTP Ingestion Protocol) gives WebRTC a simple, standard way to receive a stream from an encoder. It became an IETF standard, RFC 9725, in March 2025, and OBS Studio added WHIP output in version 30. Its playback counterpart, WHEP, is still an IETF draft.

  • Best for: Sending a broadcast from OBS or a hardware encoder into a WebRTC stream, keeping latency low from end to end.
  • Watch out for: Support is still growing. Not every platform accepts WHIP yet.

6. Secure Reliable Transport (SRT)

The SRT protocol was created by Haivision and open-sourced in 2017. It sends video over UDP and recovers lost packets by asking the sender to resend them within a fixed latency window, which keeps streams stable over unreliable networks. It also supports AES encryption with 128-, 192-, or 256-bit keys.

  • Best for: Sending high-quality video from the field, a studio, or a remote producer over the public internet.
  • Strengths: Sub-second latency, built-in encryption, and it works with any codec.
  • Watch out for: Browsers can't play SRT, so it's used for ingest and contribution, not for viewers.

7. Real-Time Messaging Protocol (RTMP)

RTMP was built by Adobe for Flash Player. Flash reached end of life in December 2020, so no browser plays RTMP anymore, but it's still the most widely accepted ingest protocol. YouTube Live and Twitch both accept it, and most encoders support it.

  • Best for: Sending a stream from OBS or another encoder to a streaming platform.
  • Strengths: Universal support and latency of around 2 to 5 seconds. Enhanced RTMP, introduced in 2023 by a group including Adobe and YouTube, adds modern codecs like HEVC and AV1.
  • Watch out for: It runs over TCP, so on a poor connection, lost packets cause stalls instead of brief glitches.

8. Real-Time Streaming Protocol (RTSP)

RTSP controls media sessions, like play and pause, while the video itself travels over RTP. It dates back to 1998, with RTSP 2.0 published as RFC 7826 in 2016. Today, it's the standard way IP security cameras stream video, and the ONVIF Profile S camera standard requires it.

  • Best for: Security cameras, CCTV, and other devices on private networks.
  • Watch out for: Browsers can't play RTSP. To show a camera feed in a web app, you need a gateway that converts it to WebRTC or HLS.
Building your own app? Get access to our Livestream or Video Calling API and launch in days!

9. Media over QUIC (MoQ)

Media over QUIC is a new protocol being developed at the IETF. It's still a draft as of November 2026. It aims to combine WebRTC's low latency with the scale of HLS and DASH by sending media over QUIC, the transport behind HTTP/3. Cloudflare launched a MoQ relay network in August 2025.

  • Best for: Experimenting with the next generation of live streaming.
  • Watch out for: The spec is still changing, and player and encoder support is limited.

The Protocols Underneath

Streaming protocols run on top of lower-level network protocols. You don't usually choose these directly, but they explain a lot about how each streaming protocol behaves:

  • TCP guarantees every packet arrives in order by resending lost ones. That makes it reliable but slower when a connection is poor. HLS, MPEG-DASH, and RTMP run over TCP.
  • UDP sends packets without waiting for confirmation, so a lost packet causes a brief glitch instead of a stall. WebRTC media and SRT run over UDP, and add their own recovery on top. Learn more in our guide to communication protocols.
  • QUIC, standardized in 2021 as RFC 9000, runs over UDP but adds reliability and encryption. It powers HTTP/3 and Media over QUIC.
  • SIP isn't a streaming protocol. It sets up and ends calls, mostly for VoIP phone systems, while the media itself travels over RTP.

Head-to-Head: Common Protocol Comparisons

RTMP vs RTSP

Both are older protocols, but they're used for different jobs. RTMP sends a stream from an encoder to a streaming platform, and is accepted by YouTube, Twitch, and most media servers. RTSP pulls video from IP cameras on private networks. Neither plays in a browser, so both are usually converted to HLS or WebRTC for viewers.

RTSP vs WebRTC

RTSP is how most IP cameras output video, and WebRTC is how browsers play real-time video. They often work together. A gateway pulls the camera's RTSP stream and converts it to WebRTC, so people can watch the camera live in a web app with minimal delay.

HLS vs WebRTC

HLS is built for scale. It works with standard CDNs and plays on almost any device, but viewers are 15 to 30 seconds behind, or a few seconds with LL-HLS. WebRTC is built for interaction, with under half a second of delay, but it needs media servers instead of a CDN. Many apps use both: WebRTC for hosts and active participants, and HLS for large audiences who are only watching.

SRT vs RTMP

Both are ingest protocols. RTMP has the widest support and is the default in most encoders and platforms. SRT runs over UDP with its own packet recovery and encryption, so it holds up better on unreliable networks and is common in professional broadcasting. Choose RTMP for compatibility and SRT for quality and security over the public internet.

SRT vs RTSP

SRT sends video reliably across the public internet, while RTSP is designed for cameras on local networks. If you need to send camera footage from one site to another, SRT is usually the better choice for that leg.

HLS vs MPEG-DASH

They work almost the same way, and with CMAF they can even share the same media segments. HLS has native support on Apple devices, and MPEG-DASH is an open international standard with more codec flexibility. Large platforms often support both.

How to Choose the Right Protocol

Start with what your viewers do as opposed to the protocol itself:

  • Broadcasting to a large audience, like a sports stream or a product launch: ingest with RTMP or SRT, and deliver with HLS or MPEG-DASH through a CDN. Use LL-HLS if viewers need to stay close to real time.
  • Interactive streams, like live shopping, auctions, or Q&A sessions: deliver with WebRTC so viewers and hosts are in sync, and use WHIP if hosts broadcast from OBS. Read more about low-latency video streaming.
  • Video calls and meetings: use WebRTC.
  • Professional contribution, like a remote studio or a field camera: send with SRT.
  • Security cameras: keep RTSP on the camera side, and convert to WebRTC or HLS for viewing in apps.

Protocol choices also shape your costs, since CDN delivery and media servers are priced differently. Our breakdown of live streaming infrastructure costs covers what to expect.

Live Streaming With Stream

If you'd rather not run ingest servers, transcoders, and media servers yourself, Stream Video handles each stage of the pipeline:

  • Ingest: Hosts can go live from the browser or mobile SDKs, or send a stream from OBS or an encoder with RTMP, WHIP, or SRT.
  • Delivery: Viewers watch over WebRTC for real-time interaction, or over HLS for large audiences.
  • Restreaming: You can also broadcast over RTMP to other platforms like YouTube.

See how Popup launched creator livestreams in days and how Lokal scaled video and audio calling to millions of users with Stream.

Frequently Asked Questions

What is the most common video streaming protocol?

For delivery, HLS is the most widely supported, since it plays on nearly every device and works with standard CDNs. For ingest, RTMP is still the most widely accepted by streaming platforms and encoders.

What protocol does Twitch use?

Twitch receives streams over RTMP and delivers them to viewers over HLS. In 2024, it began testing Enhanced Broadcasting, which uses Enhanced RTMP to send several quality levels from the streamer's computer.

What protocols does YouTube Live accept?

According to YouTube's documentation, YouTube Live accepts RTMP and RTMPS, HLS, and MPEG-DASH for ingest.

Which protocol is used for video conferencing?

Most video conferencing apps use WebRTC, which sends media over UDP for low latency. If a firewall blocks UDP, WebRTC falls back to TCP through a relay server.

Is TCP or UDP better for streaming video?

It depends on latency. TCP, used by HLS, DASH, and RTMP, guarantees every packet arrives, which suits streams that can buffer for a few seconds. UDP, used by WebRTC and SRT, keeps video moving when packets are lost, which suits real-time streams.

Is RTMP still used?

Yes. Browsers no longer play RTMP, but it's still the most common way to send a stream from an encoder to a platform. Enhanced RTMP, introduced in 2023, added support for newer codecs like HEVC and AV1.

Which streaming protocol has the lowest latency?

WebRTC, at under half a second, is the lowest-latency protocol that plays in browsers. SRT also reaches sub-second latency, but only for ingest and contribution.