RTMP/RTMPS with OBS, vMix and encoders
Set up OpenRTMP ingest, enter server and key in OBS, use RTMPS, and understand legacy vs. Enhanced RTMP.
RTMPS does not replace the RTMP protocol and does not automatically improve picture quality or bitrate. It wraps the connection in TLS. For OBS and other encoders, the server URL, stream key and basic publish workflow remain very similar.
| Property | RTMP | RTMPS |
|---|---|---|
| Transport encryption | No | Yes, TLS |
| Stream key protected | Not by transport itself | Inside the TLS tunnel |
| Video quality | Depends on encoder/codec | Identical for the same stream |
| Additional latency | No TLS handshake | Small TLS overhead |
| Compatibility | Very broad | Broad, but both endpoints need TLS support |
If your ingest provides an rtmps:// URL and your encoder supports it, use RTMPS. An older device that only supports rtmp:// may still require classic RTMP.
On IRL.com.de the panel shows the connection details valid for your stream. See RTMP/RTMPS with OBS for the complete setup workflow.
No. TLS and codec signaling are separate layers. Modern codecs over RTMP are signaled through E-RTMP (Enhanced RTMP). Whether HEVC or AV1 actually works depends on support at the sender, relay and destination.
Read more: Enhanced RTMP with HEVC and AV1.