How to Multistream with Restream

Before you start

Restream routes one outgoing live feed to multiple destinations, but it does not create the source feed by itself. You still need a camera, capture card, screen capture tool, encoder, or streaming application that can send video to a server. The connection from your device goes to Restream, and Restream distributes that signal to the platforms you have connected. This means you need an account, a stable upload connection, and at least one destination channel that accepts external stream keys.

Check the upload bandwidth available for your stream rather than only the download speed shown by a general speed test. A conservative starting point is to leave headroom above your selected video bitrate so the connection can handle audio, network variation, and streaming overhead. For a typical camera setup, use a wired network connection when possible because it can reduce the wireless interference that causes frame drops.

The process is service-based, not fully local. Restream receives the encoded stream, so you must allow your encoder or camera to reach the Restream server. Corporate networks, VPNs, or restrictive firewalls can block that traffic even when normal browsing works. If a direct camera-to-server path is blocked, try a standard computer-based encoder on an unrestricted connection to confirm whether the limitation is in the camera or the network.

Step-by-step instructions

In your Restream dashboard, open the destination or channel settings and connect the platforms you want to receive the stream. Follow the sign-in prompts for each platform because Restream uses platform authorization to link the destination. If a platform is not listed as a direct connection, look for a custom RTMP destination option and use the stream key plus server address supplied by that platform.

Select the destination set

Choose the platform or group of platforms that should receive the next broadcast. Restream can let you create a default destination set so you do not have to toggle every channel before each session. Review the selected destinations before going live because a channel left enabled from a previous test can receive an unwanted stream.

Enter the server and stream key in your encoder

Open the stream settings in your camera app, hardware encoder, or software such as a broadcast tool or web-based encoder. Find the RTMP server field and stream key field, then copy the server URL and stream key shown by Restream. The stream key is treated like a password for that stream: paste it only into your encoder and do not share it or display it on screen.

If the encoder has separate fields for a URL and a key, place the full Restream server address in the URL field and the key in the key field. If the tool accepts only one combined value, enter the server address followed immediately by the stream key, using a slash separator only when that matches the format required by the tool. Do not add spaces unless the encoder documentation specifically expects them.

Set resolution, frame rate, and audio

Match the source feed to the video mode supported by your camera and encoder. A common practical starting point is 1920 by 1080 at 30 frames per second, but a lower resolution such as 1280 by 720 may be safer on a limited connection. Keep the frame rate stable rather than switching between 30 and 60 during a broadcast, because repeated changes can create visible timing problems.

Enable one active audio source and check the audio meter before going live. If the encoder lets you select separate microphone and system audio channels, choose only the channels the stream should carry. Silence or a missing audio device can still produce a usable silent stream, but a misrouted channel may send monitor audio, feedback, or unwanted system sounds.

Version differences affect where some settings appear. Older encoder versions may call the service a custom RTMP server, while newer versions may offer a built-in Restream destination. The underlying connection is the same: you must send one encoded stream to the Restream server and let the dashboard control the destinations.

Start the stream

Begin the broadcast from the encoder or camera and keep the Restream dashboard open in a separate window or device. Starting in Restream alone does not start the camera feed, and starting the camera does not automatically make every destination live unless Restream receives the signal. Because the change is reversible, it is usually safer to start the feed, check the Restream input preview, and only then treat the broadcast as public.

Check the output

Open the Restream dashboard and confirm that the incoming bitrate, resolution, frame rate, and audio level match the values you set in the encoder. The input status should show a connected or live state before you rely on the destination platforms. A dashboard that shows an offline destination may still have a good incoming feed, so check the input first and then each destination separately.

For each platform, open the stream manager or live preview in that platform and confirm that the video and audio are playing. The arrival time can differ slightly between destinations because each platform receives a separate distribution path from Restream. Some destinations may take longer to show the live preview or may require you to publish or schedule the stream through the platform's own control panel.

Watch for practical format limitations. Restream can distribute a source feed, but it cannot guarantee that every destination accepts the same encoder settings. A platform may transcode the feed, reduce the resolution, or reject an unsupported frame rate or codec. If one destination shows video problems while another looks correct on the same input, treat it as a destination-specific incompatibility rather than a general camera failure.

Common problems and next steps

If the dashboard does not receive the feed, recheck the server and stream key in the encoder. A single mistyped key or a copied blank space can prevent the connection. Remove the value and paste it again, making sure the encoder does not store an old key from another service. Then confirm that the encoder shows a resolving or connecting state and is not blocked by a firewall or VPN.

A feed that connects but breaks up usually indicates an upload limitation rather than a problem inside Restream. Reduce the video bitrate or resolution, close other upload-heavy applications, and test on a wired connection. If the camera and computer are both sending data through the same network, make sure the total upload demand is below the available capacity.

For a destination that does not appear or does not publish, open that platform's live settings and check whether the stream requires manual confirmation, a scheduled event, or an enabled live feature. Some platforms need the stream key applied inside their own creator settings before Restream can deliver the feed. When the issue is isolated to one platform, correct that platform's destination settings and leave the working source feed unchanged.

If the audio is present in the source preview but missing on a destination, check whether the platform is muted by default in a preview window. Platform settings can also apply their own audio processing, so compare the source meter with the destination monitor. When the source meter is silent, fix the microphone or audio routing in the encoder because that is the setting Restream will forward.