RTMP server explained for 2026: what it is, why RTMP outlived Flash, RTMP vs WebRTC vs SRT, surveillance and broadcast uses, free server options and securing it.
Every few months someone declares RTMP dead. Adobe Flash, which gave RTMP its original purpose, was retired at the end of 2020, and newer formats such as HLS, LL-HLS, WebRTC and SRT have replaced RTMP for watching video. All true. None of it explains why RTMP is still the most common way to send live video into a server in 2026, why Twitch, YouTube Live and Facebook Live still accept it by default, or why security teams still use it to bring cameras and phones into their platforms.
This guide explains what an RTMP server is, why RTMP outlived Flash, how it compares with WebRTC and SRT, where it fits in surveillance, how to set one up with free software, and how to secure it.
RTMP (Real-Time Messaging Protocol) was created by Macromedia, later part of Adobe, in the early 2000s to carry audio, video and data for Flash.
An RTMP server receives RTMP streams from encoders or cameras and sends them onwards: to viewers, to recording, or into other formats such as HLS or DASH for playback. It sits at the entry point of a streaming system, accepting connections, checking credentials, then passing on or repackaging the video.
Its role has changed. In the Flash era, RTMP carried video both in and out. Today it is used almost entirely for sending video in, while viewers watch over HLS, LL-HLS, WebRTC or DASH.
That split is why RTMP survived. Encoders, phone apps, cameras and broadcast equipment standardised on RTMP for sending, and changing thousands of products at once is hard. Viewing changed quickly when Flash disappeared, because browsers and apps moved on. The result is a streaming world that uses RTMP at the entry point and modern formats everywhere after it.
Encoders. OBS, the leading free broadcasting software, sends RTMP as standard. So does every major hardware encoder, including Teradek, Matrox, AJA, Elgato and Blackmagic, plus most phone streaming apps and many cameras.
Destinations. Twitch, YouTube Live, Facebook Live, X Live, LinkedIn Live, TikTok Live and nearly every other live platform accept RTMP by default. Some also accept newer options such as SRT, but RTMP is the universal default.
Firewalls. RTMP normally uses port 1935 and can fall back to web ports when that is blocked, which makes it one of the most reliably deliverable protocols on restrictive corporate and mobile networks.
Delay. A few seconds is fine for most broadcasting and for recording surveillance video, where nobody needs sub second control.
Together, these make RTMP a living, well supported part of modern streaming, especially for getting video in.
The question is not which protocol is newest, but which fits the job.
RTMP. A few seconds of delay. Works with almost every encoder and destination, and gets through firewalls well. Runs over TCP, so it can stall on unreliable networks. Not encrypted unless you use RTMPS. Best when compatibility matters most and a few seconds of delay is fine.
WebRTC. Under a second of delay. Modern transport with built in loss recovery, and always encrypted. For sending video in, it uses WHIP (WebRTC HTTP Ingestion Protocol), now widely supported. Best for live response: control rooms, interactive use and reacting to AI alerts.
SRT (Secure Reliable Transport). Low delay and strong recovery from lost packets, designed for poor networks, with encryption built in. Widely supported by professional broadcast equipment. Best over unreliable links such as field operations, long distance broadcasts and links between remote sites.
For most broadcasting, RTMP remains the sensible default. For live response or poor networks, WebRTC and SRT are better. The approach that works best is a server that accepts all three and lets each source use what suits it.
Live broadcasting. OBS and hardware encoders push to an RTMP server, which handles sign in, recording, conversion to viewing formats and distribution. This is how Twitch, YouTube Live and every multi platform setup work.
Cameras. Many IP cameras can push RTMP as an alternative to RTSP, useful when they must cross restrictive networks.
Field teams. Security staff, police, journalists and inspectors stream live from phones to a central server over ordinary mobile networks, usually over RTMP.
Simulcasting. Broadcasters send one stream to an RTMP server, which forwards it to several platforms at once, saving upload bandwidth and centralising control.
Self hosted streaming. Small broadcasters, creators and company video teams run free RTMP servers to keep streaming under their own control.
The three most common free options are Nginx with the nginx-rtmp-module, MediaMTX and Red5 Open Source.
Nginx with nginx-rtmp-module is the most widely deployed. Install Nginx with the RTMP module (many Linux distributions include it), add an RTMP application block to nginx.conf, optionally turn on HLS or DASH output, and add authentication using on_publish webhooks. It is stable and well documented. The catch: the module is no longer actively maintained, though community forks continue.
MediaMTX is the modern alternative, handling RTMP, RTSP, SRT, WebRTC and HLS in one server with a simple configuration file. It is what many engineers choose for new self hosted projects.
Red5 Open Source is a long established server with a paid Red5 Pro edition that adds WebRTC, SRT, low latency streaming and clustering.
A typical Nginx setup: install Nginx with RTMP support; set up the application block and the stream key authentication you need; turn on HLS for browser viewing if required; add encryption for any stream crossing an untrusted network; open the firewall ports; test from OBS with a stream URL such as rtmp://server-address:1935/live and your stream key; then check playback. A basic setup takes hours. Production hardening, with authentication, monitoring, redundancy and scaling, takes days.
Plain RTMP is not encrypted. The video and the stream key travel in the clear, so anyone who can see the network traffic can capture both.
Encrypt anything that crosses an untrusted network. RTMPS wraps RTMP in TLS, like HTTPS. SRT and WebRTC encrypt by design and handle poor networks better too. Keep plain RTMP for trusted internal networks.
Protect stream keys. The stream key is usually the only credential, and leaked keys are one of the most common live streaming incidents. Use separate keys per event or broadcaster, rotate any that may be exposed, and check every connection against a central identity service rather than relying on a fixed key.
Segment the network. Expose only the streaming ports, lock management screens to administrators, and never put an admin interface or playback endpoint directly on the public internet.
For surveillance, treat the RTMP server as part of your security boundary: subject to the same access controls, audit and data protection expectations, such as India's DPDP Act or GDPR, as the rest of your video estate.
Camera to platform. Some IP cameras, especially older models, can push RTMP. That helps when the platform cannot reach a camera over RTSP, when the camera is remote with patchy connectivity, or when its RTSP is unreliable.
Field teams. Guards, patrols, police and incident responders stream live from phones into the video platform during incidents, getting eyes from the field into the control room in real time.
Public displays. Smart cities, transit operators and public safety agencies often use RTMP to feed public dashboards, citizen apps and station screens.
Broadcast sharing. Security operations occasionally send live footage to broadcasters, during emergencies for example, using RTMP because that is what broadcasters accept.
Each of these needs a surveillance platform that treats RTMP as a first class protocol alongside RTSP, WebRTC, HLS, SRT and ONVIF. Platforms that support only some protocols force you to bolt on extra infrastructure.
Visylix is an automated AI video surveillance platform built in India. Its native streaming engine supports 13+ protocols, including RTMP, RTSP, HLS, LL-HLS, WebRTC (WHEP and WHIP), SRT and HTTP-FLV, plus GB28181, NDI and RIST ingest and ONVIF camera control. Video arriving over any of them is repackaged for the others, and recorded exactly as it arrived.
One entry point, every destination. Visylix accepts RTMP from OBS, hardware encoders, phone streaming apps and RTMP capable cameras, checking publish authentication on every connection. The same stream can be recorded, watched live over WebRTC in under a second or over HLS, pulled by a remote site over SRT, and pushed to a broadcast destination over RTMP. For streams crossing the public internet, Visylix also accepts SRT and WebRTC (WHIP), both encrypted by design.
The same AI on every stream. A stream arriving over RTMP gets the same 22 AI analytics, built in house, as one arriving over RTSP or WebRTC: face recognition, number plate recognition, object detection, person tracking, crowd detection, PPE detection, pose estimation, heat maps, motion detection, unique person counting, intrusion detection and line crossing. A live stream from a guard's phone can trigger the same Sudarshan rules as a fixed camera.
Built for India and the world. An interface in 55 languages including 13 Indian languages, rupee pricing through Razorpay, and deployment on your own infrastructure rather than a foreign cloud. Starter and Pro include unlimited cameras on the VMS licence, from ₹4,999 or $49 per month.
Designing a deployment that needs RTMP alongside the full protocol mix real surveillance and broadcast work demands? Talk to the Visylix team: https://visylix.com/contact.
RTMP is not a legacy protocol. Flash ended it as a viewing format, but it remains the most widely used way to send live video in, with universal encoder support and a delay of a few seconds that suits most broadcasting.
WebRTC is better for live response and SRT for unreliable networks. A good server accepts all three.
Free RTMP servers, including Nginx with nginx-rtmp-module, MediaMTX and Red5, are widely used and well supported.
Plain RTMP is unencrypted. Encrypt anything crossing an untrusted network, rotate stream keys and authenticate every connection.
In surveillance, RTMP brings in cameras and field teams and feeds public displays and broadcasters. Choose a platform that handles it alongside every other protocol.
An RTMP server is software that receives live video sent over RTMP (Real-Time Messaging Protocol) from encoders, cameras or phone apps, checks the sender is allowed, and then records the video, passes it on, or repackages it into formats such as HLS or WebRTC for viewers. Today RTMP is used mainly for sending video in; viewers usually watch over HLS, LL-HLS, WebRTC or DASH.
Sending live video into a server: from broadcasting software such as OBS to Twitch or YouTube Live, from cameras to a video platform, from phones in the field to a control room, from one stream out to many destinations at once, and in self hosted streaming setups built on free software such as Nginx with its RTMP module, MediaMTX or Red5.
No. The end of Flash in 2020 ended RTMP as a way to watch video, but RTMP remains the most widely used way to send live video in. Every major live platform, including Twitch, YouTube Live, Facebook Live, TikTok Live and LinkedIn Live, accepts it, and OBS, hardware encoders, phone apps and many cameras send it by default.
The most common free options are Nginx with the nginx-rtmp-module, MediaMTX and Red5 Open Source. For Nginx: install it with RTMP support, add an RTMP application block to the configuration, optionally turn on HLS output for browser viewing, add authentication, open the right firewall ports, and test with OBS. A basic setup takes hours; production hardening with authentication, monitoring and redundancy takes days.
Yes, several. Nginx with nginx-rtmp-module is free and open source. MediaMTX is free and handles RTMP alongside RTSP, SRT, WebRTC and HLS in one server. Red5 Open Source is free, with a paid Red5 Pro edition. MonaServer is another free option. Commercial products such as Wowza, Castr and Nimble Streamer add enterprise features on top.
Plain RTMP is not encrypted, so video and stream keys travel in the clear. It runs over TCP, which can stall and buffer on unreliable networks where SRT or WebRTC cope better. Its delay of a few seconds is too long for live response. And the popular nginx-rtmp-module is no longer actively maintained, though community forks continue. Each issue can be managed if you plan for it.
It depends on the job. RTMP offers the widest compatibility with a delay of a few seconds, and suits most live broadcasting. WebRTC delivers video in under a second, with built in encryption and loss recovery, and suits live response. SRT is built for unreliable networks, with strong loss recovery and encryption, and suits field and long distance links. A good streaming server accepts all three.
Yes. Many IP cameras can push RTMP as an alternative to their usual RTSP or ONVIF connection. That helps when the platform cannot reach the camera directly because of network restrictions, when the camera is remote with patchy connectivity, or when the camera's RTSP is unreliable. Security teams also use RTMP to stream from phones in the field, to share video with public displays and to send footage to broadcasters.
RTMP is the plain protocol, with video and stream keys unencrypted. RTMPS is RTMP wrapped in TLS, the same encryption that turns HTTP into HTTPS. Behaviour is identical; security is very different. For any stream crossing an untrusted network, use an encrypted option: RTMPS where your destination expects it, or SRT and WebRTC, which encrypt by design.
Open source RTMP servers are free to use; the real costs are hosting, bandwidth, storage and engineering time. Commercial streaming servers charge by scale and features. Complete video surveillance platforms such as Visylix include RTMP as one of many protocols in the platform licence rather than as a separate product.