
You can hear a game or video through your headphones, but OBS Studio records silence. Before changing drivers or reinstalling anything, find out where the sound stops. A moving Desktop Audio meter means OBS is receiving sound; a flat meter means it is not. Then make a 10-second test recording to check whether the sound reaches the file. This guide walks through both results on Windows and macOS.
Open a video or music file that you know produces sound. Keep it playing, then look at the Audio Mixer in OBS. Watch the Desktop Audio meter, not the microphone meter. Click Start Recording, record about 10 seconds, stop, and play the file outside OBS. OBS recommends checking the mixer and making a test recording before a real session.
| What you see | What it usually means | Go to |
|---|---|---|
| The Desktop Audio meter stays flat | OBS is not receiving sound from the selected device or app. | Check the capture device and app output. |
| The meter moves, but the file is silent | Sound reached OBS but may not be routed to the recorded track. | Check track and monitoring settings. |
| The file has sound, but you cannot hear it while recording | Capture may be working; headphone playback and OBS monitoring are separate. | Check what you are monitoring. |
On Windows, the most common mismatch is simple: your browser or game plays through one output, while OBS listens to another. This often happens after switching from speakers to a USB headset, connecting Bluetooth headphones, or plugging in an HDMI monitor.
To capture one headset or speaker in a particular scene, click + in Sources, add Audio Output Capture, and select the same device that plays the sound. Do not capture that device both here and through the global Desktop Audio setting; duplicate capture can create echo. If you only need game or browser sound on a supported Windows setup, Application Audio Capture may be cleaner. OBS also supports adding app audio through newer Window Capture or Game Capture options. Disable global Desktop Audio when you intentionally use per-app capture to avoid picking up the same sound twice.
If you are deciding between whole-desktop and app-only sound for a screen recording, the OBSBOT guide to recording audio with screen video covers those broader workflow choices.
A moving meter proves OBS received the sound. It does not prove that your recording includes it. Work through these checks in order:
If you are still setting up the rest of your recording, see the OBSBOT overview of OBS recording settings. For the audio-track behavior itself, follow the OBS multiple-audio-track guide.
On macOS, a flat Desktop Audio meter does not always mean a broken output device. The capture method depends on your macOS and OBS versions:
If a macOS capture source cannot see the intended window or app, review OBS permissions in macOS and restart OBS when the system requests it. The official macOS desktop-audio guide explains the available paths by version.
After each change, record a short clip with the actual app, headset, and scene you plan to use. Play the file through a regular video player and confirm that the game or browser sound and microphone are both present at sensible levels. If you deliberately record separate tracks, also inspect the file in an editor that can show every track; a standard player may play only Track 1.
Do not judge the result only by what you hear in your headphones. Monitoring controls what OBS sends back to you, while output tracks control what goes into the recording or stream. If the recording is correct but your headphones are quiet, fix monitoring or the system playback device without undoing a working capture route.
The game may be playing through a headset or monitor that OBS is not capturing. Compare the game's output in Windows Volume mixer with Settings > Audio > Desktop Audio in OBS. If they differ, choose the actual output device in OBS or use an app-specific capture source.
The microphone and desktop audio are separate sources. A working mic does not confirm that OBS selected the correct speaker or headset. Check the Desktop Audio meter first; if it moves, check the desktop source’s recording-track checkbox.
Your sound may be on a separate audio track that the player does not select. For straightforward playback, assign the sources you want viewers to hear to Track 1 and record that track. Keep separate tracks as extras when you need editing flexibility.
Not necessarily. On Windows, display capture handles the picture; configure desktop or app audio separately and confirm the relevant mixer meter moves. On supported macOS versions, the macOS Screen Capture source can include audio, but you still need to verify its meter and the recorded file.
Windows or the app may have switched to a new output device while OBS still captures the old one. Play your test sound, inspect the app's output in Windows Volume mixer, then reselect the matching device in OBS. Make another 10-second recording before going live.
Follow the sound from the app to the OBS meter to the recorded file. A flat meter points to device or capture selection; a moving meter with a silent file points to tracks or monitoring. One short test after each change will show whether the fix worked.


