OBS Isn't Capturing Audio from a Specific App: Causes and Setup
How Application Audio Capture Works in OBS
Application Audio Capture doesn't capture all the audio from a device—it captures the audio session of a selected Windows process. That's why an app can be audible in your headphones but produce no signal in OBS. The source needs to find the exact process that is currently creating audio and sending it to the system.
First, look at the level meter for the source itself in the OBS mixer. If the indicator isn't moving, the problem lies before recording, streaming, tracks, and filters. In that case, check the process, the volume in Windows, launch permissions, and the output device. If the meter responds, capture is already working—you need to look for the cause in OBS routing.
The Native OBS Source and the Old Plugin-Based Capture
In OBS you may come across two sources that seem similar. Application Audio Capture is the native source for capturing audio from an individual app. Many people also still have the old "Application Audio Capture" that was added via the win-capture-audio plugin. Their settings, process lists, and behavior may differ.
During diagnostics, avoid adding both sources for the same app at the same time. Otherwise, you might mistake one source's signal for the other's working, or end up with doubled audio in the recording. The old plugin-based option has a drawback: its operation depends on compatibility with a specific OBS and Windows build, and after updates the settings sometimes need to be rechecked.
The Wrong Process Is Selected in the Source
A single app often runs several processes with similar names. The main window, launcher, update service, embedded browser, and playback module may each exist separately. In the Application Audio Capture list, it's easy to pick a visible process that doesn't create an audio session at all.
Close the app completely, then launch it again and play some sound: a video, game, call, or music. After that, open the source properties in OBS and select the process that appeared during playback. If the source is bound to an old instance of the app, delete it and create a new one. This approach has a clear drawback: the source's settings and filters will have to be configured again.
The App's Child Process Is Creating the Audio
Browsers, game clients, editors, messengers, and apps with built-in players often output audio through a process other than the main one. The app window stays in one process, while the tab, video player, ad, voice chat, or game runs in another. Capturing the main process in this situation will produce silence.
Check the process list at the exact moment the sound starts. For a browser, a separate profile, a separate window, or launching the needed site without extra tabs helps: that makes it easier to figure out which process is tied to playback. The drawback of this solution is that after restarting the browser, switching tabs, or refreshing the page, the process may change, and the binding in OBS needs to be checked again.
OBS and the Captured App Are Running with Different Permissions
Windows restricts regular apps' access to processes running with elevated privileges. If a game, launcher, or work app is open as administrator while OBS runs normally, the source may appear in the list but receive no audio. A similar situation is possible in reverse.
Run OBS and the target app at the same permission level. Most often it's enough to open both apps normally. If the app genuinely needs elevated privileges, run OBS the same way. Always running OBS as administrator has a drawback: plugins, captures, and integrations may behave differently, and the app itself will have access to system actions that usually aren't needed for streaming.
The App Doesn't Create an Accessible Windows Audio Session
Application Audio Capture works through Windows audio sessions. If an app uses non-standard output, a specific driver, a virtual device, or a closed media stream, a separate session may not appear. Then OBS won't be able to capture the app as a standalone source, even if the audio plays locally.
Open the Windows volume mixer while audio is playing. The app should appear separately and have an active level. If it doesn't, capturing that specific app may be unavailable. As a workaround, people use desktop audio capture. Its drawback: notifications, music, voice chats, and any other computer sound will end up in the stream.
The App Is Routed to a Different Output Device
In Windows, an individual app can be assigned its own headphones, HDMI monitor, audio interface, or virtual device. A different device by itself doesn't necessarily interfere with Application Audio Capture: if Windows creates a normal audio session, OBS can see it. The problem arises when the app outputs audio bypassing the standard session, or when the device is changed after the app has already launched.
After a device change, Windows often creates a new stream for the app. The OBS source may remain bound to the old inactive session: there's sound in your headphones, but the mixer indicator isn't moving. Open the Windows sound settings, check the output device specifically for the target app, then restart the app and reselect the process in the OBS source. The drawback of switching devices on the fly is that the sound may disappear only in the recording or only for viewers, while you keep hearing it locally.

