RTMP's Long Goodbye: SRT, WebRTC, and the New Ingest Stack Every Live Producer Should Know
The 25-year-old protocol still carrying most of live video is being retired. What SRT, WebRTC ingest, and RIST actually change about latency, reliability, and cost.
For a quarter-century, RTMP has been the front door of live video. Nearly every encoder, every switcher, every OBS install in the world still speaks it by default. And nearly every engineering team running a serious live platform is actively working to replace it.
RTMP didn’t fail — it aged. Its TCP-based transport treats packet loss as a retry problem, which translates directly to latency spikes. On a congested network or a long-haul path, RTMP’s reliability mechanism becomes its latency liability.
The Successor Stack, Ranked by Job
| Protocol | Latency | Best For | Catch |
|---|---|---|---|
| RTMP | 3–10s | Legacy compatibility | TCP retries, no native encryption story |
| SRT | <1s | Contribution/ingest over public internet | Still transport, not playback |
| WebRTC | <500ms | Interactive broadcast, real-time audience | Complexity, scaling cost |
| RIST | <2s | Broadcast contribution, reliability | Niche tooling, encoder support |
What the Shift Actually Means for a Producer
The distinction that matters isn’t “new vs old” — it’s which layer the protocol serves:
- Ingest/contribution (camera → cloud): SRT has become the de-facto replacement. ARQ recovery without TCP head-of-line blocking, native AES, and it tolerates lossy paths that would have choked RTMP.
- Distribution/playback (cloud → audience): WebRTC for sub-second interactivity; LL-HLS/LL-DASH for scale. RTMP never really lived here anyway.
- The hybrid reality: Most professional stacks now run SRT ingest → transcode → HLS/DASH or WebRTC distribution. RTMP lingers at the encoder edge because the installed base of hardware doesn’t retire on spec schedules.
“RTMP isn’t dead — it’s becoming the printer port of streaming. Still everywhere, increasingly vestigial.”
Encoder profiles and ingest configurations in the YEDKK — Live Production Notebook.
The front door is moving. Know which protocol is carrying your signal.