What Is RTMP, and Why Is Your Stream Still Using It?
By Mira Okonkwo··6 min read
Real-Time Messaging Protocol is how your encoder hands video to a platform. Adobe built it for Flash, Flash died in 2020, and RTMP is still the front door at Twitch, YouTube and Kick — because nothing replaced the one job it does well.
The URL and the key are different things
Every platform gives you two strings and most guides blur them together. They have opposite security properties, which is the part worth getting right.
Server URL
rtmp://ingest.global-contribute.live-video.net/appThe address of the ingest server. Public, not a secret, and specific to the platform and often to a region. This is the half that goes stale when a platform changes infrastructure.
Stream key
live_123456789_AbCdEf…Your identity and authorisation in one string. Anyone holding it can broadcast to your channel, which is why it should never appear on stream, in a screenshot, or in a support thread. Platforms let you reset it; do that the moment it leaks.
The key is a password that looks like a setting. It grants the holder the ability to broadcast as you. Treat a stream key visible in a screenshot the way you would treat a visible password — reset it immediately rather than hoping nobody paused the VOD.
Do not copy an RTMP URL out of an article
Including this one. Ingest addresses change when a platform moves infrastructure, and published guides do not change with them — which is why "my stream will not connect" so often traces back to an address someone pasted from a search result.
A concrete example, checked while writing this. Querying Twitch's own ingest endpoint on returned 14 servers, with a default of:
rtmp://ingest.global-contribute.live-video.net/appRegional entries follow the same pattern — euc10 for Frankfurt, eun10 for Stockholm and so on, all under contribute.live-video.net. Most articles ranking for this question still print rtmp://live.twitch.tv/app, which is not what Twitch hands out today. Read the list yourself at ingest.twitch.tv/ingests; OBS also fetches it for you when you select Twitch as the service instead of Custom.
The same logic applies everywhere else, which is why there is no table of ingest URLs on this page. Take YouTube's from Live Control Room and Kick's from its creator dashboard, at the moment you need them.
Why a dead protocol is still the default
RTMP stopped being how viewers receive video a long time ago — that is HLS and DASH, which chop the stream into segments a browser can fetch over ordinary HTTP. What survived is the first hop: encoder to ingest server, one connection, well understood, implemented in every encoder ever written.
Replacing it is less attractive than it sounds. SRT handles packet loss better and is genuinely the right tool over a shaky link. WHIP carries WebRTC and gets latency down to something conversational. Both solve real problems — and neither solves the problem of several million existing setups that already work. So the major platforms keep RTMP as the standard entrance and add the others beside it.
Twitch also runs Enhanced Broadcasting, which sends multiple encodes over a single connection rather than replacing the protocol underneath. Its limits and codec support have moved more than once, and published figures disagree, so check Twitch's own broadcasting guidelines rather than a number from an article — this one included.
If the connection is the thing failing
A correct URL and key still will not help if the line underneath cannot carry the stream. Dropped frames with a valid connection are a bandwidth or routing question, not a protocol one — our upload speed guide has the one test that tells those two apart. For what to send once you are connected, the bitrate and encoder cheat sheet covers settings per platform, and the OBS setup guide is where the Custom service fields live.
Frequently Asked Questions
What is RTMP?
Real-Time Messaging Protocol — the protocol your encoder uses to send video to a streaming platform. Adobe built it for Flash, Flash died in 2020, and RTMP outlived it because the job it does well, getting one stream from an encoder to an ingest server reliably, never stopped being needed. It is no longer how viewers receive video — that is HLS or DASH — but it is still how almost every stream starts. Twitch's own broadcasting documentation names RTMP as the protocol its tools send with.
What is an RTMP URL?
The address of the ingest server your encoder connects to, for example rtmp://ingest.global-contribute.live-video.net/app. It is paired with a stream key, which is the part that identifies and authorises you. The URL is public; the key is not. In OBS the two are entered separately under Settings → Stream when you pick the Custom service.
Where do I find my RTMP URL and stream key?
From the platform, not from a guide. On Twitch the ingest list lives at ingest.twitch.tv/ingests and the key is in Creator Dashboard → Settings → Stream. YouTube shows both in Live Control Room, Kick in its creator dashboard. This matters more than it sounds: when we queried Twitch's ingest endpoint on October 24, 2026 it returned 14 servers with a default of rtmp://ingest.global-contribute.live-video.net/app, while most published guides still print rtmp://live.twitch.tv/app. Copying an address from an article is a common reason a stream will not connect.
What is the difference between RTMP and RTMPS?
RTMPS is RTMP inside a TLS connection — the same protocol with the transport encrypted, the way HTTPS relates to HTTP. It protects the stream key in transit and stops intermediaries reading the feed. Some platforms accept both and some require RTMPS. If an encoder offers it and the platform supports it, there is no reason to use plain RTMP.
Is RTMP obsolete in 2026?
Not for ingest. It was replaced long ago for delivery to viewers, where HLS and DASH took over, and newer ingest protocols exist — SRT handles unreliable networks better, and WHIP carries WebRTC for genuinely low latency. But the major platforms still take RTMP as their standard ingest, every encoder speaks it, and that combination keeps it in place. Twitch also runs Enhanced Broadcasting, which sends several encodes over one connection rather than replacing the protocol; its exact limits and codec support change, so read Twitch's own guidelines rather than a secondhand figure.
Why does RTMP add a few seconds of latency?
Partly the protocol and mostly everything after it. RTMP itself is reasonably quick to the ingest server; the delay a viewer experiences comes from transcoding and from the segmented delivery format they are watching, which buffers by design. Switching your ingest to SRT will not meaningfully reduce what a Twitch viewer sees, because the segments on the far end are what set the floor. Low-latency modes on the platform side are the lever that works.
When should I use SRT instead of RTMP?
When the connection between you and the ingest server is the problem — mobile bonding, a remote venue, anything crossing a long or lossy path. SRT recovers from packet loss in a way RTMP does not, which is why IRL setups reach for it. On a stable wired home connection it buys you very little, and the platform has to accept it, which not all do.