Back

Blog details

Restream to Multiple Platforms With AIOZ Stream Multicast

AIOZ Network
6 min readNovember 20, 2026
aioz-stream
AIOZ Stream knowledge hub cover with the headline Restream to Multiple Platforms With Stream Multicast

To restream to multiple platforms, you send one live feed to a relay that copies it to each destination, such as YouTube, Twitch and Facebook. Your encoder uploads once, and the relay makes every extra copy for you.

TL;DR:

  • Restreaming, also called multistreaming or simulcasting, sends one live broadcast to several platforms at the same time.
  • You can do it from your encoder, through a cloud relay, or on your own relay server, and the main difference is how much upload bandwidth you need.
  • At 6,000 Kbps of video plus 160 Kbps of audio, three encoder outputs need about 18.5 Mbps of upload, while one relayed stream needs about 6.2 Mbps.
  • Check each platform's rules first: Twitch says its stream must not be worse than your other destinations, and Facebook's Live API requires RTMPS.
  • On AIOZ Stream, multicast keeps a list of destination RTMP URLs on your stream key, set in the dashboard or through the /api/live_streams/multicast/:stream_key endpoints.

What does it mean to restream to multiple platforms?

Restreaming means taking a live broadcast that is already running and forwarding it, as it arrives, to more destinations. Twitch defines simulcasting, or multistreaming, as broadcasting the same stream to multiple platforms at once, and most tools treat the three words as one idea. You do it for reach, since your viewers on YouTube, Twitch and Facebook all see the same show while you run one production instead of three.

AIOZ Stream calls this feature multicast, which is not IP multicast, the network technique that sends packets to a group address. Here it means one RTMP stream in and several RTMP streams out, the definition you will also find in our video streaming glossary entry for multicast. A relay that forwards the feed without re-encoding it is doing what the glossary calls RTMP pass-through.

How do you stream to multiple platforms at once?

There are three common setups, and they differ in who makes the extra copies (for the whole pipeline around them, see how live streaming works from encoder to viewer).

  • Encoder multi-output. Your encoder opens a separate connection to each platform. In OBS Studio you add this with a plugin such as obs-multi-rtmp, and every extra output uses more of your upload bandwidth.
  • Cloud relay. You send one stream to a service, and its servers send a copy to every destination you configured. Your upload stays the same however many platforms you add.
  • Self-hosted relay. You run your own server, for example nginx with the RTMP module and one push line per platform. It costs little, but you now operate a server that every broadcast depends on.

A platform-side relay such as AIOZ Stream multicast is the cloud model built into the service you already stream to. The platform receives your RTMP feed, plays it to its own viewers over HLS, and forwards copies to the URLs you listed.

Diagram comparing two ways to restream one broadcast to YouTube, Twitch and Facebook: with encoder multi-output, OBS Studio sends three 6,160 Kbps streams for 18,480 Kbps of upload; with AIOZ Stream multicast, OBS sends one 6,160 Kbps RTMP stream to AIOZ Stream, which plays it over HLS and forwards it to the destination URLs in the stream key's multicast_urls list
Encoder multi-output vs a platform-side relay, using the top bitrates from the AIOZ Stream OBS guide.

How much upload bandwidth do you need to multistream?

Multiply your total bitrate by the number of streams your own connection sends. AIOZ Stream's OBS guide gives a 1080p30 starting profile of 4,500 to 6,000 Kbps of video, plus 128 to 160 Kbps of AAC audio. At the top of both ranges, one stream is 6,160 Kbps.

  • Encoder multi-output to three platforms: 3 x 6,160 = 18,480 Kbps, or about 18.5 Mbps of steady upload.
  • One stream to a relay with three destinations: 6,160 Kbps, or about 6.2 Mbps, whatever the destination count.

These figures cover the media bitrate only, so leave headroom for protocol overhead and dips in your connection, and expect more CPU or GPU load when each output gets its own encode. To choose the bitrate itself, use our guide to OBS encoder settings for 1080p and 720p.

Simulcasting rules on Twitch, Facebook and YouTube

Each destination sets its own rules, and the relay can't change them, so read them before your first multistream.

  • Twitch allows simulcasting under its Simulcasting Guidelines unless you have an agreement that requires exclusivity. Its FAQ says that shrinking or degrading the Twitch video so it looks worse than elsewhere breaks the guidelines, and that you cannot use Twitch to push viewers toward a concurrent stream on another service.
  • Facebook requires RTMPS, the TLS-encrypted form of RTMP. Meta's Live Video API documentation says your app must produce an RTMPS stream to go live on Facebook.
  • YouTube takes an RTMP URL plus your stream key, and the AIOZ Stream docs use rtmp://a.rtmp.youtube.com/live2/ followed by a key as their example destination.

Sending the same resolution and bitrate everywhere is the simplest way to stay inside the Twitch rule, and a relay that forwards one unchanged feed does that by default. For how RTMP and RTMPS sit next to HLS, WebRTC and SRT, see our overview of video streaming protocols.

How AIOZ Stream handles it

We built multicast into AIOZ Stream's live workflow, and the docs say it sends "a single stream to multiple destinations, such as YouTube, Facebook, and Twitch, simultaneously" over RTMP. You need one encoder and one outgoing stream, and you can set destinations in two places.

  • Dashboard. When you create a streaming session, the optional Add Destination field takes external restreaming destinations. Sessions themselves are optional, as our guide to stream keys and streaming sessions explains, so create one before you go live if you want destinations set.
  • API. Three endpoints on /api/live_streams/multicast/:stream_key manage a multicast_urls array: POST adds or updates the list, GET reads it, and DELETE removes it. Each accepts a Bearer token or the stream-public-key and stream-secret-key headers.

