Skip to main content

RTMP

RTMP (Real-Time Messaging Protocol) is the standard protocol that carries your stream from OBS to Twitch, YouTube or Kick.

RTMP is the transport layer of live streaming. When you press "Start Streaming" in OBS, the encoded video and audio are packaged into an RTMP connection and pushed to the platform's ingest server.

Server URL and stream key

An RTMP configuration has two halves: the server URL, published by the platform (for example rtmp://live.twitch.tv/app), and your stream key, unique to your account. The URL says where the stream goes; the key says whose channel it lands on. Anyone holding your key can broadcast as you.

Why a 1990s protocol is still standard

RTMP was created by Macromedia and later maintained by Adobe. Flash is long dead, but RTMP survived because it is simple, low latency and universally supported by ingest infrastructure. Every major platform still accepts it in 2026.

The modern alternatives

Why it matters

Understanding RTMP explains why simulcasting costs upload bandwidth: each platform needs its own RTMP connection unless you use a server-side redistribution service. It also explains most "failed to connect to server" errors — a wrong server URL, a rotated key, or a firewall blocking port 1935.

Frequently asked questions

What is the difference between RTMP and RTMPS?

RTMPS is RTMP wrapped in TLS encryption. It uses the same workflow but protects the connection in transit. Some platforms, including Facebook, require RTMPS.

Which port does RTMP use?

Port 1935 by default. Some corporate or campus networks block it; RTMPS on port 443 is often the workaround.

Should I switch from RTMP to SRT?

Only if you stream over an unreliable connection, such as mobile bonding or a rural link, and your platform supports SRT ingest. On a stable wired connection RTMP performs identically and is simpler to configure.

Related reading