Skip to content
Guide · SRT protocol

SRT streaming for connections you can't trust

SRT is a way to send live video that copes with poor connections: when part of the stream goes missing, SRT asks for it again within a short delay you choose. Here you'll find SRT in plain words, the exact settings for OBS, vMix and other encoders, and how one SRT stream reaches YouTube, Twitch, Facebook and Kick through StreamRove.

SRT stands for Secure Reliable Transport. Haivision created it and released it as open source, and OBS, vMix and FFmpeg can all send it.

8890
SRT port on StreamRove
500 ms
Latency to start with
Caller
Mode for your encoder
H.264 + AAC
What the relay accepts

Why streamers switch to SRT

It copes with a bad line

SRT runs over UDP and asks again only for the pieces that went missing, inside the latency you set. RTMP runs over TCP and waits for every lost piece in turn: on a lossy line, that means stalls and then a dropped connection.

You decide how much delay to trade

SRT keeps a short buffer, called latency, and uses it to recover lost data. StreamRove suggests 500 ms to start. OBS's own guide asks for at least 2.5 times the round trip to the server: a long or mobile route needs more.

Platforms get the address they expect

YouTube's encoder settings list RTMP and RTMPS (plus HLS), and Facebook and Kick hand out RTMPS addresses. You send SRT to StreamRove; each platform receives your stream over the address it gave you.

One stream leaves the venue

Your upload carries a single SRT stream, and the copies for each platform are made on our side. Three platforms at 6,000 kbps need about 8.8 Mbps of upload instead of about 26.

SRT with StreamRove

An SRT address on every encoder stream

The SRT tab gives one ready-made URL and the same address in separate fields, with a settings line: port 8890, mode Caller, latency 500 ms, no passphrase.

SRT in, the platforms' own format out

The StreamRove relay passes your stream on, and YouTube, Twitch, Kick, Facebook and custom RTMP destinations each receive it the way they take streams.

Works with the encoder you have

OBS 25 or newer, vMix, Larix Broadcaster, FFmpeg and hardware encoders with an SRT caller mode. The relay takes H.264 video with AAC audio and names anything else it receives.

A status line for the link

The SRT tab says what the relay sees, such as 'Encoder connected over SRT — the relay is delivering' or no data for 15 seconds. The Broadcast Engineer panel watches bitrate, frame rate and keyframes.

A holding screen when the line gives out

On the Control plan and up, the Backup stream card keeps your destinations live with a holding screen until your encoder reconnects. It covers the gap; it isn't a second feed.

SRT out as well

A Custom SRT destination feeds a receiver that listens for SRT. With Broadcast delivery (Relay plan and up), the relay forwards your encoder's own signal untouched, 1080i50 included.

SRT into StreamRove, or RTMP from the venue to each platform?

Both get a show on air. The difference shows when the connection is poor, shared or far away.

StreamRoveRTMP to each platform
Lost data on a poor line✓ Asked for again within the latency you setWaited for in order: stalls, then a reconnect
Delay you addThe SRT latency, 500 ms to start withNone to set; it grows when the line struggles
Upload for three platforms at 6,000 kbps✓ About 8.8 Mbps: one streamAbout 26 Mbps: three streams
Encryption on the way in— None: StreamRove's SRT address has no passphrase✓ With RTMPS (TLS)
Networks that only let web traffic out— May be blocked: SRT uses UDP port 8890✓ Cloudflare's RTMPS address on the stream page uses port 443, like secure websites
If the encoder dropsHolding screen on Control and up; Signal alerts on every planEvery platform goes offline
Delivery to a broadcaster's SRT receiver✓ Custom SRT destination— Not possible over RTMP

How to send SRT to StreamRove and every platform

Set it up the day before, on the connection you'll actually use.

  1. Create an encoder stream

    In StreamRove, click New Stream and choose Encoder | RTMP. The stream page opens on the RTMPS tab; click SRT beside it.

  2. Add your destinations

    Under Your Channels, add YouTube, Twitch or Kick in one click, or Facebook, Custom RTMP and Custom SRT with a pasted address. Leave them off for the first test.

  3. Copy the SRT address your encoder wants

    Single URL holds everything in one line, which OBS and most software take. Separate fields gives Server, Stream ID and a settings line, for encoders with a box for each.

  4. OBS: paste the URL into Server

    Open Settings → Stream, choose Custom... as the Service, paste the SRT URL into Server and leave Stream Key empty. Add &latency=500000 to the end of the URL for 500 ms: OBS reads SRT latency in microseconds.

  5. vMix, apps and hardware: fill in the fields

    Set the mode or type to Caller, host live.streamrove.com, port 8890 and latency 500 (milliseconds). Paste the Stream ID whole and leave the passphrase empty. Our vMix guide has vMix's screens.

  6. Send H.264 video and AAC audio

    Use H.264 at a constant bitrate of up to 6,000 kbps, a keyframe every 2 seconds and AAC audio at 128 kbps. The relay converts H.265, AV1, Opus and MP3 for you, but H.264 and AAC go out untouched.

  7. Start, read the status line, then go live

    Start streaming. The SRT tab should read 'Encoder connected over SRT — the relay is delivering', and the preview appears. Switch your destinations on and check that each one shows Reaching.

SRT settings, field by field

Copy values from your stream's SRT tab; here is what each one means and what encoders call it.

