If one specific application records silent while the rest of your OBS mixer behaves normally, the problem may not be on your end at all. OBS's own knowledge base labels Application Audio Capture as a BETA source, and it says in writing that some applications are incompatible with it.
That admission is the single most useful fact about this error, and it is missing from almost every checklist written about it. Before you restart OBS for the fourth time, work out which part of this is a setting you control and which part is a documented limitation.
What this source actually is
OBS's Application Audio Capture Guide opens with the conditions, and every clause in it matters:
"As of OBS Studio 28, per-application audio sources are available for users running Windows 10 (Version 2004 or later) and Windows 11. These Application Audio Capture (BETA) sources allow you to add each application you would like to capture as its own audio source. With the release of OBS Studio 30.1, you are able to include audio with a Window Capture or Game Capture source."
Three separate gates are stacked in that paragraph:
- Operating system — Windows 10 (Version 2004 or later) and Windows 11. An older Windows 10 build is outside what that sentence covers.
- OBS version — per-application audio sources arrive as of OBS Studio 28.
- A second, later feature — audio bundled into a Window Capture or Game Capture source is separate, and the guide ties it to OBS Studio 30.1.
That third point causes a specific confusion: someone follows a tutorial that says to tick the audio option on their Game Capture source, finds no such option, and concludes the install is broken. It is a version difference, not a fault.
The line the documentation buries
Here is the sentence worth the whole page. Verbatim from the same guide:
"Due to how some applications output some of their audio, it may be incompatible with the Application Audio Capture (BETA) source. For these applications, there are separate steps required to isolate the missing audio as it's own source in OBS Studio."
Read the qualifiers: some applications, and some of their audio. That wording covers an app whose audio is only partly picked up, not just one that is captured or not at all.
Two things follow. "It works for my friend" proves nothing — compatibility depends on how the application emits audio, so identical settings on identical Windows versions can give different results for different apps. And the official escape route is application-specific: OBS says separate steps are required to isolate the missing audio as its own source. Start from OBS's help page and check the official documentation for the app you are capturing rather than guessing at a workaround.
The fastest check: did any audio reach the file?
Before rebuilding your audio setup, work out which of two situations you are in — they sound identical during playback:
- Nothing was captured. The source produced silence, and there is nothing to recover.
- Something was captured, but you are not hearing it. OBS can write several audio tracks into one file, and ordinary players read only one of them.
The live check is the mixer. If that application's level meter never moves while the app is making noise, nothing is being captured and no output setting will change that. If the meter moves and the recording is still silent, the audio is in the file and the problem is routing.
For a file you have already recorded, pulling the audio out tells you something concrete:
Try it right here
Runs in your browser. Your file is not uploaded anywhere.
Be precise about what this proves. The tool reads the first audio track only (-map 0:a:0 internally), and it runs in your browser, so the recording stays on your machine. Audible output means track 1 contains sound; a silent result means track 1 specifically is empty — not that the file is. To reach track 2 or beyond you need the command line, and extracting audio with FFmpeg covers -map 0:a:1.
Other causes, in order of likelihood
1. You disabled global Desktop Audio, as instructed
The guide includes this note:
"Note: if you are using Application Audio Capture sources you will want to set your global Desktop Audio source to disabled in the Settings → Audio menu to avoid echo"
That advice is sound on its own. But put it next to the incompatibility note: you have switched off the catch-all source, and the per-application source may not be able to capture that particular app. Neither note is wrong; together they describe a configuration where an incompatible app has nothing left picking it up. If you disabled Desktop Audio and one app went quiet at the same moment, start there.
2. The audio is on a track your player ignores
OBS's multi-track guidance is blunt about the consequence (the example it points to is on their own page):
"It is important to note that all standard video players will only play back one audio track at a time so if you are not planning on processing every video through an editor before publishing it, send all of your audio sources to track 1 like you see in the example below."
Track assignment is a two-step affair, and skipping either half produces confusing results. Per the official instructions, you assign sources in Advanced Audio Properties (the gear icon at the bottom left of the Audio Mixer dock), and you enable the tracks you want recorded in Settings → Output. Do one without the other and the file will not match what you thought you configured. See how many audio tracks OBS can record and OBS recording has no audio for the wider case.
3. Your output mode is hiding the track controls
The Standard Recording Output Guide notes:
"When in the Advanced view you can select which audio tracks you'd like to record which can be helpful if you have, for example, copyrighted music in your stream that you don't wish to have recorded."
If you cannot find the per-track recording checkboxes, that is the view you are missing — the multi-track guide likewise tells you to switch to Advanced Output Mode to get those options.
4. The sound is there, but only in one ear
A different symptom, also documented. From the Audio Mixer Guide:
"If only the first meter lights up, your viewers will only hear that source in their left channel. You can enable "Downmix to Mono" in the Advanced Audio section of the Audio Mixer to force 1 channel audio to 2 channels."
The diagnostic is visual — one meter lighting instead of two — and the fix is a single checkbox.
If you are on macOS
Application Audio Capture is the Windows source described above; macOS has its own path, with its own version conditions:
"When using OBS Studio 30 on macOS 13 (Ventura) and higher, you can use the new macOS Audio Capture Source. You can choose to capture all desktop audio or just a certain application."
OBS 28 and 29 on macOS 13 and higher could already capture desktop audio or the audio from a single application; on older macOS versions, OBS says additional software is required. And one line saves a lot of confusion:
"If the source is hidden, the audio will be removed."
Hiding the capture source in your scene takes its audio with it. If you want the sound without the picture, OBS's documented options are to place the macOS Screen Capture Source behind all other sources, or to set its transformation to zero width by zero height. OBS not recording desktop audio on Mac goes through the full version matrix.
How to tell it worked
Do not trust the preview. OBS's guidance is to test the way the recording will actually be used:
"Finally, be sure to record a session as you normally would and then listen back to the file before going live."
Record a session the way you normally would, with the real applications running, then play the file back in the player your audience will use — not in an editor, which reads every track and so tells you nothing about what a normal player does. While recording, watch that application's meter; the peak indicator shows the loudest level in the last 20 seconds, enough to confirm sound is arriving.
FAQ
Why is OBS not capturing audio from one specific application? OBS documents this directly: some applications are incompatible with the Application Audio Capture (BETA) source because of how they output some of their audio. The guide says separate steps are needed to isolate that audio as its own source — check the official documentation for your case.
Is OBS Application Audio Capture still in beta? The source is labelled "(BETA)" in OBS's own knowledge base, and the same page is where the incompatibility note appears. Check the official documentation for the current status in your version.
Why can't I find Application Audio Capture in OBS? The guide describes it as available as of OBS Studio 28 for users running Windows 10 (Version 2004 or later) and Windows 11. Including audio with a Window Capture or Game Capture source is separate and came with OBS Studio 30.1.
Should I disable Desktop Audio when using Application Audio Capture? OBS says you will want to set the global Desktop Audio source to disabled in Settings → Audio to avoid echo. Just be aware of what that leaves you with if one of your applications turns out to be incompatible with the per-app source.
Can I recover the sound from a recording that is already finished? Only if it was captured. If the mixer meters were moving, the audio is in the file and may simply be on a track your player does not read. If they were flat, nothing was recorded and there is nothing to retrieve.
Quotes from OBS Studio's own knowledge base — the Application Audio Capture, macOS Desktop Audio Capture, Audio Mixer, Multiple Audio Track Recording and Standard Recording Output guides — checked 16 September 2026. More in the fix archive, or try extract audio from video and all Clapr tools.
