How to multistream from Streamlabs, vMix, Ecamm Live, XSplit or any RTMP encoder

Multistreaming doesn't depend on which software you use. Any encoder with a custom RTMP setting can send one stream to StreamHub, and StreamHub delivers it to every platform you've added. Here's where that setting lives in the popular encoders, the trade-offs against their own built-in multistream features, and how to tune each one.

Updated

The one setting every encoder needs

Every streaming application, from free desktop software to rack-mounted hardware, uses the same two values to know where to send video: a server URL and a stream key. When you stream directly to Twitch, those are Twitch's values. To multistream, you swap them for the ingest URL and stream key of a StreamHub event, and the encoder doesn't need to know anything else.

So the rest of this guide is mostly about finding the custom RTMP option in each tool. If you'd like the background first, what is RTMP explains how URLs and keys fit together, and how to stream to multiple platforms at once compares this approach with streaming several outputs from your own computer.

Before you configure the encoder

Streamlabs Desktop

Streamlabs Desktop is built on OBS, so it streams over RTMP in the same way. Open Settings → Stream, change the stream type from a named service to Custom Streaming Server, and paste the StreamHub ingest URL into URL and the key into Stream key. Save, and Go Live sends to StreamHub.

Streamlabs also offers its own multistreaming, tied to its subscription tiers. It's convenient if you already pay for it. A separate service makes sense when you want destinations Streamlabs doesn't cover, per-destination vertical encoding, a team sharing the same destinations, or the same setup whether you're streaming from Streamlabs, OBS or a browser. Check Streamlabs' current plans for what its own feature includes.

Streamlabs' Go Live dialog may try to set titles on connected platforms. With a custom server it can't, so set titles in each platform's dashboard, or on the LinkedIn and YouTube scheduled events, before you go live.

vMix

vMix is a Windows live production suite used for church, corporate and sports productions. Click the cog next to the Stream button to open streaming settings, choose Custom RTMP Server as the destination, and paste the StreamHub ingest URL and stream key. Pick a quality preset that matches what your upload can carry, and start the stream.

vMix can send several streams itself, but each one is encoded and uploaded from your production machine. Sending one stream to StreamHub frees that CPU for the production and keeps your upload at one stream, while StreamHub handles the rest. You can also mix the two: keep a direct stream to one platform for redundancy and send the second vMix output to StreamHub for everything else.

Ecamm Live (Mac)

Ecamm Live is a popular Mac app for interviews and business shows. In its destination menu choose the custom RTMP option, then paste the StreamHub ingest URL as the server and the event key as the stream key. Ecamm sends to StreamHub, and StreamHub sends to every destination on the event.

Ecamm can also connect directly to some platforms with sign-in. Those integrations post titles and descriptions for you, so set those yourself on each platform when you use a custom RTMP destination. Ecamm's guests join through its own interview feature. If you'd rather your guests join from a browser link instead, see the browser Studio.

XSplit Broadcaster

In XSplit, open Broadcast → Set up a new output → Custom RTMP. Give the output a name, paste the StreamHub URL and stream key, and choose the encoder and bitrate. The new output appears in the Broadcast menu. Start it to go live everywhere the event is configured to reach.

Hardware encoders and video switchers

Dedicated encoders and switchers with built-in streaming nearly always have a custom RTMP option, sometimes labelled “Custom”, “RTMP push” or “Generic RTMP”. Enter the StreamHub URL and key there. Some models list only named platforms in their menus and take custom servers through their companion software or a configuration file. The manufacturer's manual will say which.

Hardware pairs especially well with a cloud service. The box is reliable but usually streams in one shape at one bitrate, and every extra destination it sends to costs another full stream of upload. Sending one stream to StreamHub keeps the box simple and lets the cloud produce a vertical version for TikTok or Instagram as well.

Mobile apps and other software

Any app that offers RTMP, custom RTMP or “stream to custom server” works the same way, including several mobile streaming apps, Wirecast and production tools built on FFmpeg. If an app only lists named platforms and has no custom field, it can't send to a multistreaming service directly.

If you don't need a desktop encoder at all, the browser Studio streams camera, microphone and screen straight from Chrome, Edge, Firefox or Safari.

Why the settings above work

Constant bitrate keeps your upload predictable, so it doesn't burst past what the connection can carry during fast motion. A 2-second keyframe interval lets platforms start playback quickly and is what most of them ask for. 30 fps is plenty for talking heads, worship, classes and most events, and it halves the encoding work compared with 60 fps.

For the reasoning behind each value, and the OBS-specific menus, read best OBS settings for multistreaming. The bitrate calculator will tell you whether your connection can carry a given quality.

Built-in multistreaming vs a separate service

