RTMP

RTMP
Name	Real-Time Messaging Protocol
Abbreviation	RTMP
Developed by	Adobe Systems
Initial release	2002
Status	Legacy / Maintained
License	Proprietary / Open implementations

RTMP RTMP is a proprietary streaming protocol developed for persistent, low-latency delivery of audio, video, and data between Adobe Systems servers and clients such as Adobe Flash Player, VLC media player, and mobile applications. It enabled interactive multimedia experiences alongside platforms and services including YouTube, Twitch (service), Akamai Technologies, and Limelight Networks. RTMP influenced later media transport standards adopted by organizations like Apple Inc., Microsoft, and IETF working groups.

Overview

RTMP provides multiplexed channels for encoded media, metadata, and control messages between endpoints such as Adobe Flash Player, Wowza Media Systems, Nginx (software), Red5 (software), and dedicated streaming appliances from Wowza Media Systems and Adobe Systems. It works with codecs including H.264, AAC (codec), MP3, and container formats used by products from Apple Inc., Microsoft Corporation, and Google LLC. Content delivery networks such as Akamai Technologies and Cloudflare historically supported RTMP ingestion for live streaming fed to CDNs and playback workflows involving players like JW Player and Flowplayer.

History and Development

RTMP originated at Macromedia and was further developed after the company's acquisition by Adobe Systems in 2005; its evolution paralleled the rise of platforms like YouTube and services from Limelight Networks. Key milestones include support for live streaming in server software from Adobe Systems, open-source implementations such as Red5 (software) and nginx-rtmp-module, and wide adoption by broadcasters using encoders from Telestream and Wirecast. Shifts in web standards led companies such as Apple Inc. and Google LLC to promote HTTP-based streaming like HLS and DASH through collaborations with standards bodies like the IETF.

Protocol Architecture and Operation

RTMP uses a persistent TCP connection with a handshake and chunked message framing similar to designs used in server products from Adobe Systems and open-source projects like Red5 (software)]. It defines logical channels for audio, video, and command messages; control flows resemble patterns used in media servers from Wowza Media Systems and encoders from Wirecast and OBS Studio. Session negotiation may involve codec signaling compatible with H.264 profiles defined by ITU-T, audio parameters aligned with standards from MPEG and ISO/IEC, and metadata schemas interoperable with tools from Adobe Systems. Variants include encapsulations over secure transports supported by OpenSSL and commercial stacks used by companies such as Akamai Technologies.

Implementations and Software Support

Server implementations include commercial software from Adobe Systems, Wowza Media Systems, and open-source projects like Red5 (software and the nginx (software) module maintained by community contributors. Client support historically centered on Adobe Flash Player and later moved to native players such as VLC media player and libraries integrated into mobile SDKs from Apple Inc. and Google LLC. Encoder and production tool vendors including Telestream, vMix, Wirecast, and OBS Studio provide RTMP output for ingestion into platforms like YouTube, Twitch (service), Facebook Live, and enterprise streaming services from Microsoft Corporation.

Use Cases and Applications

RTMP has been widely used for live broadcasting workflows for events promoted by organizations like ESPN, BBC, and CNN, educational streaming for institutions such as Coursera and edX, interactive applications by firms like Adobe Systems and Akamai Technologies, and low-latency gaming streams on platforms including Twitch (service)]. It has served as an ingestion protocol for large-scale streaming services run by YouTube, Facebook, and corporate CDNs from Limelight Networks.

Security and Limitations

RTMP’s default TCP-based transport required additional layers such as TLS provided by OpenSSL or proprietary tunneling from vendors like Akamai Technologies to meet security policies enforced by enterprises and platforms such as Microsoft Corporation and Apple Inc.. Its dependence on plugins like Adobe Flash Player and persistent TCP sessions became problematic with browser shifts led by Google LLC and Apple Inc. toward HTML5 standards. Scalability and NAT traversal in large deployments rely on CDNs and relay architectures from providers like Akamai Technologies and Cloudflare.

Future and Successor Technologies

Successors and alternatives include HTTP-based adaptive bitrate protocols such as HLS (promoted by Apple Inc.), DASH (standardized by MPEG and ISO/IEC), and low-latency transports like WebRTC developed by the IETF and W3C communities, with implementations from Google LLC, Mozilla Foundation, and Microsoft Corporation. Commercial media distributors and CDNs including Akamai Technologies and Cloudflare have migrated ingestion and edge delivery toward these standards, while open-source projects like NGINX (software) and FFmpeg continue to offer compatibility layers and converters bridging legacy RTMP workflows to modern stacks.

Category:Streaming protocols