“Integrate Discord with Streamlabs” can mean three different things: posting a stream announcement in a Discord server, showing a Streamlabs scene in a Discord call, or deciding whether Discord voices are heard on your broadcast. These are separate workflows, so choose the result you need before changing settings.
The steps below cover Streamlabs Desktop where video and audio capture are involved. The announcement link is configured through Streamlabs’ dashboard or Streamlabels; it does not automatically share your scene or capture call audio. If you use the Streamlabs Plugin for OBS Studio, do not assume its interface has the same controls.
Choose what you want Discord and Streamlabs to do
Start with the direction of the media. An announcement sends information from Streamlabs to Discord. A virtual camera sends Streamlabs video into a Discord call. Audio capture sends sound from Discord into Streamlabs Desktop, which can then put it in the YouTube broadcast. You might want one of these, two of them, or none.
| What you want | Direction | Main control | What it does not do |
|---|---|---|---|
| Tell a server that you are live | Streamlabs to Discord | Discord integration and an announcement action | It does not send your scene into a call or route call audio |
| Show a composed scene in a call | Streamlabs Desktop to Discord | Streamlabs Desktop Virtual Camera | The virtual-camera path sends video, not desktop audio |
| Let viewers hear Discord voices | Discord to Streamlabs Desktop to YouTube | Application Audio Capture and output routing | Linking the Discord integration does not set this up |
| Share a basic app or screen | Your computer to Discord | Discord screen share | It does not provide the Streamlabs scene composition unless you share that output |
For a small business, an announcement may be enough to let regulars know a demonstration is under way. For a study music channel, you may want to show a prepared scene to a guest in a call, but keep conversation out of the public stream. A devotional channel with a live host may instead need selected voices in the broadcast. Decide whether the audience should receive video, audio, both or neither before routing anything.
If your goal is an always-on YouTube channel, Discord is usually a way to communicate with a community, not a requirement for the broadcast itself. Keep the broadcast setup and community workflow distinct. For background on planning the channel loop, see how to create a YouTube radio station or always-on channel. If you are testing scenes or schedules before making a permanent change, the playlist schedule testing guide may help with that separate task.
Link Discord for stream announcements
Streamlabs’ Discord Integration guide describes linking a Discord server from the Streamlabs dashboard. Open the integrations page, find Discord and choose Link. In the authorisation window, select the server you want to use and complete any verification prompt that appears. You need the appropriate authority in that server to authorise the integration; if the server is not offered, check that you are signed into the right Discord account and have permission to add the integration.
The guide was last updated in December 2021. The current dashboard may differ, and Discord may not be available on every account or interface. Confirm that Discord appears on your own Streamlabs integrations page before following older screenshots or looking for a control that has moved. The linked guide is a useful reference, not a guarantee that every account will see identical options.
This linking step authorises the connection; it is not the same as setting up an announcement. Streamlabs’ guide describes the bot as appearing offline except when it needs to post. That can look unexpected if you are used to bots that remain visibly online, but the status alone does not tell you whether your configuration is correct. Test the intended announcement in the channel you selected rather than relying on the bot’s presence indicator.
The documented process also requires you to be live and to click an Announce button manually. Do not plan around an automatic announcement trigger unless the current controls in your own account explicitly offer and document one. The guide says a post may take up to five minutes, so allow time before concluding that the announcement failed. That delay is a note from the guide, not a promise that every post will appear on that schedule.
Set the announcement message and channel
After linking, use the Streamlabs dashboard or the Live Actions tab in the Streamlabels application to set the message and the Discord channel where it should appear. The exact route depends on the interface available to you. Look for the announcement settings, choose a channel intended for live notifications, and write a short message that tells members what is happening and where to watch. Avoid putting routine stream notices in a channel where they would interrupt unrelated discussion.
Check the message before using it. Include the YouTube destination you want members to visit, and make sure the text still makes sense if a stream starts late or the subject changes. If your channel runs continuously, the point of an announcement may be a scheduled event, a new programme block or a guest appearance rather than the stream’s initial start. A manually clicked action is better suited to those deliberate moments than to a broadcast that restarts while nobody is at the computer.
Then go live and use the Announce action when you are ready. Check the selected Discord channel directly to confirm that the post appeared and that the destination is correct. If nothing arrives, verify that the account remains linked, the right server and channel are selected, and the stream is live. Allow for the delay described in Streamlabs’ guide before repeating the action, since duplicate posts can confuse members.
Treat this as a small publishing workflow: connect, compose, trigger, verify. If you need unattended notices every time a continuous stream reconnects, the documented manual action may not match that requirement. Do not infer an automatic trigger from the fact that the integration is linked; confirm the behaviour in the current product documentation and account interface first.
Show a Streamlabs scene in a Discord call
If you want people in a Discord call to see your Streamlabs scene, use Streamlabs Desktop’s Virtual Camera workflow. In Streamlabs Desktop, open settings, install and start Virtual Camera, then join or open your Discord call and choose Streamlabs Desktop Virtual Camera as the camera. The call should receive the video composition produced by Streamlabs Desktop, which can include the scene elements you have arranged there.
This is a video route. Streamlabs’ guide explicitly says that desktop audio is not delivered through the virtual camera. If the people in the call need to hear game sound, music or another desktop source, you will need a separate audio route; do not assume that selecting the camera includes it. Streamlabs describes an audio-routing programme such as VoiceMeeter Banana as one possible approach, but it is not the only conceivable routing arrangement and may not suit every computer or workflow. See the Streamlabs guide to streaming on Discord for the documented virtual-camera steps and audio limitation.
If you do not need Streamlabs scenes, overlays, alerts or webcam composition, Discord’s own screen-share control may be simpler. You can share a specific application instead of the whole desktop when you want to limit what call participants can see. Sharing an application is especially useful when the desktop may contain private notifications or other windows. It is a different method from sending the Streamlabs Virtual Camera, not an additional effect of linking the Discord integration.
Before using either route in a public or guest call, preview the result. Confirm that Discord is using the intended camera, that the right scene is visible, and that private windows are not exposed. If Streamlabs Desktop does not appear as a camera, check that Virtual Camera is installed and started, then review Discord’s camera selection and permissions. The precise labels can change between software versions, so use the current controls in each application rather than relying on an old screenshot.
Decide whether Discord voice chat enters the broadcast
A Discord call can be audible to you without being audible to your YouTube viewers. Streamlabs’ audio guidance frames the choice plainly: hear your friends or moderators in Discord without the stream hearing them. To achieve that, route Discord to an output device you can hear, such as your headset, that Streamlabs Desktop is not capturing. In Discord’s Voice & Video settings, select that output device.
If you want call participants to be part of the broadcast, add Discord as a selected source in Streamlabs Desktop. Streamlabs’ instructions describe adding Application Audio Capture and choosing the application to capture. Select Discord for that source. This lets you choose the call audio rather than sending all computer sound to the broadcast, but test the capture before relying on it. A call can include interruptions or private conversation, so agree with participants about what may be broadcast and when.
In Streamlabs Desktop, disable Desktop Audio in Settings > Audio when you do not want all computer audio captured in addition to your chosen application source. Leaving Desktop Audio enabled while also capturing Discord can make the same sound arrive by more than one route. That can create echoes or doubled audio. If you hear duplication, inspect the active sources and disable the broad desktop capture if selected application audio is meant to be the only route.
Alerts need separate attention. Streamlabs says to set alert sources to Monitor and Output if alerts should remain audible to viewers while using selected application audio. Check this after changing the capture approach: a clean Discord mix is not useful if an alert that should be public becomes inaudible. The audio-splitting guide from Streamlabs covers application capture, monitoring and selective recording in Streamlabs Desktop.
Check permissions and audio routing
Work through the setup in the order the signal travels. For an announcement, confirm server authorisation, the destination channel, the message and the manual action. For a scene in a call, confirm that Streamlabs Desktop Virtual Camera is running and selected in Discord. For voice, confirm which application Streamlabs captures, which output Discord uses, and whether Desktop Audio is also active. These checks are not interchangeable; a successful announcement tells you nothing about the camera or audio path.
Permissions matter on both sides. The account linking an announcement needs permission to authorise the Discord server connection and post in the selected channel. The Discord application needs permission to use the chosen camera and microphone where relevant. If you are sharing a scene but not sending microphone audio to the call, check that the call’s microphone state matches your intention. The scene itself may also contain alerts, browser content or overlays that you did not intend to show to call participants.
Make a short private test before a real session. Ask a trusted person in the call to confirm what they can see and hear, while you monitor Streamlabs’ audio meters and local playback. Test a spoken Discord voice, a desktop sound and an alert separately; this makes it easier to identify which source is responsible if something is missing or duplicated. Do not treat a meter moving as proof that the correct audience receives the signal: verify both the call and broadcast preview or recording path you intend to use.
For selective recordings, Streamlabs describes Selective Recording, which lets you choose for each source whether it is included in the stream, the recording, or both. This can be useful when you want a recording layout to differ from what viewers receive live. It does not replace checking audio routing, and the settings are specifically documented for Streamlabs Desktop. Keep a note of the source choices you changed so that you can restore them after a guest session.
Product boundaries are important here. Streamlabs’ guidance for Virtual Camera and Application Audio Capture concerns Streamlabs Desktop. Streamlabs separately documents a Plugin for OBS Studio; its guide describes Streamlabs overlays, alerts, widgets and related controls in the OBS interface, but that does not establish that Discord controls match Desktop’s. The Plugin for OBS guide is the right starting point if you use that product. For broader OBS continuity concerns, see how to keep an OBS YouTube stream running after a Windows restart, which addresses a separate problem rather than Discord integration.
If your actual requirement is to turn a prepared file into a YouTube live stream without keeping your own computer running, StreamNeo removes that specific need to leave a local streaming setup on overnight: you upload the video, provide your YouTube stream key, and the broadcast runs with your computer switched off. It is YouTube-only, and it does not replace the Discord announcement, call-camera or voice-routing steps described above.
When the right workflow is clear, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.
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
Does linking Discord make my Streamlabs scene appear in a call?
No. Linking Discord through the Streamlabs dashboard is for the announcement workflow described in Streamlabs’ integration guide. To show a Streamlabs Desktop scene in a call, start its Virtual Camera and select it in Discord, or use Discord screen share if you only need a basic screen or application view.
Will Discord call audio go through Streamlabs Virtual Camera?
No. The Virtual Camera path carries video, not desktop audio. If viewers or call participants need to hear a separate sound source, configure an audio route separately and test it; application audio capture and Discord’s output-device choice control whether call audio reaches the Streamlabs Desktop broadcast.
Can I hear Discord while keeping it out of the YouTube stream?
Yes, if Discord’s output is sent to a headset or speakers that Streamlabs Desktop is not capturing. Use the Discord Voice & Video output-device setting and check Streamlabs’ audio sources, particularly whether Desktop Audio is still enabled. Test with a private call so you can confirm the stream mix before broadcasting.
Are these steps the same in the Streamlabs Plugin for OBS Studio?
Do not assume so. The Virtual Camera and Application Audio Capture instructions above are for Streamlabs Desktop, while the Plugin for OBS is a separate product with its own interface. Check the current guide for the product you actually use.