RTMPS
RTMPS is RTMP (Real-Time Messaging Protocol) sent inside an encrypted TLS connection, the same security layer that protects HTTPS websites. It carries live video from an encoder to a streaming platform exactly like RTMP, but nobody between the two can read or alter the stream or its stream key. It usually runs on port 443, which firewalls rarely block.
Why it matters
A leaked stream key lets anyone broadcast on your channel or intercept a private event. RTMPS encrypts the stream and key in transit, which protects paid events, internal company broadcasts and brand reputation. It costs almost nothing to adopt, since most encoders already support it.
How it works
- The encoder connects to an rtmps:// server address instead of an rtmp:// address.
- The encoder and server perform a TLS handshake and agree on encryption keys.
- The stream key and the video and audio data travel inside that encrypted connection.
- The server decrypts the stream and passes it on for transcoding and delivery to viewers.
Is RTMPS more secure than RTMP?
Yes. RTMPS encrypts the connection with TLS, so the stream key and video cannot be read or changed by anyone between the encoder and the server. Plain RTMP sends everything in the clear. RTMPS does not control who can watch the finished stream; that needs viewer-side protections such as signed playback URLs or DRM. Both sides can be covered in one FastPix setup: encrypted RTMPS ingest from the encoder, and playback tokens or live DRM so only the viewers you allow can watch.
What port does RTMPS use?
RTMPS most commonly uses port 443, the standard HTTPS port. Because nearly every network allows traffic on port 443, RTMPS rarely gets blocked by corporate or venue firewalls. Plain RTMP uses port 1935 by default, which some locked-down networks block, so switching to RTMPS can also fix connection problems.
Where it's used
Video platforms, live sports producers and corporate teams running town halls use RTMPS to send live streams encrypted, so stream keys and confidential content cannot be intercepted on public networks.
Where it usually goes wrong, and how FastPix handles it
Teams often leave encoders on plain RTMP for convenience, exposing stream keys on shared venue or hotel networks where traffic can be watched.
RTMPS is one of two ingest protocols FastPix accepts, alongside SRT; plain RTMP is not accepted. Streams reach viewers as LL-HLS and are recorded automatically for on-demand playback. A town hall or paid event stays protected on venue Wi-Fi, and the recording is ready to share without a second upload.
