STREAMING GUIDE / STREAM TOOLS

Streamlabs Desktop has no audio: find where the sound stops

Use one sound and one microphone to separate a missing input from a silent recording or live output. This walkthrough covers Streamlabs Desktop on Windows.

START HERE

First check whether the missing source moves a Streamlabs mixer meter. No meter activity points toward device selection or capture. A moving meter with a silent saved file points toward mute, output level, or track assignments. Test those two cases separately before reinstalling anything.

1. Make the failure reproducible

Close your stream preview and pause alerts. Put on headphones, play a short familiar sound in one application, and make a 20-second local recording containing that sound and a spoken sentence. Listen to the saved file rather than judging only what reaches your headphones.

Write down what is missing: microphone, game, browser, or everything. Also note whether it is absent from the mixer, recording, or live player. If the game itself is silent outside Streamlabs, fix its output first with the one-app audio checklist. A streaming application cannot capture audio that never reaches the route you selected.

2. Match the capture device to the actual playback device

  1. In Windows sound settings, identify the output that is playing the test sound. A headset, monitor, USB receiver, and virtual cable are different endpoints even when they connect to the same desk.
  2. In Streamlabs Desktop audio settings, choose that device explicitly for desktop capture. Temporarily avoid a default-device alias while diagnosing a device change.
  3. Play the same sample. If the desktop meter now moves, repeat the recording before changing anything else.
  4. If using a scene-level Audio Output Capture source instead, select that same endpoint and disable the equivalent global capture. Capturing both can create a second copy.

These device choices follow Streamlabs' desktop-capture guidance. An application assigned to a different output in the Windows volume mixer will not automatically follow the endpoint you chose here.

3. Diagnose the microphone separately

Speak with the game paused. If the microphone meter stays still, check its physical mute switch and Windows input selection, then select that input explicitly in Streamlabs. Use the browser microphone test as a separate capture comparison. Close that test when finished.

If a raw recording works but Streamlabs loses quiet words, temporarily bypass its microphone filters one at a time. Save the original settings first. A gate that closes between words is a different fault from a device that cannot be opened. Restore each change that does not improve the same spoken sample.

4. If meters move, inspect the output mix

Check the source's mute state and fader. Then compare the track selected for streaming or recording in Output settings with the source assignments in the advanced mixer. At least one recorded track must actually contain your test source. Streamlabs documents these as separate selections.

For a diagnostic file, make one deliberately complete mix containing microphone and desktop sound. When that works, restore your isolated editing tracks. A media player may play only one audio track from a file; silence on that track does not establish that every recorded track is empty. Open the file in an editor or switch its playback track before declaring the recording lost.

5. Narrow down persistent capture failures

If the correct endpoint remains silent only in Streamlabs, quit competing audio-processing applications normally and test again. Change one item per recording. Avoid adding a virtual mixer just to hide an unexplained failure: it creates another route to maintain.

If the fault began after connecting a monitor or changing a USB port, reselect the endpoint and restart the affected application. Test a clean scene with a single capture source before altering the production layout. These Windows endpoint steps do not describe macOS system capture; use Streamlabs' platform-specific documentation for that setup.

Confirm the fix before going live

Record game sound, normal speech, a mute interval, and a scene transition. Confirm the saved mix contains exactly the intended sounds and stays silent during the mute interval. Then test the live destination separately while keeping its playback out of the captured desktop mix.

If only the live destination is silent, preserve the working local configuration and investigate the streaming-track assignment and service settings. For support, provide Streamlabs version, OS version, device names, the failing stage, and a short description of your test; remove stream keys and account details from screenshots.

Sources & version notes

Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.