Mode / TypeCallerYour encoder calls StreamRove, which listens. OBS uses caller by default; vMix calls the setting Type.
Host / Serverlive.streamrove.com, or srt://live.streamrove.com:8890 in a single server fieldThe StreamRove relay. Copy it from the SRT tab.
Port8890SRT travels over UDP: the network you stream from must let UDP out on this port.
Stream IDThe value under Separate fields, starting publish:live/Identifies your stream and works like a password. Replace relay key issues a new one.
Latency500 ms; in an OBS URL, &latency=500000OBS and FFmpeg count SRT latency in microseconds; vMix and most hardware count milliseconds.
PassphraseLeave emptyStreamRove's SRT address uses none. The stream isn't encrypted on the way in.
VideoH.264, CBR, keyframe every 2 s, up to 6,000 kbpsWhat the SRT tab asks for. The relay converts H.265 and AV1 to H.264, up to 1080p.
AudioAAC, stereo, 128 kbps, 48 kHzStreamRove's advice. The relay converts Opus and other audio codecs to AAC.

Measure the upload of the computer that will stream with the bitrate calculator: the SRT tab's numbers assume the line can carry them.

What SRT teaches you on bad connections

Set latency from the route, not from habit

OBS's guide asks for a latency of at least 2.5 times the round trip between encoder and server. StreamRove's 500 ms suits a steady wired line; on mobile data, hotel Wi-Fi or a route across continents, raise it in steps and test again. Every millisecond you add is delay your viewers wait for, on top of each platform's own. Stop as soon as the picture holds.

Leave room for the resends

SRT recovers lost data by sending it again, and those resends share the upload with the stream itself. A connection filled to the brim has no room for them. Keep your bitrate well under what the line carries: StreamRove's bitrate calculator plans a stream at no more than 70% of your measured upload, and the SRT tab suggests up to 6 Mbps.

Test on the worst connection of the day

Test on the line you'll have during the show: the venue Wi-Fi, the phone hotspot, the shared office network. Keep every destination off and watch the SRT tab's status line for a few minutes while people use the network. In our own test on 16 September 2026, SRT to the relay held 6 Mbps at 30 fps with nothing dropped on a line where RTMP stuttered.

When SRT won't connect at all

A stream that never appears usually means outgoing UDP is blocked or the Stream ID was cut short while copying. Paste it again, whole, starting with publish:live/. On a network that only lets web traffic out, use the RTMPS tab and the Cloudflare address folded under it, which runs on port 443. If a Stream ID leaks, Replace relay key makes a new one and disconnects the old.

Frequently asked questions

What is SRT streaming?

SRT (Secure Reliable Transport) is an open-source protocol for sending live video over the internet, created by Haivision. It runs over UDP, asks again for data that goes missing, and keeps a fixed delay you choose, called latency. That makes it steadier than RTMP on Wi-Fi, mobile data and long routes.

Is SRT better than RTMP?

For getting a stream out of a building over an unreliable line, usually yes: SRT recovers lost data instead of stalling. On a good wired line, RTMPS works as well and needs no latency setting. Our RTMP guide covers that side.

What SRT latency should I use?

Start with 500 ms, StreamRove's advice. OBS's guide asks for at least 2.5 times the round trip between encoder and server; long routes and mobile links need more, so raise it in steps and test. Mind the units: vMix and most hardware use milliseconds, OBS and FFmpeg microseconds. In an OBS URL, 500 ms is latency=500000.

How do I stream SRT from OBS?

In Settings → Stream, choose Custom... as the Service, paste the whole SRT URL from your stream's SRT tab into Server and leave Stream Key empty. The URL already holds the Stream ID; add &latency=500000 to the end for 500 ms. OBS 25 or newer is needed, and the rest is in our OBS guide.

Can I send SRT straight to YouTube, Facebook or Kick?

Not with their standard addresses. YouTube's encoder settings list RTMP and RTMPS (plus HLS), and Facebook and Kick give you RTMPS addresses. Send SRT to StreamRove and each platform receives your stream over the address it gave you.

Is my SRT stream to StreamRove encrypted?

No. SRT can encrypt with a passphrase, but StreamRove's SRT address uses none: the stream travels unencrypted, as over plain RTMP. Treat the Stream ID like a password. If the route needs encryption, use the RTMPS tab, which wraps the stream in TLS.

Which encoders can send SRT?

OBS Studio 25 or newer, vMix (as an output), Larix Broadcaster on iOS and Android, FFmpeg and many hardware encoders: look for SRT with a caller mode in the manual. vMix has its own walkthrough in our vMix guide.

Why does StreamRove refuse my SRT stream?

The SRT tab gives the reason. 'The stream key isn't recognised' means the Stream ID is wrong or has been replaced: copy it again. A codec message says what the relay couldn't use, such as sound with no picture. If it says the relay has no converter free for your H.265 video, switch the encoder to H.264 and start again with the same address.

Can StreamRove send SRT on to a broadcaster or my own server?

Yes. Add a Custom SRT destination with the receiver's srt:// address; its listener must be running first, because StreamRove calls it. With Broadcast delivery (Relay plan and up), the relay forwards your encoder's signal untouched, keeping the 1080i50 that the standard route turns into 25p.

Can I use StreamRove as an SRT to RTMP gateway?

Yes. Send SRT in and YouTube, Twitch, Kick, Facebook and any RTMP server receive the stream over RTMP or RTMPS, while a broadcaster's receiver can get SRT again. The SRT gateway page covers routing a contribution feed, Broadcast delivery and 1080i50.

Keep reading

From the blog

Bring your SRT stream to every platform

Copy one SRT address into your encoder, add your destinations, and test it on your worst connection.

Sign up for free