Audio Is Disabled or Muted in Windows
An app has its own volume level in the Windows mixer, and it doesn't match the device's overall volume. The app may be muted, have a zero level, or be routed to a disabled device. Also check the settings of the game, player, call, or browser tab itself: the system mixer doesn't override internal audio muting.
Open the volume mixer while playback is active and make sure the app isn't turned off, its slider isn't at zero, and the assigned device is available. In a browser, check whether the tab is muted. In a game, check the effects, music, and voice chat volumes separately. After changes, restart playback and look at the Application Audio Capture meter in OBS. If the meter doesn't respond, move on to checking the process and permissions.
The Source Is Added to the Wrong Scene or Is Duplicated
An Application Audio Capture source may be in a different scene, group, or scene collection. After copying scenes, several capture instances with identical names often appear. As a result, you configure one source while another is used on air—without a selected process or with different routing.
Check the scene name, the active instance of the source, and its presence in the mixer. For diagnostics, leave one source with a clear name, for example after the app's name, and temporarily disable the duplicates. The drawback of duplication isn't just confusion: when both sources successfully receive the same signal, the audio may end up in the stream twice, causing echo, level overload, or phase distortion.
The OBS Meter Moves, but There's No Audio in the Recording or Stream
If the Application Audio Capture indicator responds, the selected process is already sending a signal to OBS. From there, you check not the source but the audio track routing. The source may be excluded from the recording track, not included in the streaming track, or turned off in the advanced audio properties.
Open the advanced audio properties and compare the source's tracks with the tracks enabled in the recording and streaming settings. Then check the filters: noise suppression, expander, gate, and compressor. An expander or gate threshold set too high can completely cut off quiet game audio, background music, or a conversation partner's lines. The drawback of aggressive filters is that they can clip the beginnings of phrases and individual quiet effects.
There's Audio in OBS but It's Not Audible in Headphones
Application Audio Capture isn't required to send audio to monitoring. The source may correctly go into the recording and stream but not play in your headphones. In that situation, rely on the mixer indicator and a short test recording, not just on local listening.
Monitoring is configured in the advanced audio properties, and the monitoring device is selected in the OBS settings. The monitor-and-output mode lets you hear the source and send it to viewers at the same time. It has a drawback: if desktop audio is also being captured at the same time, you can get signal duplication or an audio loop.
Protected Content and Limitations of a Specific App
Some apps and media services use protected playback, closed output, or restrictions for individual streams. OBS may not see the audio session or may receive silence while such material is playing. Bypassing these restrictions with third-party methods isn't advisable: it may violate the service's rules, the license, or the content's terms of use.
To test, play an allowed local file, a system interface sound, or other regular material in the same app. If that gets captured but the specific stream doesn't, the cause is related to the content type, not to OBS settings. Capturing the overall output sometimes technically passes such audio through, but its drawback remains the same: the entire computer audio stream will end up on air.
A Quick Diagnostic Order for Application Audio Capture
- Play a noticeable sound in the app and look at its source level in the OBS mixer.
- If the level isn't moving, open the Application Audio Capture properties and check the selected process during playback.
- Compare the launch permissions of OBS and the app: both should run at the same level.
- Check the app's volume, whether it's muted, and its assigned output device in the Windows mixer.
- Make sure the app appears in the system mixer as a separate audio session.
- Restart the app after changing the output device and, if needed, recreate the source in OBS.
- If the meter in OBS is moving, check the tracks, filters, and monitoring, and make a short test recording.
Last Articles
What has changed in design and functionality We have updated the website to make working with it faster and more convenient. The main changes affect ..
Good afternoon, I've collected all the news during this time.: 1. The main news is that prices for twitch viewers have been greatly reduced, while Tw..
1. Use promo code "December2025" for a 15% discount for all our viewers2. We have reduced the base prices for our configurator and the most affordable..
Twitch services are working stably, so we are ready to cooperate with squads, resellers, service owners, bot owners, and many others.Individual te..
We have completely updated our Twitch viewer services, and they are now working stably. We only use high-quality IP addresses for the viewers.The ..
Hello everyone! Today, we are announcing a new feature—"Twitch Viewer Configurator". Now, you can customize any plan for your Twitch channel. Choo..
Greetings, I have compiled a guide for streamers, which will be very relevant at the moment. Now YouTube and twitch have disabled monetization from vi..
We have finally developed the APINow it will be more convenient for our partner sites to work with us.To update the maximum tariffs for YouTube, an up..
Due to the huge popularity of the partnership services and referral program, we have made a cooperation table. The essence is very simple: more live a..
Our Services for Streamers
Our Services for Content Creators










