How to Capture Application Audio in OBS

If you want OBS to record or stream the sound from one application, use a per-application capture source where your operating system and OBS version support it. On supported Windows systems, that usually means adding Application Audio Capture, selecting the target window, and turning off global Desktop Audio to prevent the same sound being captured twice.

The exact route depends on your platform and OBS version. Windows 10 version 2004 or later and Windows 11 have the clearest built-in workflow; recent macOS versions have their own sources; Linux needs more caution because the available device sources do not establish one universal per-application method.

Choose the workflow before adding sources

Start by identifying three things: your operating system, your OBS version, and whether you need one application or all computer audio. The source names and available options change between platforms, so following Windows instructions on macOS will not solve the problem.

Your setup	First workflow to try	Main limitation or check
Windows 10 version 2004 or later, or Windows 11	Application Audio Capture	Some applications may not output audio in a compatible way
Windows with OBS 30.1 or later	Application Audio Capture, or audio included in Window Capture or Game Capture	Choose one route for the same application, not both
macOS 13 or later with OBS 30 or later	macOS Audio Capture	Choose all desktop audio or a particular application
macOS 13 or later with OBS 28 or 29	macOS Screen Capture in Application Capture or Window Capture mode	The source’s visibility affects its audio in this workflow
Earlier macOS	An additional audio-routing method documented by OBS	Per-application routing may require separate software
Linux	The audio sources exposed by your OBS build, such as ALSA or PulseAudio	Do not assume identical per-application behaviour across distributions

You can check the OBS version under the application’s Help or About menu, depending on your operating system. If you are preparing a long devotional stream, a study channel, or an overnight broadcast, record a short local test after changing the source rather than trusting that the mixer looks correct.

The OBS Quick Start Guide recommends checking the audio meters and making a test recording before a real stream. That small step catches a silent source, a doubled signal, and an audio delay while you can still correct them.

Add Application Audio Capture on supported Windows

The Windows per-application method is documented by OBS for Windows 10 version 2004 or later and Windows 11. It is not a general instruction for every Windows release, so check the operating system version first if the source is missing.

Open the scene where you want the application’s sound.
In the Sources dock, select the plus button.
Add Application Audio Capture.
Give the source a descriptive name, such as Browser music or Game audio.
Select the window containing the application that is producing sound.
Choose the window matching priority that best fits the application.
Confirm that the source appears in the Audio Mixer and that its meter moves when the application plays audio.

OBS describes Application Audio Capture as a beta source in its Windows guidance. That does not mean you should avoid it, but it does mean you should verify the particular application before relying on it for a long unattended broadcast.

For most applications, matching by window type is the sensible first choice. If you are capturing a game or a fixed desktop application, its window may stay stable for the whole session. Select the application before starting your test recording, because a source that has been added but is not attached to the correct window can look configured while carrying no sound.

OBS 30.1 and later also allow audio to be included with a Window Capture or Game Capture source on compatible Windows setups. You can enable Capture Audio in that source. This can be useful when you want the picture and sound tied together, but do not enable it and add a separate Application Audio Capture source for the same application unless you have a deliberate reason and understand the resulting mix.

The OBS Application Audio Capture guide is the best place to check the current source behaviour and supported options. OBS may change labels or compatibility as the feature develops, so use the installed version’s interface as the final reference.

Select the target application carefully

Application Audio Capture does not mean “capture whichever sound is currently coming from the computer”. It attaches the source to a selected application window. If the application has several windows, you need to choose the one that is actually playing audio.

Open the application and start a sound that is easy to recognise. A short spoken clip is more useful than a quiet music bed because you can quickly confirm whether the right source is responding. Then return to OBS, open the source properties, and select the relevant window.

A browser is a common source of confusion. One browser window may contain a video, while another contains a silent page. If OBS lists several similar windows, use the title shown in the source properties and test the one that contains the playing tab. If the browser creates a separate audio or pop-up window, select that window only if it is the one producing the sound.

Do not judge success only by the presence of a source in the Sources dock. Look at the corresponding Audio Mixer channel. A moving meter indicates that OBS is receiving a signal; it does not by itself prove that the recording contains the expected sound, which is why the playback test later in this guide matters.

If you also need a microphone, keep the microphone as a separate source. This gives you independent control over the voice and application levels. For a tutorial, for example, you may want the application quiet enough for narration. For a radio-style stream, you may want the application source to carry the complete programme without adding microphone input at all.

Handle applications whose window title changes

