OBS desktop audio problems become much easier to diagnose when you watch the Audio Mixer while sound is playing.
Play a YouTube video, game, or local audio file, then look at the Desktop Audio meter in OBS.
What the meter does tells you where the problem is:
- Meter does not move: OBS is not receiving the desktop sound.
- Meter moves but the recording is silent: OBS is receiving audio, but the recording track or playback of that track is wrong.
- Recording contains audio but you cannot hear it yourself: capture works; the problem is monitoring or your listening device.
- Most desktop sound works but one app or game is missing: investigate that application’s output or use per-application capture.
Do not reinstall OBS until you know which of those failures you have.
Desktop Audio Meter Does Not Move
Start with the output device OBS is actually capturing.
Open:
OBS > Settings > Audio > Global Audio Devices
Look at Desktop Audio.
If it is Disabled, choose the Windows playback device that is currently producing sound, such as your speakers, headphones, USB headset, HDMI display, or audio interface.
OBS’s own Quick Start documentation recommends manually selecting the audio device when the Audio Mixer meters are not moving.
For troubleshooting, I prefer selecting the exact device instead of Default. It removes uncertainty when Windows changes outputs after you connect a headset, monitor, dock, or Bluetooth device.
Play sound again and watch the meter.
Windows and OBS must be looking at the same output
Open:
Windows Settings > System > Sound
Under Output, identify the device currently playing your desktop sound.
Now compare it with:
OBS > Settings > Audio > Desktop Audio
For example, this will fail:
Windows: USB Headset
OBS: Realtek Speakers
You can hear the game because Windows is sending it to the headset, while OBS is listening to the speakers.
Select the same endpoint and test again.
Desktop Audio Is Missing From the Mixer
When there is no Desktop Audio entry in the Audio Mixer, check whether the global source is disabled under:
Settings > Audio > Global Audio Devices
You can also capture a particular playback device directly in the scene.
Under Sources:
- Click +.
- Choose Audio Output Capture.
- Create a new source.
- Select the required output device.
- Click OK.
OBS documents Audio Output Capture as a scene-level way to capture a specific output device.
Use either the global Desktop Audio path or the dedicated Audio Output Capture source for that device during your test.
Capturing the same device through both paths can duplicate the sound and create echo or phasing.
Windows Plays Sound but OBS Still Shows a Dead Meter
Now check whether the application itself is using a different Windows output.
Open:
Settings > System > Sound > Volume mixer
Find the game, browser, music player, or other application producing the sound.
Check that:
- the application is not muted;
- its volume is high enough;
- its output device matches the device OBS is capturing.
This is especially important with gaming headsets that expose separate Game, Chat, or Media endpoints.
A game can use one endpoint while OBS listens to another.
After changing an application’s output, restart that application if necessary and watch the OBS meter again.
Only One Game or App Is Missing From OBS
Do not rebuild the entire Desktop Audio setup when everything except one program is captured.
OBS supports per-application audio capture on supported Windows systems.
One option is:
Sources > + > Application Audio Capture
Choose the application whose sound you want.
OBS also supports including audio with compatible Window Capture or Game Capture sources in newer versions.
This approach is useful when you want to capture a game without capturing notifications, browser audio, music, or other Windows sounds.
When you use Application Audio Capture, avoid simultaneously capturing the same application through global Desktop Audio unless you intentionally need both. OBS warns that duplicate capture paths can cause echo.
Some applications do not cooperate cleanly with application-specific capture. If one app remains silent, compare it with normal Desktop Audio or an Audio Output Capture source before assuming OBS audio is broken.
Meter Moves but the Recording Is Silent
This is a different problem.
OBS has already captured the audio far enough for the meter to react. Stop changing Windows playback devices and inspect the recording tracks.
In the Audio Mixer:
- Open the menu beside Desktop Audio.
- Choose Advanced Audio Properties.
- Find Desktop Audio.
- Check which tracks are selected.
Then open:
Settings > Output > Recording
When using Advanced Output Mode, verify that the recording is configured to save at least one of the same tracks.
For example:
Desktop Audio: Track 2
Recording: Track 1 only
The meter will move, but that desktop source will not be written to the enabled recording track.
For a straightforward recording where you do not need isolated tracks, putting the normal sources on Track 1 makes testing simpler.
Make a short recording and play it back before starting a long session.
The Recording May Already Contain the Audio
Multi-track recordings can look silent in a basic media player even when the desktop sound is present on another track.
For example:
- Track 1: microphone
- Track 2: desktop/game
- Track 3: Discord
A player that automatically plays Track 1 can make the recording appear to have no desktop sound.
Import the file into an editor that supports multiple audio tracks or temporarily create a test recording with all required sources included on Track 1.
Do not delete an important recording until you have checked whether the missing sound exists on another track.
OBS Records the Audio but You Cannot Hear It
When the finished recording contains the desktop sound, capture is working.
The issue is monitoring or normal Windows playback.
OBS audio monitoring and OBS recording are separate concepts. A source can be recorded without being played back to your headphones through OBS.
Open:
Audio Mixer > Advanced Audio Properties
Look at Audio Monitoring.
Options can include:
- Monitor Off
- Monitor Only
- Monitor and Output
Do not automatically set ordinary Desktop Audio to Monitor and Output. You are usually already hearing that desktop sound directly through Windows, and sending it back through OBS can produce echo.
Monitoring is more useful for sources such as capture cards, remote audio, or specialized routing setups.
If you specifically need monitoring, also confirm that OBS is using the intended monitoring device.
Desktop Audio Stopped After Connecting Headphones or a Monitor
This usually deserves a device check before a driver reinstall.
Windows can change its playback endpoint when you connect:
- USB headphones;
- Bluetooth audio;
- an HDMI or DisplayPort monitor;
- a dock;
- an audio interface.
OBS may remain attached to the previous device.
Close OBS, select the intended output under Windows Settings > System > Sound, verify that Windows can play through it, then reopen OBS.
Return to Settings > Audio and reselect the correct Desktop Audio device if necessary.
This is particularly important when an HDMI monitor becomes the default Windows audio device even though you still expect OBS to capture your speakers or headset.
Windows Itself Has No Sound
At this point OBS is downstream of the real failure.
Open:
Settings > System > Sound
Select the correct output and test ordinary Windows audio.
If Windows cannot play through the device, fix that first.
Check the physical connection, Bluetooth state, Windows volume, output selection, and Device Manager.
Driver troubleshooting makes sense when the playback device has disappeared or Windows audio itself is broken.
For a Realtek-specific Windows problem, see Realtek Audio Console Not Opening rather than treating it as an OBS configuration failure.
Avoid third-party driver updater utilities. For a branded laptop or desktop, the manufacturer’s audio package may include device-specific components that a generic driver does not.
Audio Is Distorted, Unstable, or Drops Out
A sample-rate mismatch is more relevant to distorted or unstable audio than to a completely dead Desktop Audio meter.
Check:
OBS > Settings > Audio > Sample Rate
Then inspect the Windows playback device under:
Settings > System > Sound > More sound settings > Playback device > Properties > Advanced
Where practical, keep the relevant Windows and OBS rates consistent.
Change one variable at a time and restart OBS before judging the result.
Do not randomly change sample rate, exclusive mode, channel layout, drivers, and monitoring simultaneously. That makes it difficult to identify what actually fixed or broke the audio.
Desktop Audio Echoes or Sounds Doubled
This is almost the opposite of missing audio: OBS may be receiving the same sound more than once.
Look for overlapping capture paths such as:
- global Desktop Audio;
- Audio Output Capture for the same device;
- Application Audio Capture for the same program;
- audio included with Game/Window Capture;
- Monitor and Output feeding sound back into another captured path;
- a virtual audio cable looping audio back into OBS.
Simplify the scene so each sound is captured once.
OBS specifically warns about duplicate global and source-level audio capture because it can produce echo.
One Elevated Game Is the Exception
When ordinary desktop sound works but an administrator-level game or program behaves differently, compare its privileges with OBS.
As a troubleshooting test, close OBS and run it as administrator, then test the affected application again.
This is not a general desktop-audio fix. Administrator privileges will not repair a wrong playback device or incorrect recording track.
Use the test only when the failure is isolated to an elevated application.
A Clean Test Scene Can Expose a Complicated OBS Setup
Long-running OBS configurations can accumulate old audio sources, duplicated devices, track routing, filters, and monitoring choices.
Instead of immediately reinstalling OBS, create a temporary scene called something like Audio Test.
Add only the video source you need and one desktop-audio capture method.
Make a short recording.
If that works, OBS and Windows can capture desktop audio. Return to the production scene and look for duplicated sources, muted audio, track assignments, filters, or monitoring settings.
This preserves your existing setup while giving you a clean baseline.
Reinstalling OBS Is Rarely the First Answer
A reinstall does not correct:
- Windows sending audio to the wrong device;
- Desktop Audio being disabled;
- a muted mixer source;
- application-specific Windows routing;
- mismatched recording tracks;
- audio stored on another recording track;
- a disconnected headset endpoint.
Consider a clean profile or reinstall only after a simple test configuration also fails and the problem remains isolated to OBS.
Back up important profiles and scene collections before removing or resetting configuration.
OBS’s Quick Start Guide confirms that the Audio Mixer meters and manually selected devices are the baseline checks for audio capture. Its Application Audio Capture Guide documents current per-application capture options and warns about duplicate desktop capture when those sources are used.
The Audio Mixer is the best dividing line for this problem. A dead meter means OBS has not received the desktop audio yet. A moving meter means it has, so the investigation should move forward to recording tracks or monitoring instead of repeatedly changing the playback device.
