What is RTMP? Server URLs, stream keys and RTMPS explained

RTMP (Real-Time Messaging Protocol) is how almost every live stream gets from your encoder to a streaming platform. Viewers never touch it, but every time you paste a server URL and stream key into OBS, you're configuring an RTMP connection. Knowing how it works explains most of the streaming setup errors you'll ever meet.

Updated

RTMP in one paragraph

RTMP is a protocol for sending audio and video continuously over a single, long-lived TCP connection. It was created by Macromedia for Flash Player and later published by Adobe. Flash is long gone, but RTMP stayed on as the standard way to push a live stream into a platform. YouTube, Twitch, Facebook, LinkedIn, Kick and TikTok all accept it, and practically every encoder, from OBS to hardware boxes, can send it.

The important word is push. RTMP carries video one way, from you to the platform. The platform then converts it into formats viewers' devices play (usually HLS or DASH over ordinary web servers). That split, RTMP in and HLS out, is the architecture behind nearly every live platform.

The two values: server URL and stream key

Every platform asks your encoder for the same two things. The server URL (also called ingest URL, stream URL or RTMP URL) says which server to connect to. The stream key says which channel or broadcast the video belongs to.

A typical server URL looks like rtmp://live.example.com/app. The part after the host, here “app”, is the application path, and it matters. Copying only the domain is one of the most common reasons a stream won't connect. The encoder joins the URL and key together when it connects, so the full address it really dials is the server URL followed by the key.

The stream key works like a password for your channel: anyone with it can stream to your account. Treat it like one. Our stream key security guide covers how keys leak and what to do when one does.

RTMP vs RTMPS

RTMPS is RTMP inside a TLS-encrypted connection, the same encryption that puts the padlock on HTTPS websites. It stops anyone between you and the platform from reading your stream key or video. The URL starts with rtmps:// and usually uses port 443 instead of RTMP's 1935, which also helps on networks that block unusual ports.

Some platforms only accept RTMPS (Facebook and Instagram, for example). Others offer both. When a platform gives you an rtmps:// address, use it exactly as given. StreamHub accepts both rtmp:// and rtmps:// destination URLs and checks the format when you save a destination, so a malformed URL is caught then rather than failing at go-live.

RTMPRTMPS
URL prefixrtmp://rtmps://
Usual port1935443
EncryptedNoYes (TLS)
Stream key visible on the networkYesNo
Passes strict firewallsSometimes blockedUsually allowed

How a live stream travels, step by step

A multistreaming service adds one hop in the middle: your encoder pushes RTMP to the service, and the service opens a separate RTMP connection to each platform. See what is multistreaming for the full picture.

  • Your camera and microphone are captured by an encoder (OBS, vMix, a hardware box, or the browser).
  • The encoder compresses them, typically H.264 video and AAC audio, at a bitrate you choose.
  • It opens an RTMP connection to the server URL, authenticates with the stream key, and pushes the compressed stream continuously.
  • The platform's ingest server receives it and transcodes it into several qualities (1080p, 720p, 480p…) for adaptive playback.
  • Viewers' players download short segments over HLS or DASH and switch quality to match their connection.

Is RTMP outdated?

RTMP is old, and it has real limits: it runs over TCP, so a lossy connection causes stalls rather than brief glitches. The original specification doesn't cover newer codecs such as HEVC and AV1, although extended versions now do. And it isn't designed for delivery to viewers.

Newer protocols fix pieces of that. SRT handles lossy networks better and is popular in broadcast contribution. WebRTC (and its ingest form WHIP) gets latency under a second and is what browser-based studios use. But platform support decides what you can actually use, and RTMP is still the one ingest protocol every major platform accepts. For getting a stream onto YouTube, Twitch, Facebook and LinkedIn today, RTMP or RTMPS remains the default.

ProtocolTypical useAccepted by major platforms for ingest
RTMP / RTMPSEncoder → platformYes, universally
SRTContribution over unreliable networksSome
WebRTC / WHIPBrowser publishing, real-time callsFew, and not directly
HLS / DASHPlatform → viewersNot for ingest

Where StreamHub uses RTMP and where it doesn't

Encoders (OBS, Streamlabs, vMix, Ecamm, Zoom, hardware) send to StreamHub over RTMP. Each event has its own RTMP ingest URL and stream key, so different shows and different team members never collide.

The browser Studio doesn't use RTMP on your side. It publishes your camera and microphone with WebRTC, which is how browsers do real-time video, and guests join the same way. StreamHub then delivers to each platform over RTMP or RTMPS, as that platform requires. Whichever way video arrives, the platforms receive standard RTMP they accept.

Common RTMP errors and what they mean

  • “Failed to connect to server”: the URL is wrong or incomplete (often a missing application path), or a firewall is blocking port 1935. Try the platform's RTMPS address if it has one.
  • “Invalid stream key” or an instant disconnect: the key has a typo or stray space, or it has been reset. Keys created per broadcast (Instagram, some LinkedIn events) expire after use.
  • Connected, but the platform shows no video: the encoder is sending an unsupported format or no keyframes. Use H.264 with a 2-second keyframe interval.
  • Stream drops every few minutes: your upload can't keep up with the bitrate. Lower it or fix the connection. See how to fix dropped frames and disconnects.
  • Works at home, fails at the venue: corporate and school networks often block 1935. RTMPS on 443 or a different network usually solves it.

RTMP settings that matter

