Key takeaways
- RTMP is an ingest protocol, not a delivery protocol for end users.
- Modern browsers dropped RTMP support, so you cannot play RTMP streams directly on the web.
- RTMP is simple to set up but lacks the error recovery of newer protocols like SRT.
- Use RTMP for stable, high-bandwidth connections where packet loss is low.
How RTMP works
RTMP operates over TCP port 1935. It breaks video and audio into small chunks, typically 1024 bytes, and sends them sequentially. The protocol includes a handshake phase where the client and server exchange version numbers and timestamps to synchronize the stream. Once connected, data flows in one direction from the encoder to the server.
Because RTMP runs over TCP, it relies on the network to handle retransmissions. If a packet is lost, TCP requests a resend, which can introduce jitter or delay. This makes RTMP sensitive to network instability. It works best on wired connections or strong Wi-Fi with consistent bandwidth. For mobile or cellular ingest, RTMP may struggle with high packet loss.
The protocol supports multiple streams over a single connection and allows for data messages, which can carry metadata or control signals. However, it does not include built-in encryption. Operators often wrap RTMP in SSL (RTMPS) to secure the connection, though this adds overhead and complexity.
Why RTMP matters for a streaming business
RTMP remains a standard for ingesting live content because it is widely supported by hardware encoders, software encoders, and streaming platforms. If you run a live event, a church service, or a sports league, your camera or encoder likely outputs RTMP by default. Understanding RTMP helps you troubleshoot ingest issues, such as dropped frames or connection timeouts.
For operators, the key decision is whether to stick with RTMP or move to a more resilient protocol. RTMP is sufficient for controlled environments, like a studio with a fiber connection. But if you are broadcasting from a remote location with unstable internet, RTMP may not cut it. You need to know the limits of your ingest protocol to avoid blackouts during critical moments.
Also, RTMP is not for delivery. You cannot send an RTMP stream to a viewer's browser. You must transcode the RTMP ingest into HLS or DASH for playback. This distinction is critical for planning your infrastructure. If you try to use RTMP for end-user playback, it will fail in modern browsers.
RTMP vs SRT
RTMP and SRT serve the same purpose: ingesting live video into a server. But they handle network instability very differently. RTMP uses TCP, which can stall if packets are lost. SRT uses UDP with its own error correction and retransmission logic, making it more resilient to jitter and packet loss.
| Feature | RTMP | SRT |
|---|---|---|
| Transport Protocol | TCP | UDP |
| Latency | Low (1-3 seconds) | Low (1-3 seconds) |
| Packet Loss Handling | Relies on TCP retransmission | Built-in FEC and ARQ |
| Encryption | Optional (RTMPS) | Native (AES-128) |
| Browser Support | None (ingest only) | None (ingest only) |
| Best Use Case | Stable, high-bandwidth connections | Unstable or cellular connections |
Choose RTMP for simplicity and compatibility. Choose SRT for reliability in challenging network conditions. Many platforms support both, so you can test which works best for your specific broadcast setup.
Common mistakes with RTMP
- Using RTMP for playback: Browsers no longer support RTMP. You must transcode to HLS or DASH for web delivery.
- Ignoring bandwidth limits: RTMP requires a stable upload speed. If your encoder bitrate exceeds your available bandwidth, the stream will drop.
- Skipping encryption: Unencrypted RTMP streams can be intercepted. Use RTMPS or SRT for sensitive content.
- Assuming low latency means no delay: RTMP still has inherent buffering. Do not expect sub-second latency without additional tuning.
How Flicknexs handles RTMP
Flicknexs accepts RTMP ingest for your live streams. You generate a unique stream key in your dashboard and enter it into your encoder. Once the stream connects, Flicknexs transcodes it into adaptive bitrate HLS for delivery across web, iOS, Android, and smart TV apps. You can record live streams to VOD automatically. The platform supports concurrent device limits and geo-restriction to control access. For secure ingest, you can use RTMPS if your encoder supports it. Check the Broadcast streaming software page for details on setting up your first live event.
Done reading about RTMP?
Flicknexs ships it as part of a white-label streaming platform: web, mobile and TV apps, billing, ads, DRM and playout, on your own domain.