Some applications change their window title as you use them. A browser may replace the page title whenever you change tabs. Spotify and similar players can also update the title as the track changes. If the source is matched too strictly to the current title, it may stop following the application when that title changes.

In the Application Audio Capture properties, try a matching option based on the executable name for applications with changing titles. OBS documents executable-name matching as a way to keep capture attached when titles change. The precise options presented may depend on the source and installed OBS version.

Test this deliberately. Start audio, confirm the meter moves, then perform the action that normally changes the title: change browser tabs, start another track, open a new document, or move from a menu into the main application. Watch the mixer again. If the meter stops, revisit the matching priority rather than assuming the stream will recover later.

There is a trade-off with broader matching. A rule that follows an executable can be more resilient, but it may also capture audio from another window belonging to that same application. If you have several browser windows and only one should be heard, inspect the result in a short recording. A reliable source is one that follows the intended window without silently adding unrelated sound.

When an application has a fixed title and you need only that window, a more specific match may be easier to reason about. When the title changes constantly, executable-name matching is often the practical choice. The correct setting is the one that survives the actions your channel will actually perform.

Avoid capturing the same sound twice

The most common bad result is not silence but duplication. You add Application Audio Capture for a game, leave global Desktop Audio enabled, and OBS receives the game through both paths. The recording can contain an echo, a hollow sound, or a louder signal than expected.

If you are using per-application sources, open Settings → Audio and disable global Desktop Audio. Then keep the application-specific source as the single route for that application. This is especially important when your Windows playback device is also selected as a global desktop source.

The same principle applies when using Window Capture or Game Capture with Capture Audio enabled. Do not also add a separate source for the same signal unless you are intentionally mixing two distinct copies. In normal use, choose one of these arrangements:

application-specific source with global Desktop Audio disabled;
Window Capture or Game Capture with its audio option enabled; or
global Desktop Audio for all computer sound, when you do not need application isolation.

Avoid switching between arrangements without checking the Audio Mixer. Removing a source from the preview does not always answer the routing question, because a source may still exist in the scene or another scene may be active. Check the scene you will actually use for the broadcast.

OBS also warns that adding an input or output device to a scene can echo if the same device is already selected in the global audio settings. This is why a neat-looking list of sources is not enough. Write down which route is meant to carry each sound, then remove or disable duplicate routes.

For a 24/7 channel, this check matters before you leave the computer unattended. If your source is a finished video file rather than a live application, you may find that a cloud workflow is simpler than leaving a desktop session running. StreamNeo removes the need to keep OBS and the computer operating for that particular uploaded-video-to-YouTube use case, but it does not replace OBS when you need to capture a live application.

If a completed recording has a doubled or distorted signal, compare it with the guidance in how to fix a YouTube radio livestream with distorted audio. The symptom may originate in capture routing rather than in the source media itself.

Verify levels and test playback

Once the source is selected, make a short local recording. Do not go directly to a public overnight stream. A test should include the actions that matter: start the application, produce sound, change its window title if that is normal for the app, and speak into the microphone if you are using one.

Watch the Audio Mixer while recording. The application channel should respond when the application plays sound. If the microphone is separate, its channel should respond only when you speak. This separation makes it easier to find out whether the problem is capture, routing, or the source material.

After stopping, play the recording from beginning to end. Check four points:

Is the application sound present, not merely visible on the mixer?
Is the sound present only once, without an echo or doubled timing?
Can you hear speech or music clearly when the microphone is active?
Does the sound continue after the application changes title, track, tab, or window?

Use headphones for the first check, but also listen through the device your viewers are likely to use. Headphones can reveal a duplicate signal that is less obvious on a small speaker. If your channel uses a quiet devotional track or ambience loop, listen for low-level doubling as well as obvious echo.

Keep the test file until you have completed the broadcast setup. It is useful evidence if you later change OBS versions, Windows audio settings, or the application itself. If you are building a longer source for continuous streaming, the FFmpeg encoding guide can help with the separate question of preparing a file for a stable YouTube stream; it does not replace the OBS capture test described here.

Before going live, also confirm that the correct scene is selected, the source is not muted, and any monitoring settings are intentional. Monitoring audio back into the same playback device can create feedback or make troubleshooting confusing. The viewer-facing recording, rather than your local monitor alone, is the final test.

If your plan is to run an overnight playlist rather than capture an interactive application, keep the workflows separate. The guide to scheduling a YouTube playlist livestream overnight in India covers a different operating model, where the key risk is continuity of the prepared playlist rather than application-window capture.

Troubleshoot missing application audio

The source is not listed