RTMP itself has almost no settings. What you tune is the encoding the connection carries. H.264 video, AAC audio, constant bitrate, and a keyframe every 2 seconds are accepted everywhere. The bitrate depends on resolution and on your upload. Best OBS settings for multistreaming gives exact values, and the streaming bitrate calculator works out what your connection can carry.

Custom RTMP destinations

Because RTMP is a standard, any service that publishes an RTMP ingest URL and key can be a destination, not just the big names. Kick, Vimeo, company video platforms, church streaming services and your own media server all work as a custom RTMP destination in StreamHub, alongside YouTube, Twitch and Facebook.

How to find your RTMP URL and stream key

Every platform keeps its RTMP details in the creator or live dashboard, usually under a heading like Stream, Streaming software, Go live or Encoder setup. Look for two fields labelled server (or URL) and stream key. Many dashboards hide the key behind a Show or Copy button. Copy it with the button rather than selecting the text, which can pick up a trailing space.

Our platform pages give the exact location for each: YouTube, Twitch, Facebook, LinkedIn, TikTok and Instagram. Some keys are persistent and can be saved once. Others are created per broadcast and must be refreshed each time.

In StreamHub you'll see two kinds of RTMP details. The destination details are the platform's URL and key, which you paste in once and which are encrypted and never shown again. The event's ingest URL and key are what your encoder streams to. They're different on purpose: your encoder only ever knows StreamHub's address, so your platform keys never sit in an encoder profile or a shared computer.

RTMP URL examples by platform

Platforms format their ingest addresses differently, but all follow the server-plus-key pattern. These show the shape you'll see, not values to copy. Always take the current URL from the platform's own dashboard, since platforms change ingest servers over time and some assign one per region or per broadcast.

PlatformShape of the server URLKey
YouTubertmp://a.rtmp.youtube.com/live2 (an rtmps:// address is also offered)Per channel or per stream
Twitchrtmp://<region>.contribute.live-video.net/appPrimary stream key
Facebookrtmps://live-api-s.facebook.com:443/rtmp/Per broadcast or persistent
Instagramrtmps://… from Live ProducerFresh per broadcast
LinkedInFrom the LinkedIn Live event's custom stream setupPer event
StreamHubShown on each eventPer event

How RTMP handles a bad connection

Because RTMP runs over TCP, every packet must arrive, in order. When your connection briefly loses packets, TCP resends them, and everything behind them waits. A short wobble becomes a pause. A longer one fills your encoder's output buffer. That's when OBS starts reporting dropped frames: it's discarding video it couldn't send in time.

This is why steady upload matters more than headline speed, and why a constant bitrate comfortably below your upload is the standard advice. It's also why multistreaming from your own computer is fragile: several RTMP connections share one uplink, and a wobble hits all of them together. With a cloud service your connection carries one RTMP stream, and the service's own data-centre connections carry the rest.

RTMP ingest vs playback: a common confusion

People sometimes ask how to watch an RTMP stream, or try to give viewers an RTMP link. Modern browsers can't play RTMP at all. Since Flash was retired, RTMP has only been for getting video into a platform. Viewers watch on the platform's own player, which uses HLS or DASH. If you run your own server, it converts RTMP to HLS for playback in the same way.

So the RTMP URL and key you see in StreamHub or YouTube Studio are for your encoder only. Share the watch page (the YouTube video link, the Facebook post, the LinkedIn event) with viewers, and never the RTMP details.

Glossary

  • Ingest: the server that receives your stream; the “in” side of a platform.
  • Stream key: the secret identifying your channel or broadcast to the ingest server.
  • Application path: the part of an RTMP URL after the host, such as /live2 or /app.
  • Encoder: the software or hardware that compresses video and sends it (OBS, vMix, a hardware box).
  • Transcoding: re-encoding video into different sizes or bitrates. Platforms do it for playback; StreamHub does it per destination.
  • Keyframe: a complete video frame that playback can start from; most platforms want one every 2 seconds.
  • HLS / DASH: the formats platforms use to deliver video to viewers in short downloadable segments.

Frequently asked questions

What does RTMP stand for?

Real-Time Messaging Protocol. It was created for Flash and remains the standard way encoders push live video to streaming platforms.

What is an RTMP server URL?

The address your encoder connects to, such as rtmp://live.example.com/app. It's paired with a stream key that identifies your channel or broadcast.

What is the difference between RTMP and RTMPS?

RTMPS is RTMP encrypted with TLS, usually on port 443. It protects your stream key and video in transit, and some platforms such as Facebook require it.

Is RTMP still used in 2026?

Yes. It's still the ingest protocol every major live platform accepts, even though viewers watch over HLS or DASH and browsers publish with WebRTC.

What port does RTMP use?

Port 1935 by default. RTMPS usually uses 443, which is why it often works on networks that block 1935.

Can I stream to my own RTMP server and to YouTube at the same time?

Yes. Add your server as a custom RTMP destination and YouTube as another, put both on one StreamHub event, and they receive the stream together.

Can viewers watch an RTMP link directly?

No. Browsers can't play RTMP. It's only used to send video into a platform, and viewers watch on that platform's player over HLS or DASH.

Why does my RTMP URL have a path like /live2 or /app?

That's the application path on the ingest server. It's part of the address, so copy the full URL, not just the domain.

Related reading

Platform setup guides

Go live everywhere from one stream

Free plan, no credit card, no downloads.