RTMP and MMS in 2026: what they are and whether they're still used
RTMP (Real-Time Messaging Protocol) is an Adobe, Flash-era protocol for streaming audio, video and data over a persistent TCP connection. MMS (Microsoft Media Server protocol) is a much older Microsoft protocol that pushed media from Windows Media Services to Windows Media Player. Neither is used for modern in-browser playback: Adobe Flash Player reached end-of-life on 31 December 2020, and MMS was deprecated by Microsoft long before that in favour of HTTP-based streaming. RTMP is the survivor, but only in one role - as an ingest protocol. Live platforms such as YouTube Live, Twitch and Facebook Live still accept RTMP streams from encoders like OBS and ffmpeg, then re-package them into HLS or MPEG-DASH for delivery. MMS is best treated as history.
A quick map of streaming protocols
A streaming protocol governs how media data is moved between a server and a client in real time, instead of forcing a full download first. Over the years the field has included HTTP progressive download, RTSP, MMS, RTMP, RTP/RTCP, and today's adaptive HTTP protocols. The important shift to understand is the move away from custom, stateful, plugin-bound protocols (RTMP, MMS) toward adaptive streaming over plain HTTP (HLS and MPEG-DASH) and, for truly real-time use cases, WebRTC.
This post covers the two legacy protocols. For the audio container and codec side of the story - Ogg, MP3 and AAC - see the companion post on streaming protocols: Ogg, MP3 and AAC.
RTMP (Real-Time Messaging Protocol)
RTMP is a proprietary protocol Adobe developed to stream audio, video and data between a Flash player and a Flash Media Server. It is a stateful, TCP-based protocol designed for low-latency, persistent connections, and it traditionally carried H.264 video with AAC or MP3 audio.
Key characteristics:
- Default port: 1935 (TCP). Variants include RTMPS (over TLS), RTMPT (tunnelled over HTTP) and RTMPE (legacy encryption).
- Persistent connection: the client and server keep a long-lived TCP session, which historically gave RTMP an edge in latency and interactivity.
- Server software: historically delivered by Adobe Flash Media Server, Wowza, Red5, nginx-rtmp and crtmpserver.
- Codecs: classic RTMP supported H.264/AAC/MP3; the format itself has not evolved to carry modern codecs like AV1 well.
Why RTMP is no longer used for playback
RTMP playback required the Flash plugin (or a Flash replacement such as the now-unmaintained Gnash on Linux). With Flash Player officially dead since 31 December 2020 and removed from every major browser, you cannot play RTMP in a browser anymore. Any site still claiming "RTMP playback" is describing a dead path.
Why RTMP still survives - as an ingest protocol
The one place RTMP remains genuinely common is the first hop of a live broadcast: an encoder sends a single RTMP stream up to a media platform. OBS Studio, ffmpeg, hardware encoders and most "go live" tooling speak RTMP, and YouTube Live, Twitch and Facebook Live all accept it. The platform then transcodes and repackages that stream into adaptive HTTP formats (HLS / DASH) for the audience. So in 2026 RTMP is contribution/ingest plumbing, not a delivery protocol - and newer ingest options like SRT and WebRTC-based WHIP are steadily taking its place.
# Push a local video file to a live platform's RTMP ingest endpoint with ffmpeg.
# This is the role RTMP still plays in 2026: encoder -> platform ingest.
# Replace STREAM_KEY with the key your platform (YouTube/Twitch/etc.) gives you.
ffmpeg -re -i input.mp4 \
-c:v libx264 -preset veryfast -b:v 4500k -maxrate 4500k -bufsize 9000k \
-g 60 -pix_fmt yuv420p \
-c:a aac -b:a 160k -ar 44100 \
-f flv rtmp://a.rtmp.youtube.com/live2/STREAM_KEYMMS (Microsoft Media Server protocol)
MMS was Microsoft's proprietary protocol for delivering real-time multimedia from Windows Media Services to Windows Media Player. It could run over TCP or UDP (default port 1755) and let the client send control messages - start, stop, seek - while the server streamed audio and video back, either on the same TCP connection or as a flow of UDP packets.
MMS is obsolete. Microsoft deprecated it years ago and moved Windows Media delivery to RTSP and then to HTTP-based streaming (and ultimately to Smooth Streaming, an early adaptive HTTP format). Modern Windows Media stacks and the wider ecosystem no longer rely on mms:// URLs, and most current players will not handle them. Treat MMS purely as historical context: if you encounter it in old documentation or legacy systems, the migration target today is HLS or MPEG-DASH.
What replaced RTMP and MMS for delivery
Modern streaming delivery is built on adaptive bitrate streaming over ordinary HTTP, which works through firewalls and CDNs without plugins:
- HLS (HTTP Live Streaming): the most widely supported delivery format, plays natively on Apple devices and via JavaScript players (hls.js) everywhere else. LL-HLS (Low-Latency HLS) reduces glass-to-glass latency.
- MPEG-DASH: the open, codec-agnostic standard for adaptive streaming, common in DRM-protected and non-Apple workflows.
- WebRTC: the choice for genuinely real-time, sub-second use cases - video calls, interactive auctions, live betting, two-way audio.
A typical 2026 live pipeline is: encoder sends RTMP/SRT ingest -> media server or cloud service transcodes -> audience receives HLS/DASH (or WebRTC for ultra-low latency).
Building streaming into your product
At MicroPyramid we have spent 12+ years and delivered 50+ projects building web and cloud applications for startups and enterprises, including audio and video streaming features. If you are modernising a legacy Flash/RTMP or Windows Media stack, or adding live and on-demand streaming to a new product, the right architecture today is HTTP-based adaptive delivery (HLS/DASH) with RTMP or SRT used only for ingest, fronted by a CDN. Learn more about our web development services to see how we can help you design and ship a modern streaming pipeline.
Frequently asked questions
Is RTMP still used in 2026?
Yes, but only as an ingest protocol. You can no longer play RTMP in a browser because Adobe Flash Player has been end-of-life since 31 December 2020. RTMP survives as the format encoders like OBS and ffmpeg use to push a live stream up to platforms such as YouTube Live, Twitch and Facebook Live, which then repackage it into HLS or MPEG-DASH for viewers.
Is MMS streaming still supported?
No. MMS (Microsoft Media Server protocol) is obsolete. Microsoft deprecated it long ago and moved to RTSP and then HTTP-based streaming. Modern players generally do not handle mms:// URLs, so MMS should be treated as historical and migrated to HLS or MPEG-DASH.
What is the difference between RTMP and HLS?
RTMP is a stateful, persistent TCP protocol that once delivered Flash playback and now mostly handles live ingest. HLS delivers media as small files over plain HTTP, adapts the bitrate to the viewer's bandwidth, plays without any plugin, and works smoothly with CDNs. For audience delivery in 2026, HLS (or MPEG-DASH) is the standard; RTMP is the first hop, not the last.
What should I use instead of RTMP and MMS today?
For delivery to viewers, use HLS or MPEG-DASH for adaptive streaming, with LL-HLS where lower latency matters and WebRTC for real-time, sub-second interaction. For the ingest hop into a media server or cloud platform, RTMP still works, though SRT and WebRTC-based WHIP are increasingly preferred.
Can I still build an internet radio or audio streaming service?
Yes. The modern approach uses HTTP-based streaming (HLS for adaptive audio, or Icecast/HTTP for simple internet radio) rather than RTMP or MMS. For codec and container choices on the audio side, see our companion post on Ogg, MP3 and AAC.