Skip to content
Guide · RTMP protocol

RTMP streaming explained, and multiplied

RTMP is how most encoders hand a live stream to a platform: a server address plus a stream key. This guide explains RTMP and RTMPS in plain words, the settings that work on every major platform, and how to send one RTMP stream to YouTube, Twitch, Kick, Facebook and your own servers at once.

If your streaming app asks for a Server and a Stream Key, it's speaking RTMP.

1935
Port for RTMP
1936
Port for RTMPS
2 s
Keyframe interval
H.264 + AAC
Video and audio to send

Why RTMP still runs the streaming world

Every streaming app knows it

OBS, vMix, Streamlabs, hardware encoders and many cameras send RTMP, and YouTube, Twitch, Kick and Facebook all take it. Whatever you stream with, two fields get you on air: a server and a key.

A key instead of a login

A stream key works like a password for one channel. Platforms show it in their dashboard, and anyone who has it can broadcast to your channel. Keep it off screenshots and screen shares.

RTMPS when the route isn't yours

RTMPS is RTMP inside TLS, the encryption behind https: nobody along the way can read your key or your video. YouTube recommends it, and Kick's server address starts with rtmps://.

One stream can reach them all

A separate RTMP stream to every platform multiplies your upload. Send one to StreamRove and the copies are made on our side: three platforms at 6,000 kbps need about 9 Mbps up instead of about 26.

RTMP with StreamRove

RTMPS and RTMP for every stream

Each stream has rtmps://live.streamrove.com:1936/live and rtmp://live.streamrove.com/live, plus its own stream key. RTMPS is the default tab on the stream page.

Any RTMP destination

Besides the one-click platforms, add any service with an RTMP or RTMPS address as Custom RTMP: a display name, the RTMP URL, the stream key, and a username and password if the server asks for them.

One click where platforms allow it

YouTube, Twitch and Kick connect with one click, and StreamRove reads their keys itself. Facebook, LinkedIn, X and Instagram take a pasted server and key; LinkedIn issues a new key per event and Instagram one for every broadcast.

Encoder settings for your mix

The Output profile card works out the bitrate, frame rate, keyframe interval and audio bitrate that suit all your destinations, and shows which platform set each limit.

Every destination on its own

Each destination is a separate connection with its own switch and its own status: Reaching, Connecting… or Not reaching. One platform refusing the stream doesn't stop the others.

Keys kept out of sight

Destination keys are stored encrypted, and your StreamRove stream key stays hidden on the stream page until you choose to show or copy it.

Straight to each platform, or once through StreamRove?

Same protocol either way. The difference is how many streams leave your building.

StreamRoveDirect to each platform
Streams leaving your computer for three platforms✓ OneThree
Upload for three platforms at 6,000 kbps✓ About 9 MbpsAbout 26 Mbps
Different settings per platform— No: one stream goes to all✓ Yes, one encoder output each
Adding a platform while live✓ A switch on the stream pageAnother output to set up in the encoder
Stream keys✓ Stored once, encrypted; read automatically for YouTube, Twitch and KickPasted into each encoder output
Encryption on the way out✓ RTMPS to StreamRoveWhatever each platform's address offers
If the encoder dropsHolding screen on Control and up; Signal alerts on every planEvery platform goes offline

How to send one RTMP stream to every platform

The same steps work in OBS, vMix, Streamlabs or a hardware encoder; only the menu names change.

  1. Create a stream

    In StreamRove, click New Stream and pick Encoder | RTMP. The stream page opens on the RTMPS tab, with the RTMP tab beside it; each shows a URL and the stream key.

  2. Add your destinations

    Under Your Channels, add YouTube, Twitch or Kick in one click, or Custom RTMP for anything else. The stream key finder shows where 12 platforms keep their server and key.

  3. Choose RTMPS unless something stops you

    RTMPS is encrypted and runs on port 1936. Pick the RTMP tab only for an encoder that can't do RTMPS, or one that stutters on it.

  4. Paste the URL and the key

    OBS: Settings → Stream, Custom... as the Service, the URL in Server and the key in Stream Key. vMix: the cog next to Stream, Custom RTMP Server, then URL and Stream Key. Hardware encoders ask for the same two values, sometimes as one address with the key at the end.

  5. Set the encoder once for all destinations

    H.264 video, CBR, a keyframe interval of 2 seconds and AAC audio. Take the bitrate from the Output profile card: it follows the strictest destination you added.

  6. Start and check the preview

    Start streaming with the destinations switched off. The preview appears on the stream page about 10 seconds after the encoder connects, once the first keyframes arrive. Then switch the destinations on.

  7. Watch each destination

    Each one should change to Reaching. If one stays on Not reaching, check its key on the platform first: a reset or expired key is a common cause, and the others keep going while you fix it.

StreamRove's stream key finder for YouTube showing the RTMP server address rtmp://a.rtmp.youtube.com/live2, the RTMPS alternative and the settings YouTube accepts
An RTMP address and a stream key are all an encoder needs. Here, YouTube's, with its RTMPS alternative for networks that require encryption.

RTMP settings that work on every major platform

Values from the limits StreamRove applies per platform. With several destinations, the strictest one wins.