First check the OS and OBS version. Windows Application Audio Capture is documented for Windows 10 version 2004 or later and Windows 11, not every Windows version. On macOS, the available native sources depend on both macOS 13 or later and the OBS version. Linux exposes audio device sources, but the reviewed OBS documentation does not establish one general per-application recipe for every Linux desktop.

Restarting OBS after installing or updating the application can also help the source list reflect the current environment. Do not treat a missing source as proof that the application itself has no audio.

The meter does not move

Confirm that the application is playing sound through the expected output and that the selected window is the one producing it. Check the operating system’s volume controls, then reopen the source properties and select the target again. A muted application, a paused browser tab, or a different output device can all look like an OBS failure.

Make a new short recording after each meaningful change. This prevents several untested changes from hiding the actual cause.

Windows still does not capture the app

OBS notes that some applications output audio in a way that is incompatible with Application Audio Capture. Its documented fallback is to install VB-CABLE, route the target application to CABLE Input through the Windows Volume Mixer, and add the cable as an Audio Input Capture source in OBS.

This route adds another device and another place where the signal can be muted or misdirected. Use it as a fallback after testing the native source, not as the first step. Once configured, apply the same duplicate-audio rule: do not also capture the same sound through global Desktop Audio.

macOS audio is missing

On macOS 13 or later with OBS 30 or later, try macOS Audio Capture and choose either all desktop audio or the target application. You can also use macOS Screen Capture, which includes audio on supported macOS versions. With OBS 28 or 29 on macOS 13 or later, OBS documents using macOS Screen Capture in Application Capture or Window Capture mode.

In that older OBS workflow, check whether the Screen Capture source is visible. OBS says that hiding the source also removes its audio. If you need only the sound, the source can be placed behind other sources or its dimensions can be set to zero, provided it remains active in the scene.

On earlier macOS versions, OBS documents additional routing methods. It distinguishes VB-CABLE as a desktop-audio route without per-application capture, while Loopback and Sound Siphon are described for per-application routing. Check the current OBS documentation and the current compatibility details for any additional software before relying on it.

Linux behaves differently from the example

OBS documents Audio Capture Device sources on Linux through ALSA or PulseAudio. That is useful for device-based capture, but it does not prove that the same per-application selection will be available or behave identically on every Linux distribution, desktop environment, and audio system.

Open the source list in your installed OBS build and identify what it exposes. If the task requires isolating one application, confirm the route with a local recording before designing the live channel around it. A Linux setup that works on one desktop audio system may need different routing on another.

Prepare the final live test

When the local recording is clean, test the actual scene and output path you intend to use. Start the application, wait for its sound to begin, and watch the mixer without changing anything. Then make a short private or otherwise controlled live test if your channel workflow permits it.

Check the result from the platform side as well as inside OBS. The Audio Mixer proves that OBS has a signal; the recorded or received stream proves that the signal survives the rest of the path. This distinction matters when you are preparing a long-running YouTube broadcast.

Keep a simple note of the working setup: operating system version, OBS version, source name, matching mode, and whether global Desktop Audio is disabled. If an automatic update changes the source list or behaviour, that note gives you a reproducible starting point instead of a vague memory of what worked.

Do not add extra capture sources merely because they are available. Each additional route creates another opportunity for duplication, unexpected monitoring, or a silent device. A small scene with one deliberate application-audio path is easier to check at three in the afternoon and easier to trust before you leave it running overnight.

Before committing, compare the operating options on the pricing page. When the file and channel are ready, start free — 24-hour trial, no card.

FAQ

Can OBS capture only game audio?

On supported Windows versions, add Application Audio Capture and select the game window, then disable global Desktop Audio if that is the only computer sound you want. OBS 30.1 and later may also let you include audio in a Game Capture source. Test one method at a time so the game is not captured twice.

Why do I hear an echo after adding application audio?

The same sound is probably reaching OBS through two routes, such as Application Audio Capture and global Desktop Audio. Disable the duplicate route in Settings → Audio or remove the second source, then make another short recording to confirm that the echo has gone.

Can I capture one application on macOS?

On macOS 13 or later, the available method depends on your OBS version. OBS 30 and later provide macOS Audio Capture, while OBS 28 and 29 use macOS Screen Capture in an appropriate capture mode; earlier macOS versions may need additional routing software documented by OBS.

Does Linux have an equivalent source?

OBS documents ALSA and PulseAudio audio capture sources on Linux, but that does not establish one identical per-application workflow across Linux configurations. Check the sources exposed by your installed build and verify the result with a recording before going live.