This is the documented POST request, with line continuations added and placeholders in capitals:

curl --location --request POST 'https://api.aiozstream.network/api/live_streams/multicast/YOUR_STREAM_KEY' \
  --header 'stream-public-key: YOUR_PUBLIC_KEY' \
  --header 'stream-secret-key: YOUR_SECRET_KEY' \
  --header 'Content-Type: application/json' \
  --data-raw '{ "multicast_urls": [ "rtmp://a.rtmp.youtube.com/live2/YOUR_YOUTUBE_KEY" ] }'

The documented 200 response echoes the list back in live_stream_multicast_urls, together with the stream key and its key ID:

{
    "status": "success",
    "data": {
        "id": "7ce757f8-b67b-46e6-8d1a-84b7a670601b",
        "live_stream_key_id": "f728df2f-ada5-4f1f-bb5e-cb896feffa30",
        "stream_key": "0e34d9db-9893-4344-a727-336566cde5e6",
        "user_id": "54f4b3da-988a-4e5a-9e99-9300b8cf482b",
        "live_stream_multicast_urls": [
            "rtmp://a.rtmp.youtube.com/live2/abcd-abcd-abcd-abcd"
        ]
    }
}

We ran the GET call on October 29, 2026 with placeholder keys to show what a wrong key returns, and got HTTP 401 with this body:

{"status":"fail","message":"API key not found.","reason":"api-key-not-found","request_id":"01a18638-72c1-7674-99ec-17cdfd3575f2"}

If you work in Node.js, the official client wraps the same calls as addMulticast, getLiveStreamMulticastByStreamKey and deleteLiveStreamMulticast; we read these names in @aiozstream/nodejs-client 1.0.16. Once you are live, the statistics endpoint reports bitrate and FPS in and out, updated every 5-30 seconds, and our guide on monitoring livestream health shows how to read them. For every other live setting, see the complete AIOZ Stream live streaming guide.

What the docs don't cover yet:

  • How many destinations you can add: the dashboard guide only says "Up to limit destinations if supported by your product tier", and the API reference gives no number.
  • Whether POST replaces the whole list or appends to it, and whether DELETE can remove a single URL.
  • Whether rtmps:// destinations, which Facebook requires, are accepted.
  • Whether forwarding re-encodes the stream, how a failed destination is reported, and how forwarded traffic is billed.

To add your first destinations, open the AIOZ Stream Livestream Multicast reference.

Frequently Asked Questions

Can I restream to YouTube and Twitch at the same time?
Yes. Twitch allows simulcasting unless your agreement requires exclusivity, as long as the Twitch stream is not worse than the others, and on AIOZ Stream you add both RTMP URLs to the stream key's multicast list.

Does restreaming need more upload bandwidth?
Only when your encoder sends each copy itself. With a relay you upload one stream, about 6.2 Mbps at 1080p30 using the top values of the AIOZ Stream OBS guide, whatever the number of destinations.

Is restreaming the same as simulcasting?
In practice, yes. Twitch uses simulcasting and multistreaming for the same act of broadcasting one stream to several platforms at once.

Do I need a separate encoder for each platform?
No. The AIOZ Stream docs describe multicast as a way to reach a wider audience without multiple encoders or separate streams, so one OBS or PRISM Live Studio feed is enough.

How do I stop forwarding to my destinations on AIOZ Stream?
Send a DELETE request to /api/live_streams/multicast/:stream_key. The docs describe it as deleting the multicast URLs of the stream and list no request body.

References

We only send updates when meaningful changes ship, and you can unsubscribe anytime

Related Content

blog thumbnail

Restream to Multiple Platforms With AIOZ Stream Multicast

Restream to multiple platforms by sending one feed to a relay. Learn the bandwidth math, platform rules and how AIOZ Stream multicast forwards your RTMP stream.

aioz-stream
6 min readNovember 20, 2026
blog thumbnail

MPEG-TS vs fMP4 for HLS Segments and When to Use Each

MPEG-TS vs fMP4 for HLS: how 188-byte TS packets and fMP4 init segments differ, what each costs in overhead, which codecs need fMP4, and when TS still fits.

aioz-stream
7 min readNovember 17, 2026
blog thumbnail

Live Streaming vs VOD (Video on Demand) and When to Use Each

Live streaming vs VOD comes down to when your audience watches. Three questions help you pick live, on demand or both, with real costs and AIOZ Stream limits.

aioz-streamguide
6 min readNovember 13, 2026
blog thumbnail

How Does Live Streaming Work? From Encoder to Viewer

How does live streaming work? Video is captured, encoded, sent over RTMP, transcoded, cut into HLS segments and served to players. See each stage end to end.

aioz-streamguide
7 min readNovember 12, 2026
blog thumbnail

How Web Video Players Work: HTML5 Video, MSE and EME

How web video players work: the HTML5 video element plays media, MSE lets JavaScript feed it HLS and DASH segments, and EME unlocks DRM-protected streams.

aioz-streamguide
7 min readNovember 11, 2026
blog thumbnail

SRT vs VTT Subtitle Formats and When to Use Each One

SRT vs VTT explained: how the two subtitle formats differ in timestamps, headers and styling, which one browsers, HLS and YouTube expect, and how to convert.

aioz-stream
6 min readNovember 10, 2026