RTMP vs. RTMPS: What is the difference?
RTMP and RTMPS mainly differ in transport encryption. Learn when RTMPS is the better choice and what stays identical.
RTMP/RTMPS with OBS, vMix and encoders
For OBS, vMix, action cams and other RTMP-capable encoders, create a panel stream with ingest RTMP / RTMPS. The RTMP server is powered by OpenRTMP and librtmp2-server and supports legacy RTMP as well as Enhanced RTMP (e-rtmpv1/v2).
Create the stream in the panel
- Create a stream with ingest RTMP / RTMPS.
- Copy the RTMP publish URL and stream key – or the complete URL from the panel.
- Optional: use the displayed RTMPS URL for encrypted transport.
Set up OBS as a publisher
- Open OBS: Settings → Stream.
- Service: Custom streaming server.
- Server: the RTMP or RTMPS URL from the panel (without the key).
- Stream key: the key from the panel.
- Apply and start streaming.
Player vs. publish: OBS can also receive the relay stream as a player – that is a different workflow. See OBS as a player.
Legacy vs. Enhanced RTMP
- Legacy RTMP (typically H.264) – works with virtually all encoders.
- Enhanced RTMP (E-RTMP) – extends RTMP with modern codec signaling when sender, relay and destination support it.
For HEVC, AV1 and FourCC details, see Enhanced RTMP explained.
Players, statistics and push targets work the same after publish as with SRT/SRTLA.
RTMPS
When the panel shows an RTMPS URL, prefer it for encrypted connections between encoder and relay. Firewall and encoder must be able to reach the RTMPS port.
See RTMP vs. RTMPS for the transport-security difference.
Quick checklist
- Panel ingest = RTMP/RTMPS (not SRT by mistake)
- Publish key, not a player URL
- On timeout: panel URL/port, firewall, key typos
- Push targets only start once ingest arrives – see push targets