RTMP RTMPS TLS OBS

RTMP vs. RTMPS: What is the difference?

By IRL.com.de Published: Updated:

Short answer: RTMPS is RTMP over TLS. The basic streaming workflow and audio/video codecs do not change, but the connection between encoder and ingest is encrypted and authenticated. When both your encoder and server support RTMPS, it is therefore usually the better choice.

What stays the same with RTMPS?

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.

What does TLS encryption add?

Important: RTMPS protects transport to the relay. What a destination platform does with the stream afterwards is a separate part of the delivery chain.

RTMP and RTMPS compared

PropertyRTMPRTMPS
Transport encryptionNoYes, TLS
Stream key protectedNot by transport itselfInside the TLS tunnel
Video qualityDepends on encoder/codecIdentical for the same stream
Additional latencyNo TLS handshakeSmall TLS overhead
CompatibilityVery broadBroad, but both endpoints need TLS support

Which should I use in OBS?

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.

Is RTMPS related to HEVC or AV1?

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.

Primary sources & technical documentation

← All guides