Streamlabs Desktop encodes your video and sends one broadcast feed to Restream. Restream then forwards that feed to the destination channels you select, so you configure the production in Streamlabs and the distribution in Restream.
The connection uses an RTMP URL and stream key. Create or open an encoder stream in Restream, copy those details into Streamlabs Desktop, start the broadcast there, and use Restream's dashboard to check whether the feed is arriving.
Understand what each application does
It helps to treat the two applications as separate parts of the same route.
Streamlabs Desktop is the encoder. It captures your scene, combines video sources and audio, compresses the result, and sends the encoded feed over the internet. Your scene might contain a devotional video, a camera, an audio visualiser, a study timer, or a simple still image with music.
Restream is the distribution layer in this workflow. It receives the feed from Streamlabs, then passes it to the destination channels that you have enabled in the Restream dashboard. You do not normally enter every destination's connection details into Streamlabs when using this arrangement.
That division matters when something goes wrong. A missing camera source is a Streamlabs production problem. A feed that reaches Restream but does not appear on one selected channel needs checking in Restream and, where relevant, on that destination's own live dashboard. A failed connection before Restream sees anything usually points to the URL, key, network connection, or encoder configuration.
For an always-on channel, this also affects your operating choice. A computer running Streamlabs must remain awake, connected, and able to maintain the broadcast. If you want to upload a prepared file once and avoid leaving your computer on overnight, a cloud workflow such as StreamNeo removes that particular local-computer task, but it is a different workflow from using Streamlabs Desktop and Restream together.
Before adding distribution, make sure the source itself is suitable for a long broadcast. If your channel uses several clips, the guide to scheduling different videos in an FFmpeg YouTube stream covers a different production method, but the same principle applies here: confirm what should play when the first item ends.
Create an encoder stream in Restream
Start in Restream rather than Streamlabs. Sign in to Restream, open the home screen, and choose New Stream, followed by Encoder | RTMP. If you have already created an RTMP stream, open that existing stream instead of creating another one.
The exact wording can change as the dashboard develops, but the important choice is the encoder or RTMP route. You are telling Restream that an external software encoder will send the broadcast. Restream's guide to going live with streaming software describes this general workflow and names Streamlabs among the software that can connect through it.
Once the stream is open, look for the setup area containing the connection information. Do not copy anything until you are sure you are looking at the RTMP stream you intend to use. Creating several similar streams can make it easy to paste the key for one stream into the wrong Streamlabs profile.
Give the stream a recognisable name if Restream offers that field. For example, use a name that identifies the programme and its purpose rather than a vague label such as “Live 1”. This is useful when you have a daytime news loop, a night-time ambience stream, and a separate test feed.
You can also prepare the stream's title, description, and thumbnail where Restream provides those controls. Treat these as publishing details rather than encoder settings. The video resolution, bitrate, audio mix, and scene layout still come from Streamlabs Desktop.
Keep the Restream browser tab open while you configure Streamlabs. You will need to return to it after starting the feed, and keeping the two windows available reduces the chance of copying an old key or losing track of which stream you are testing.
Choose the broadcast destinations
Destination selection happens in Restream. Turn on the channels that should receive this particular broadcast, and leave unrelated channels disabled. If you are testing a new devotional loop, for example, do not enable every channel in the account simply because they are available in the dashboard.
Check the title, description, thumbnail, and visibility settings for each selected destination. Restream's encoder documentation describes per-channel publishing controls, so one channel may need different wording from another. A local news loop may need a current programme description, while an ambience stream may use a more stable description.
The selected destinations affect both the publishing result and the plan requirements. As listed on Restream's site in February 2026, its free-plan guidance described multistreaming to two channels and use with third-party software, while three or more channels, Facebook Pages and Groups, and custom RTMP destinations required a paid plan. Verify the current account terms in Restream before publishing because these features can change.
That limit belongs to Restream. It is not changed by the fact that Streamlabs Desktop is installed on your computer, and a Streamlabs plan does not automatically unlock Restream features. Streamlabs also has a separate multistream product. Its official multistream page describes a different workflow with its own feature and plan distinctions, so decide which application is managing distribution before you configure the broadcast.
A simple comparison helps prevent the wrong setup:
| Question | Restream with Streamlabs Desktop | Streamlabs' own multistream workflow |
|---|---|---|
| Where do you select destinations? | In the Restream dashboard | In the Streamlabs product workflow |
| What sends the encoded feed? | Streamlabs Desktop | Streamlabs Desktop and the relevant Streamlabs service |
| What connection details are used here? | Restream's RTMP URL and stream key | The connection method shown by Streamlabs |
| What determines destination access? | Restream's current account and destination terms | Streamlabs' current product and plan terms |
| Where do you monitor the relay? | Restream's stream view and destination status | The applicable Streamlabs controls and destination dashboards |
The table describes the division of labour, not a promise that either route will deliver every broadcast. If a destination is important to your channel, check its current requirements separately before scheduling an overnight stream.
Copy the RTMP URL and stream key
In the Restream encoder setup, copy the RTMP URL and the stream key. Some interfaces show these in separate fields; others present the connection details together. You need both when using a custom RTMP connection.
The URL tells Streamlabs where to send the encoded feed. The key identifies the Restream stream and authorises the connection. Treat the key like a password. Do not publish it in a screenshot, paste it into a public support forum, or include it in a screen recording.
If you suspect the key has been exposed, use the account controls provided by Restream to replace or regenerate it if that option is available. Then update Streamlabs with the new value before starting the next broadcast. A key copied from an old stream may connect to a different Restream entry or fail to connect at all.
Copy carefully rather than typing the values by hand. Avoid adding spaces at the beginning or end of the key. If you use a password manager or notes application as an intermediate step, delete any temporary copy after setup, especially on a shared computer.
The RTMP URL and key are not the same thing as a destination's public stream URL. The RTMP details are for the encoder-to-Restream connection. Viewers use the destination's normal viewing page, and you check the relay through the Restream dashboard and the destination's own controls.
Restream's Streamlabs connection guide documents the service-selection route as well as the general connection process. Keep the guide open if the labels in your account do not match the labels in older screenshots.
Configure Streamlabs Desktop
Open Streamlabs Desktop and select the gear icon to open Settings. Go to Stream. The exact layout can vary by application version, but the relevant area is the stream service or custom ingest configuration.
If Restream appears as a named service, select the option for Restream or Restream.io. Streamlabs' support article for Restream and Streamlabs Desktop documents a route through custom ingest and Streaming Services, while Restream's own instructions describe choosing Streaming Services → Restream.io. The labels may not be identical in every version.
Enter the Restream stream key in the key field. If the named Restream service handles the URL automatically, you may only see a field for the key. Save the change with Done or the equivalent confirmation button.
If Restream is not listed, choose the custom RTMP or custom destination option. Enter the RTMP URL copied from Restream in the server or URL field, and enter the Restream key in the stream key field. This is not a workaround that bypasses Restream; it is the general RTMP connection route that Restream documents for software encoders.
Do not paste a YouTube stream key into this setup when Restream is meant to receive the feed. The receiving service in this workflow is Restream, so the key must belong to the Restream encoder stream. Restream then handles the onward connection to the destinations you selected.
After saving, review the fields once more before starting. A common mistake is putting the URL into the key field, leaving out part of the key, or selecting a saved service profile that points somewhere else. If you manage multiple channels, compare the stream name in Restream with the profile or scene collection you are about to use in Streamlabs.
The YouTube stream health checklist is useful for the destination side of the process, but do not use a healthy YouTube page as proof that the Streamlabs-to-Restream connection is correctly configured. Check each stage in order.
Use sensible encoder settings
Restream's Streamlabs guide, dated April 2025, recommends Advanced output mode, Software (x264) as the encoder, CBR rate control, a 2-second keyframe interval, and the Main profile. These are Restream's recommendations in that dated guide, not universal settings for every resolution, computer, graphics card, or destination.
Open Settings → Output in Streamlabs and compare the available options with the requirements of your selected destinations. If you use hardware encoding because your computer struggles with software encoding, check whether the resulting profile and rate settings meet the destination guidance before relying on it for a long broadcast.
The destination platforms' own specifications still matter. Restream's guide says the remaining settings should follow those guidelines, so do not treat one preset as a guarantee of acceptance or delivery. The guide to compressing video without visible quality loss can help when the source file or scene is demanding, but compression choices always involve a quality and computer-load trade-off.
For a prepared 24/7 visual, keep the scene uncomplicated while testing. Disable unused browser sources, camera inputs, and animated overlays. Every active source can add processing work or introduce a failure point. You can add production elements after the basic feed has remained stable through a test.
Audio deserves a separate check. Confirm that the intended source is moving on the mixer, that it is not muted, and that background music is not being doubled by two active sources. A video that looks correct in Restream but reaches viewers without usable audio is still an unsuccessful broadcast for most channel types.
Start the broadcast and check the connection
When the scene, audio, RTMP details, and Restream destinations are ready, click Go Live or Start Streaming in Streamlabs Desktop. Streamlabs should begin sending the encoder feed to Restream.
Return to Restream and open View Stream. Restream's connection guidance says this view can be used to monitor the incoming feed, destination channels, and viewer counts. Allow the dashboard time to update rather than repeatedly stopping and starting the broadcast after only a brief delay.
Check the stages in this order:
- Streamlabs: Is the application showing that it is streaming, and is the local preview changing as expected?
- Restream: Does the encoder stream show an incoming feed rather than a waiting or disconnected state?
- Destinations: Are the selected channels receiving the broadcast, and do their own live controls show the expected title and preview?
- Content: Is the picture moving, is the audio present, and does the stream begin at the intended point?
If Streamlabs says it is live but Restream shows no incoming feed, stop and recheck the RTMP URL, stream key, selected service, and local network connection. If Restream sees the feed but one destination does not, inspect that destination's status and the destination selection in Restream rather than changing the Streamlabs scene first.
If the broadcast disconnects, avoid assuming that restarting Streamlabs has fixed the cause. Note which stage failed, check whether the computer remained awake, and look for changes in the local network or a resource-heavy source. For overnight use, disable automatic sleep and confirm that the computer will not restart for an update without warning.
Restream forwards the feed, but it does not make the source content compliant or guarantee delivery to every selected channel. Review the current rules of each destination, and make sure you have the necessary rights for the video, music, images, and recordings in the broadcast. For music-led channels, the article on why YouTube mutes parts of a radio station livestream explains why a technically correct connection can still result in audio being restricted.
Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
FAQ
How do I connect Restream to Streamlabs Desktop?
Create or open an Encoder | RTMP stream in Restream, select the destinations, and copy the RTMP URL and stream key. In Streamlabs Desktop, open Settings → Stream, select Restream if it is available, or use the custom RTMP fields, then enter the Restream connection details.
What if Restream is not listed in Streamlabs Desktop?
Use Streamlabs' custom RTMP or custom destination option. Enter the RTMP URL from Restream as the server or URL and paste the Restream stream key into the key field. Menu names can differ between application versions, but the underlying RTMP connection is the same.
Can I use Restream on its free plan?
As listed on Restream's site in February 2026, its free-plan guidance included multistreaming to two channels and use with third-party software, while three or more channels and certain destination types required a paid plan. Check the current Restream account terms before publishing because plan features and destination rules can change.
Do I need a microphone or webcam?
No. A microphone or webcam is not required for the Restream-to-Streamlabs connection itself. You only need those sources if they are part of the programme you want Streamlabs Desktop to encode.