> For the complete documentation index, see [llms.txt](https://captivatehelp.newbluelive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://captivatehelp.newbluelive.com/set-up-your-production/chapter-index-6/streaming-to-multiple-destinations.md).

# Stream to multiple destinations

> *Availability — included in Enterprise.*

Captivate can send the same program to several places at once — YouTube and Twitch and LinkedIn together, or a mix of RTMP services and SRT links. It encodes your program once and sends that same encoded video and audio to every destination you’ve switched on.

{% hint style="info" %}
Without multi-destination streaming you can configure one destination; adding or arming a second one tells you *"Your license only includes one destination."*
{% endhint %}

## Set several destinations going

1. Open **Settings** > **Streaming…**.
2. Add each destination in turn — see [Streaming with Captivate](/set-up-your-production/chapter-index-6/set-up-streaming.md) for the details of each type.
3. Switch on the ones you want on air. Their rows read **On air when you start**; the rest read **Off** and stay behind.
4. Check the footer. It counts what’s armed — **Going live to 3 destinations** — so you can confirm before you commit.
5. Go live with **Start Streaming** on the top bar.

Each destination connects on its own, so they don’t all come up at the same instant. Watch them arrive in the status readouts along the bottom of the window — see [Per-destination streaming status](https://github.com/NewBlueFX/help-docs/tree/gitbook-test/gitbook/build-out-your-production/streaming-and-delivery/get-started/the-interface/top-bar-status-meaning.adoc#per-destination-streaming-status).

**💡 TIP**\
Keep destinations you use occasionally in the list and just leave them **Off**. Configuring a channel once and arming it on the night is quicker and safer than re-entering a stream key under pressure.

## One encode for all of them

There is a single **Resolution & bitrate** setting for the whole broadcast, and it lives in each destination’s editor under a divider. Change it anywhere and it changes everywhere — Captivate warns you the first time with a **Shared Setting** prompt.

That has two practical consequences.

**Choose a format the strictest destination will accept.** Services cap what they’ll take, and the cap that matters is the lowest one among the destinations you’ve armed. Captivate names it for you in the footer, *"Twitch accepts up to 6000 Kbps — this format may be refused."*, and explains the reasoning if you hover:

*"Your program is encoded once and the same video is sent to every destination, so the format has to suit the strictest one. Lower it, or switch that destination off."*

It’s a warning rather than a block, so you can go ahead if you know the service will cope. Note that it only counts **armed** destinations: switching a demanding one off changes the advice.

**Budget your uplink for the copies, not the encodes.** One encode at 6000 Kbps sent to three destinations still puts roughly three times 6000 Kbps on your connection. If the picture breaks up as you add destinations, the encode isn’t the problem — the upload is. Lower the format, or drop a destination.

## Mixing SRT and RTMP

An SRT destination sits in the list alongside the RTMP services and behaves the same way — arm it, and it goes live with the others. This is the usual way to feed a broadcast facility over SRT while simultaneously streaming to social platforms.

Every destination counts toward your license’s destination limit, whether it’s RTMP or SRT.

## When one destination fails

A failed destination doesn’t take the others down. Captivate keeps streaming to everything that’s working, retries the failed one on its own (see [When a destination drops](https://github.com/NewBlueFX/help-docs/tree/gitbook-test/gitbook/build-out-your-production/streaming-and-delivery/build-out-your-production/streaming-and-delivery/set-up-streaming.adoc#reconnect-behavior)), and leaves it showing **Error** if it can’t recover. Your broadcast is never stopped because one service went away.

A failure is reported in the status readouts rather than by interrupting you, so make them part of your watch during a show. The summary beside the elapsed time on the top bar is the quickest check — `Connected (2)` means two destinations are up. If that count is lower than the number you armed, hover the one showing **Error** to find out why.

This applies even if every destination fails: the session stays open and keeps retrying rather than shutting itself down. Stop it yourself with **Stop Streaming** once you know what’s wrong.

## Remove them in bulk

Right-click an empty part of the destination list and choose **Remove All Destinations**. Captivate asks *"Remove all N destinations and their stream keys?"* and defaults to **No**, because the stream keys go too — you’ll be fetching them from each service again.

To clear just one, use its right-click **Remove Destination**, or the bin button that appears when you hover over the row.

## See also

* [Streaming with Captivate](/set-up-your-production/chapter-index-6/set-up-streaming.md) — the Streaming dialog, destination types, and going live
* [Stream with SRT](/set-up-your-production/chapter-index-6/streaming-with-srt.md)
* [Per-destination streaming status](https://github.com/NewBlueFX/help-docs/tree/gitbook-test/gitbook/build-out-your-production/streaming-and-delivery/get-started/the-interface/top-bar-status-meaning.adoc#per-destination-streaming-status)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://captivatehelp.newbluelive.com/set-up-your-production/chapter-index-6/streaming-to-multiple-destinations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.