Server (RTMPS)rtmps://live.streamrove.com:1936/liveEncrypted, and the default tab on your stream page.
Server (RTMP)rtmp://live.streamrove.com/liveFor encoders without RTMPS, or ones that stutter on it.
Stream keyCopied from your stream pageOBS and vMix give it its own field; it doesn't go on the end of the URL there.
Video codecH.264The codec every destination accepts.
Rate controlCBRTwitch and YouTube ask for a constant bitrate, and Kick doesn't support variable bitrate.
Keyframe interval2 secondsWhat every major platform asks for. OBS's 0 (auto) means 8 seconds, and StreamRove warns above 4.
Video bitrate6,000 kbps with Twitch or Facebook, 8,000 with Kick alone, 9,000 with YouTube aloneThe figure StreamRove's profile gives each platform; the lowest one in your mix decides.
Picture1920 × 1080 at 30 or 60 fpsLinkedIn takes 30 fps at most.
AudioAAC, stereo, 48 kHz, 128 kbpsAccepted by every destination; 160 kbps is fine when only Twitch and Kick receive it.
Upload speedAbout 9 Mbps for a 6,000 kbps streamStreamRove's calculator keeps a stream under 70% of your upload.

Check your own line with the bitrate calculator: it measures your upload and gives you OBS settings to copy.

RTMP lessons that save a broadcast

Set the keyframe interval to 2

Platforms cut your stream into pieces at keyframes, the complete pictures an encoder sends every few seconds. OBS's 0 (auto) means 8 seconds on a custom server, which makes the stream slow to start for everyone watching. Set Keyframe Interval to 2 in Settings → Output, and the preview on your stream page appears in about 10 to 12 seconds instead.

Treat the stream key like a password

Anyone with the key can broadcast to your channel. Keep it out of screenshots, screen shares and chat. If a platform's key leaks, press Reset on that platform. For a destination you pasted into StreamRove, edit it with the new key; for a one-click platform, remove the destination and add it again so StreamRove reads the new one.

If RTMPS stutters, test plain RTMP

RTMPS adds encryption the encoder has to keep up with, and some encoders handle it badly. In one of our tests, vMix's built-in encoder dropped frames on RTMPS while plain RTMP from the same machine ran clean for 94 minutes. If the picture stutters and your bitrate fits your upload, try the RTMP tab before changing anything else.

Use SRT when the line is the problem

RTMP runs over TCP, which holds everything back until each lost piece arrives again. On a lossy line, that turns into stalls. SRT re-sends only what was lost, within a delay you choose. StreamRove takes SRT on the same stream (the SRT tab, 500 ms latency to start) and still delivers RTMP to every platform.

Frequently asked questions

What is RTMP?

RTMP (Real-Time Messaging Protocol) is the way most encoders send a live stream to a server. The encoder connects to an address that starts with rtmp://, identifies itself with a stream key, and pushes video and audio continuously, usually H.264 and AAC. It runs over TCP, the same kind of connection web pages use.

What's the difference between RTMP and RTMPS?

RTMPS is RTMP wrapped in TLS, the encryption behind https, so your key and video can't be read on the way. StreamRove's RTMPS address uses port 1936 and its RTMP address port 1935. YouTube recommends RTMPS, and Kick's server address starts with rtmps://.

Does StreamRove send RTMPS to the platforms?

StreamRove sends to the address each platform gives it: RTMPS where that's what the platform uses, as with Kick and Facebook, and plain RTMP where the platform's standard address is RTMP, as with Twitch's. The leg from your encoder to StreamRove is encrypted whenever you use the RTMPS tab.

What are the best RTMP encoder settings?

H.264 video at a constant bitrate, a keyframe every 2 seconds, AAC stereo audio at 128 kbps, and 1920 × 1080 at 30 or 60 fps. The bitrate depends on where you send: 6,000 kbps with Twitch or Facebook, up to 8,000 with Kick on its own. The bitrate calculator works it out for your mix and your upload.

Can I stream to my own RTMP server or a client's CDN?

Yes. Add it as Custom RTMP with a display name, the RTMP URL, the stream key, and a username and password if the server needs them. It receives the same stream as the platforms. With Broadcast delivery (Relay plan and up), SRT destinations in caller mode work too.

Can I send H.265 (HEVC) or AV1 over RTMP?

Some platforms accept them now; YouTube does. Send StreamRove H.264 video with AAC audio anyway: it's the pair every destination accepts, and Kick only accepts H.264. If your encoder stays on H.265 or AV1, the StreamRove relay converts the picture to H.264 (up to 1080p) before it goes out. The direct Cloudflare address on the stream page takes H.264 only.

Why does my RTMP stream keep disconnecting?

Usually the line. RTMP runs over TCP, and on a connection that loses data it stalls, then drops. Lower the bitrate, use a cable instead of Wi-Fi, or switch to SRT. If a platform refuses the stream at once, check the key and the settings: Kick, for example, rejects variable bitrate and H.265.

Is RTMP being replaced by SRT?

Not for the last step to the platforms: YouTube, Twitch and Kick still take RTMP or RTMPS from most encoders. For getting a stream out of a venue over a weak line, SRT is often the better choice. With StreamRove you can use both: SRT in, RTMP out to every platform.

What does Not reaching mean on a destination?

The platform isn't accepting the stream StreamRove sends it. Common causes are a reset or expired key, a platform that wants the broadcast set up first (LinkedIn issues a new key per event, Instagram one for every broadcast) and settings outside the platform's limits. The other destinations keep going while you fix it.

My network seems to block streaming. What can I try?

Try the RTMPS address first. If neither it (port 1936) nor plain RTMP (port 1935) connects, the network probably lets only web traffic out, as office and school networks sometimes do. Open “Stuttering? Send it straight to Cloudflare instead” under the address on your stream page and use the RTMPS address there: it runs on port 443, like secure websites. If that fails too, the network is blocking streaming and you'll need another connection, such as a mobile hotspot.

Keep reading

From the blog

One RTMP stream, every platform

Get your RTMPS address and key, add your destinations, and stream once.

Sign up for free