QuestionEncoder's own multistreamEncoder → StreamHub
Upload per extra platformUsually a full extra streamNone
Vertical 9:16 for TikTok / InstagramDepends on the encoderYes, encoded separately per destination
Works if you switch softwareNo, tied to that encoderYes, any RTMP source or the browser
One destination failingVariesIsolated; restarts automatically
Team access to destinationsUsually one userShared workspace with roles

Common mistakes

  • Pasting only the server's domain. Copy the full ingest URL including its path.
  • A space before or after the stream key. It looks identical and fails silently.
  • Leaving the encoder on a named service (Twitch, YouTube) while pasting a StreamHub key. Switch to custom RTMP first.
  • 60 fps at a bitrate meant for 30 fps. Motion looks smeared and blocky. Raise the bitrate or drop to 30 fps.
  • Variable bitrate on a tight connection. Spikes trigger dropped frames. Use CBR.
  • Testing on the real channel with an audience waiting. Make a test event with one private or unlisted destination first.

Testing your encoder before the real show

Whatever encoder you use, test the whole chain before anyone is watching. Create a test event in StreamHub with a single unlisted YouTube destination, or a private one on another platform. Point the encoder at it, stream for five minutes, and check three things: the encoder's own stats show no dropped frames, the StreamHub dashboard shows the destination as live with a steady incoming bitrate, and the playback on YouTube looks and sounds right on a phone.

Then switch the encoder to the real event. Because every event has its own key, the test never touches your public channels, and your encoder settings carry over unchanged. Repeat the test whenever you change the encoder, the network, or the venue. Most failed first streams come down to a setting that was never tried end to end. If the test shows dropped frames, how to fix dropped frames and disconnects walks through the causes in order of likelihood.

Picking an encoder if you haven't yet

If you're choosing an encoder for a multistreamed show, pick for the production, not the multistreaming. Any of these can send one stream to StreamHub, so the question is which one makes your show easiest to run.

EncoderPlatformGood for
OBS StudioWindows, Mac, Linux; freeMost creators; huge plugin ecosystem
Streamlabs DesktopWindows, MacCreators who want alerts and widgets built in
vMixWindowsMulti-camera church, corporate and sports productions
Ecamm LiveMacInterview shows and business streams on a Mac
XSplit BroadcasterWindowsPresentation-style streams and gaming
Hardware encoderStandalonePermanent installs that must not depend on a PC
StreamHub browser StudioAny modern browserNo install, remote guests, locked-down computers

Running a backup stream

For high-stakes events, some teams run a backup path. One approach is a second encoder (often a hardware box) on a different internet connection, ready to send to the same StreamHub event if the primary machine fails. Only one source should stream to an event at a time, so the backup stays stopped until it's needed. Switching over is then one button on the backup, and every destination picks up again on its own.

A lighter option is to keep the primary encoder recording locally while it streams. If the connection fails mid-event, you still have a full-quality file to upload afterwards, and StreamHub's cloud recording (on paid plans) gives you the broadcast copy as well.

Moving from built-in multistreaming to StreamHub

If you currently use your encoder's own multistream, switching is quick. Add each platform's stream key to StreamHub once. Then remove the extra outputs from your encoder and set its single output to the StreamHub event. Your scenes, overlays and audio setup don't change. You'll see the difference straight away in your encoder's stats: CPU and upload drop back to what one stream uses.

Keep the old configuration exported until after your first full show, in case you need to compare or roll back. Most encoders can export a profile or scene collection.

Frequently asked questions

Can I multistream from Streamlabs without Streamlabs Ultra?

Yes. Set Streamlabs Desktop to a Custom Streaming Server pointing at StreamHub. Streamlabs sends one stream and StreamHub delivers it to every platform on your event.

Does vMix support streaming to multiple platforms?

vMix can send several streams itself, each encoded and uploaded from your machine. Sending one stream to StreamHub instead keeps the upload to one stream and lets StreamHub add vertical outputs.

Can Ecamm Live stream to a custom RTMP server?

Yes. Choose Ecamm's custom RTMP destination and paste the StreamHub event's URL and stream key.

Will StreamHub work with my hardware encoder?

If the encoder can push RTMP to a custom server, yes. StreamHub accepts standard RTMP from any source.

Do I need to change encoder settings for each platform?

No. You send one stream; StreamHub encodes each destination to suit it, including vertical outputs for TikTok and Instagram.

Does StreamHub accept SRT or WHIP?

StreamHub's ingest takes RTMP from encoders, which every tool in this guide supports, plus WebRTC from its own browser Studio.

Can two encoders send to the same StreamHub event?

Use one encoder at a time per event. Keep a backup encoder ready with the same details but stopped, and start it only if the primary fails.

Related reading

Platform setup guides

Go live everywhere from one stream

Free plan, no credit card, no downloads.