If Streamlabs is not capturing desktop audio, start by checking whether the relevant mixer channel is muted, then confirm that Streamlabs is listening to the same playback device that Windows is using. On Mac, follow a different route: Streamlabs’ documented method uses a virtual audio device and macOS Audio MIDI Setup rather than the Windows mixer path.
The right fix depends on whether you need all computer sound, one application, or audio coming from a console and capture card. Make one change at a time, play known audio, and watch the meter so you can identify the point at which the signal returns.
Why Streamlabs may not capture desktop audio
Desktop audio is not a single universal input. It is a signal moving from an application, through an operating system output device, into Streamlabs’ selected source, and then through the scene and mixer. A failure at any point can leave the stream silent even though sound is audible through your headphones or speakers.
On Windows, the common branches are a muted Streamlabs channel, the wrong playback device, or another audio utility taking control of the device. Windows may also allow an application to use the output device in exclusive mode. That can interfere with the route Streamlabs is trying to monitor.
On macOS, the documented Streamlabs workflow is different. Streamlabs says that sound from other Mac applications needs to be routed through a virtual device such as BlackHole, with a Multi-Output Device created in Audio MIDI Setup. Applying Windows instructions to a Mac will not create that route.
First identify the sound you are trying to capture. Browser audio, a game, music, a video call, and a system notification may not all follow the same path. If you only need a game or browser window, application capture is usually a better target than capturing every sound made by the computer.
If the sound is coming from a PlayStation, Xbox, or another external source through a capture card, treat that as a separate problem. Capture-card audio has its own device, console output, monitoring, and mixer settings. It is not evidence that ordinary Windows desktop capture is broken.
For a long-running YouTube channel, this distinction matters. A local computer may appear to work while unattended playback later switches to a monitor, Bluetooth device, or virtual output. If your wider aim is to keep a channel running without leaving a desktop switched on, first understand the local audio path, then compare it with how to stream 24/7 on YouTube without a PC.
Check the mixer mute state on Windows
Begin with the least disruptive check. Open Streamlabs Desktop, play a video or other known audio source, and look at the mixer. Find the channel that represents desktop audio and confirm that it is not muted. A muted channel can make the setup look correctly configured while sending no signal to the stream or recording.
Watch the meter while the sound is playing. If the meter moves, Streamlabs is receiving at least some signal. The problem may then be monitoring, scene selection, output routing, or the destination rather than capture itself. If the meter stays still, continue with the device checks below.
Do not rely only on what you hear locally. You may be hearing audio directly from Windows while Streamlabs is listening to a different output. Conversely, Streamlabs may be receiving the audio while your monitoring settings prevent you from hearing it. The meter is useful because it separates capture from monitoring.
Check the channel again after changing mute state. Stop the test audio, start it again, and allow enough time for the meter to respond. This simple repeat avoids mistaking a silent browser tab or paused application for a Streamlabs fault.
If the channel is present but no signal appears, open Streamlabs’ audio settings and note which desktop device is selected. Avoid changing several sources at once. A clean baseline makes it easier to tell whether the next change fixed the route or merely changed what you were listening to.
Select the correct playback device
Windows can have several playback devices available at once: laptop speakers, a monitor over HDMI, wired headphones, a Bluetooth headset, a USB interface, or a virtual audio device. The output you can hear is not necessarily the output Streamlabs has selected.
In Windows Sound, identify the device marked as the current default output and play audio through it. Then, in Streamlabs, manually select that same named playback device rather than leaving the desktop device set to “default”. Streamlabs’ Windows troubleshooting guidance specifically points readers towards choosing the actual playback device.
The names must match the route you are testing. If Windows is sending sound to “Headphones” but Streamlabs is listening to “Speakers”, changing the volume of either device will not repair the connection. Select the output you are genuinely using, then return to the mixer and test again.
This check becomes important after connecting or disconnecting a monitor, docking station, Bluetooth headset, or USB audio device. Windows can change the active output, while Streamlabs keeps its previous selection. A device that worked yesterday may no longer be the device carrying today’s browser or game audio.
There is another Windows approach when global desktop capture remains unreliable. Disable the global desktop-audio device in Streamlabs and add an Audio Output Capture source to the scene. Choose the specific Windows playback device in that source. This makes the route visible at scene level instead of asking one global setting to follow every output change.
Use one approach at a time. Do not keep a global Desktop Audio source and an Audio Output Capture source pointed at the same device unless you have a reason to do so. Capturing the same output twice can create duplicate sound or an echo.
The same principle applies to a continuous broadcast. If you are looping existing videos, audio must remain attached to the intended output for the whole session, not merely during a short test. For planning the content side of that setup, see how to turn existing YouTube uploads into a 24/7 live channel.
| Windows setup | What to select | What to watch for |
|---|---|---|
| All computer sound | The actual Windows playback device in Streamlabs | The desktop mixer meter should move when any chosen application plays sound |
| One named output | Audio Output Capture set to the desired playback device | Disable duplicate global capture if both sources hear the same audio |
| One application | Application Audio Capture set to the intended window | Disable global Desktop Audio to avoid overlapping or echoed sound |
| Console through a capture card | The capture device and its audio channel | Console output and capture-card settings may be separate from desktop audio |
Check competing audio utilities and exclusive mode
Audio-management utilities can alter, redirect, or take control of the same device Streamlabs needs. Streamlabs’ Windows troubleshooting article names Nahimic 2, Sonic Studio Sound, Realtek HD Audio Manager, and Sound Blaster Recon as examples of software that may interfere. The article also advises checking Task Manager for similarly named processes.
Close those utilities temporarily, not because every installation causes a problem, but because they are a useful way to isolate the conflict. If desktop audio returns, reopen the tools one at a time and test after each change. That tells you which utility is involved instead of leaving unrelated software disabled indefinitely.
Look for other audio mixers, enhancement suites, virtual cable managers, headset control panels, and motherboard sound utilities. Their names vary by computer and manufacturer. The relevant question is whether another program is applying routing, effects, or device control between Windows and Streamlabs.
Next check exclusive mode for the selected Windows playback device. Open the device’s Properties, go to the Advanced tab, and clear “Give exclusive mode applications priority”. Streamlabs presents this as a troubleshooting step for the selected output device, not as a setting that every Windows user must change.
Test before and after changing it. If the setting makes no difference, you can restore the previous state. If it resolves the missing signal, leave a note of the device and setting so you can repeat the configuration after replacing headphones, moving to a different monitor, or reinstalling audio software.
Do not jump immediately to a virtual cable or a more complex mixer. Streamlabs lists Windows C++ Redistributables in its troubleshooting material and places Voicemeeter Banana and a virtual audio cable later in the process. Those are advanced software-routing options, not required hardware and not a universal cure.
A virtual route can add another place for the signal to disappear. Use it only when the ordinary playback device path and the competing-utility checks do not meet your needs. If you use one, document which application sends audio into it, which device Streamlabs captures, and where you monitor the result.
Use Audio Output Capture for a specific output
Audio Output Capture is useful when you know exactly which Windows playback device should reach the scene. It is particularly helpful on machines with several outputs, or when you do not want Streamlabs’ global desktop setting to follow a changing default device.
Add the source to the scene and select the desired output from the device list. Then play a known sound through that device. The source’s mixer channel should show activity. If it does not, return to Windows Sound and confirm that the application is actually using the same output.
Keep the source name descriptive. “USB headphones”, “HDMI monitor”, or “studio interface” is more useful than several sources all called “Audio Output Capture”. Clear names make a long-running scene easier to inspect when something changes overnight.
If the goal is one application rather than all desktop sound, use Application Audio Capture where it is available. Streamlabs’ Advanced Audio Control Setups describes selecting a particular window. If the source is not available, Streamlabs says updating Streamlabs Desktop may be needed.
Application capture and global desktop capture are different jobs. For example, you may want a game in the stream but not private notification sounds, a messaging application, or a browser tab playing elsewhere. Select the game window, then disable the global Desktop Audio source so both routes do not capture the same sound.
Listen for an echo as well as watching the meter. An echo often means that the selected application is being captured once through Application Audio Capture and again through global desktop audio. Remove or disable the duplicate source before changing more advanced monitoring settings.
Alerts may need their own decision. If an alert should appear in the broadcast, configure its audio output and monitoring deliberately. If it should remain local, route it to speakers or another output that is not being captured. Test an alert separately from the main desktop signal.
This distinction is also useful when you are building an ambience, devotional, or radio-style channel. You may want the programme audio in the broadcast but not every sound made by the control computer. If your source is a collection of recorded files rather than a live desktop session, streaming podcast MP3 files to YouTube Live using FFmpeg covers a different, more deliberate source path.
Follow the separate Mac troubleshooting path
Mac audio should not be treated as a Windows mixer problem. Streamlabs’ guide for capturing desktop audio on Mac explains a route using BlackHole, a virtual audio device, and a Multi-Output Device created in macOS Audio MIDI Setup.
Install and configure the virtual device according to the project’s current instructions, then open Audio MIDI Setup. Create a Multi-Output Device containing BlackHole and Built-in Output, or the output device you use for monitoring. Keep Built-in Output above BlackHole in the device order if you want to continue hearing the sound through the Mac’s speakers or headphones.
Set that Multi-Output Device as the Mac’s sound output. Applications should then send their audio through the combined route. In Streamlabs Desktop, open Settings, go to Audio, and select BlackHole among the Mic/Auxiliary devices. The exact labels can change with macOS and Streamlabs updates, so compare the screen you see with the current Streamlabs Mac audio guide.
Play a known sound and watch the relevant Streamlabs mixer channel. If the meter does not move, check the Mac’s current output again and confirm that the application is not using a different app-specific output. Then check that BlackHole is selected in Streamlabs rather than a microphone or physical speaker device.
The Multi-Output Device controls what you hear locally as well as what is routed into Streamlabs. If Built-in Output is omitted, you may send sound into the virtual route without hearing it yourself. If the order or selected devices are wrong, the stream can be silent, local monitoring can be silent, or both can behave differently from what you expect.
Alerts and system sound effects may need separate handling. Streamlabs’ Mac guidance recommends keeping sounds that should not enter the broadcast routed to Built-in Output or speakers alone. Decide whether each alert belongs in the stream before adding extra routes.
For BlackHole installation questions or application-specific behaviour, use the project’s current FAQ or wiki linked from Streamlabs’ guide. Interface details can change with macOS releases. Do not assume that a Mac fix involving Windows playback Properties, exclusive mode, or a Windows audio utility applies here.
If the Mac audio is present but cuts out or becomes choppy, record the Streamlabs Desktop version and macOS version before troubleshooting further. A version-specific issue can require a different response from a completely missing signal. Keep the test limited to one source so that a monitoring problem is not mistaken for a capture problem.
Test the scene after each change
A reliable test is short, repeatable, and separate from your live broadcast. Use an audio source you know is playing, such as a browser video or local media file, and note the device through which it is being heard. Start with the mixer visible in Streamlabs.
After every change, check three things:
- Does the expected Streamlabs mixer meter move?
- Can you hear the audio locally if you intend to monitor it?
- Does a short recording or private test broadcast contain the audio without a duplicate or echo?
The first check confirms capture. The second checks local monitoring. The third checks the final output, where scene, track, monitoring, and recording choices can introduce a separate issue. Passing one does not automatically prove that the others are correct.
Save the scene only after the route works. Give each source a clear name and write down the selected output device. If you use a Multi-Output Device on Mac or a virtual route on Windows, record its component devices as well.
For a 24/7 channel, test the transitions that will occur while you are away. Change a browser tab, restart the application that provides the audio, reconnect the headphones if that is part of normal use, and confirm that the intended source remains selected. A setup that survives these checks is easier to operate than one that depends on a particular window being open.
If the machine is only a temporary production tool, moving the workload away from the desktop may be simpler than maintaining several audio routes. StreamNeo removes the need to keep a computer running for an uploaded-file YouTube stream: upload the video once, add the YouTube stream key, and the broadcast can continue with monitoring and automatic restart handled while your computer is off. It is useful when the problem is not just missing audio, but the need to leave a desktop running through the night.
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
Why can’t I capture desktop audio in Streamlabs on Windows?
Start with the Streamlabs mixer mute state and then check that Streamlabs has the same playback device that Windows is using. If the meter remains still, close competing audio utilities and test the selected device with exclusive mode disabled. Make one change at a time so you can identify the cause.
Does the Windows desktop-audio fix work on Mac?
No single Windows fix should be treated as universal on Mac. Streamlabs’ documented Mac method uses BlackHole, a Multi-Output Device in Audio MIDI Setup, and BlackHole selected in Streamlabs’ Mic/Auxiliary inputs.
How do I capture only a game or browser window?
Use Application Audio Capture and select the intended window where the source is available. Disable global Desktop Audio if it would capture the same sound as well, because the duplicate routes can produce echoes.
Is a capture card needed to fix missing computer desktop audio?
No. A capture card is relevant when audio comes from an external console or another device routed through the card. Ordinary Windows or Mac desktop audio should be diagnosed through its operating-system output and Streamlabs source instead.