Play something on your computer and look at the Audio Mixer in OBS Studio. If the Desktop Audio meter moves, OBS is receiving system playback already; if it stays still, check the selected device before adding another source.
The right route depends on whether you need all desktop audio or only one application, and on your operating system and OBS version. Confirm the meter, avoid capturing the same output twice, then make a short recording and listen to it before relying on the setup.
Check whether OBS is receiving desktop audio
Open OBS with the scene you expect to use, start playback in the application that will provide sound, and watch the Audio Mixer. The Desktop Audio meter should rise and fall with playback. OBS's Quick Start Guide says desktop audio and microphone capture are enabled by default, but a default device may not be the output your computer is currently using.
A moving meter is useful evidence that sound is reaching OBS, but it does not prove that the final recording will sound right. The wrong app might be playing, the level may be too low, or a second capture route may create an echo. Treat the meter as the first check, then verify with a recording.
If the meter is still, open Settings → Audio and inspect the Desktop Audio device. Choose the intended playback device rather than leaving an unsuitable default selected. Names differ between systems; headphones, speakers, a monitor, or a virtual device may each appear as a separate choice. Return to the mixer and play audio again after changing the selection.
Do not add a new source just because the first meter is silent. First establish whether OBS is monitoring the output device you actually use. If the computer switches from built-in speakers to headphones, for example, OBS may remain tied to the old output. A device choice that works on one machine is not automatically the right one on another.
Select the right capture route for your goal
Decide first whether OBS should capture all computer playback or isolate sound from one application. All-system capture is usually simpler when every sound belongs in the recording: music, browser playback, and system audio can travel through the selected output. Per-application capture is more selective, useful when you want one player included while notifications or another application remain out.
The method also depends on the operating system and version. Windows has a documented Application Audio Capture source for supported Windows releases. Recent supported OBS versions on macOS provide built-in capture choices. Linux users should expect a different source family and should confirm their distribution's audio routing rather than follow Windows or macOS steps.
| Goal | Practical starting point | Check before relying on it |
|---|---|---|
| All playback on Windows | Desktop Audio in Settings → Audio | The selected device is the one currently playing sound |
| One application on supported Windows | Application Audio Capture source | The app appears in the source's selection and the meter moves |
| macOS desktop or app audio | macOS Audio Capture on supported system and OBS versions | The installed macOS and OBS versions support the chosen source |
| Linux playback | ALSA or PulseAudio capture sources | The source corresponds to the active routing setup |
| Sound tied to one scene | A scene-specific audio source where supported | The matching global capture is disabled to avoid duplication |
A scene-specific source can be helpful when one scene should contain a particular output and another should not. For a single continuously running scene, global Desktop Audio may be enough. If a capture source does not list the application or device you expect, do not assume it is silently capturing everything; check the route and use a short test.
This is also where a long-running broadcast differs from a quick desktop recording. A devotional playlist, a local news loop, or a lofi video can appear visually healthy while its audio path is silent. If your aim is to run a Malayalam internet radio station on YouTube all day, a brief sound check at the start and after routing changes is more useful than assuming the settings persist across device changes.
Capture all desktop audio on Windows
For the basic Windows route, begin with Settings → Audio and inspect Desktop Audio. Set it to the playback device your computer is using, or to the appropriate default device if that is deliberate for your setup. Apply the change, return to the mixer, and play a known sound. Check that the meter responds before you build more sources into the scene.
If you want the device associated with a particular scene, add an Audio Output Capture source from the Sources dock and choose the output device. OBS's audio sources documentation describes the available audio source types and their platform availability. A scene-specific source can make scene behaviour more explicit, but it is not a reason to leave an identical global Desktop Audio capture active.
For example, suppose your computer plays a bhajan track through headphones and the scene has both global Desktop Audio and an output-capture source set to those headphones. The same playback can reach the mixer through both routes. Disable the matching global device if the source is handling that output, then confirm that the scene still has a moving meter. Duplicate paths can sound like echo or create an unexpectedly loud signal.
Keep track of what each source represents. A useful name such as “Headphone output” tells you more later than “Audio Output Capture 2”. If you change devices, revisit both the global setting and any scene-specific sources. It is the selected route, rather than the source label alone, that determines which playback OBS receives.
OBS settings and labels can change between versions, so use the OBS source documentation for the version you have installed if a menu differs. Avoid guessing among similarly named playback devices: select one, test it, and keep only the route that produces the expected result.
Capture or isolate app audio where supported
On Windows 10 version 2004 or later and Windows 11, OBS documents Application Audio Capture for capturing a selected application's sound. Add it from the Sources dock, give it a descriptive name, and select the window or application that produces the audio. Then play sound in that app and look for activity on the source's mixer meter.
OBS's Application Audio Capture guide describes matching preferences. Matching by type suits most applications. If a window title changes as you browse or change tracks, matching by executable name may keep the capture associated with the application more reliably. The relevant choice depends on how the app identifies itself, so confirm the meter after setting it.
OBS 30.1 and later also offers a Capture Audio (BETA) option on Window Capture or Game Capture sources. This is another documented path, not a guarantee that every app will expose audio as expected. If the audio does not appear, check the source selection and the relevant OBS guide, then try a supported alternative rather than assuming the whole computer is being captured.
When an application-specific source is responsible for the sound you want, disable the corresponding global Desktop Audio device. Otherwise, the global route may capture the same application's output again, resulting in duplication. This matters especially if the rest of the desktop has sounds you do not want included: an application source can separate the selected app, while global capture may reintroduce other audio.
Some applications may not work through Application Audio Capture. OBS documents routing the app through VB-CABLE and then adding the cable's output as an Audio Input Capture source as a fallback. On Windows, the application can be assigned to CABLE Input in Volume Mixer. This is a software routing workaround, not a requirement to buy a physical cable. Follow the current instructions for the software and check that sound reaches the intended OBS meter; routing labels can be easy to confuse.
Use the platform-specific route on macOS and Linux
On macOS 13 Ventura and later, OBS Studio 30 and later includes a macOS Audio Capture source that can capture all desktop audio or a selected application. The macOS Screen Capture source can also capture audio on macOS 13 and later. The exact route depends on which source you add and what you want included; check the meter after choosing it. OBS maintains a macOS desktop audio capture guide and a Screen Capture source guide for version details.
Older macOS workflows may need additional audio routing software for desktop playback. OBS's guide describes VB-CABLE setup and mentions Loopback and Sound Siphon as options. These are third-party software choices, not prerequisites for modern supported macOS capture, and their availability or terms may change. Check the vendor's own current documentation before installing or relying on one.
On Linux, OBS's source availability information points to ALSA and PulseAudio capture sources; Audio Input/Output Capture is not listed as available there. The right source depends on the sound system and routing in your distribution. Start from OBS's audio source availability notes, select the source family relevant to your setup, then test playback in the mixer. Avoid applying Windows-specific device steps as though the interfaces were identical.
For any platform, a capture source can only work with audio it can access through the selected device or route. An application may use an unusual output path, or the operating system may direct it somewhere other than the device OBS is monitoring. If the expected meter is silent, trace the playback destination first, then adjust the OBS source. This is more reliable than repeatedly adding sources with overlapping purposes.
Check the mixer and avoid duplicate capture
Once a route is selected, inspect the Audio Mixer with only the intended sound playing. Identify which meter responds. If Desktop Audio and an application or output source both respond to the same sound, you may be capturing it through two paths. Disable the route you do not intend to use, then repeat the check.
Duplicate capture can produce a noticeable echo, a level that is louder than expected, or a confusing mix when one path is delayed relative to another. The symptom may be subtle on headphones and more obvious in a recording or on another speaker system. Do not try to solve it simply by turning a fader down: remove the redundant capture route first, then set levels after confirming that the sound appears once.
A practical check is to pause all but one source of sound, play a short clip, and watch the mixer. If your goal is one application's audio, pause or mute other playback while checking that the application source is active. Then restore other sounds and confirm they remain excluded if that is important. For an all-desktop setup, check that the selected global device catches the intended output without adding a second source for the same device.
If a long-running scene includes a video loop, music and other desktop notifications may not belong in the broadcast. Decide whether you need the playback device at all or whether the media source already carries its own audio. For a sound bath loop, for instance, compare the intended OBS audio path with the approach in how to loop a sound bath recording on YouTube Live. The useful principle is to know which source contributes the programme sound before enabling ambient desktop capture.
Make a short test recording
Before a real stream or recording, make a short local test. Start playback, record in OBS, stop after you have enough to assess it, and listen back. Confirm that the sound is present, that it belongs to the intended application or desktop route, and that it does not echo or disappear when the scene changes. A moving meter alone cannot reveal all of those faults.
OBS's Quick Start Guide recommends testing for a few minutes to catch issues before the first stream or recording. Use a realistic test: play the kind of content you intend to broadcast, and use the scene and output device you expect to keep. If you switch from speakers to headphones after testing, check again, because the selected device may have changed.
For a 24/7 channel, include the transition that is most likely to expose a fault: start the source, change scenes if relevant, and check that playback continues through the expected route. A test made while a browser is open may not prove that a separate media player is captured. Test the actual application when using app capture, or representative desktop playback when using all-system capture.
Listen on the same type of output your audience-facing recording will use, not only by watching the mixer. If the recording is silent, return to the source and device selection. If it contains doubled sound, remove one of the overlapping paths. If it captures unwanted notifications, switch from global desktop audio to an application-specific route where supported. Make one change at a time, then repeat the short recording so you know which adjustment helped.
Keep the computer and broadcast workflow in view
OBS captures audio from the computer that is running OBS, so the playback application and capture route need to remain available for the session. A local setup can be suitable when you want control over a live desktop or multiple changing applications. It also means you should consider what happens if the computer sleeps, reboots, changes its output device, or loses the application that supplies sound.
If the stream is a prepared video intended to repeat continuously, desktop audio capture may be part of a broader OBS workflow rather than the only decision. Your encode and operating setup matter too; for example, see the practical trade-offs in making a 24/7 YouTube lofi stream use less CPU. Keep the audio test separate from assumptions about whether the computer will remain available overnight.
Where the broadcast is simply an uploaded video that should keep playing while your computer is switched off, StreamNeo removes the need to keep a desktop playback and OBS capture route running on your own machine. That is a different operating choice from using OBS to capture changing desktop sound; check that it fits the format you actually plan to run.
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
Why is Desktop Audio not moving in OBS?
The selected device in Settings → Audio may not be the output currently playing sound. Choose the active device, then play audio again and watch the mixer. If you use a platform-specific capture source, check that source and its application or device selection instead.
Can OBS capture only one application?
OBS documents Application Audio Capture for Windows 10 version 2004 or later and Windows 11. Supported macOS versions also have a macOS Audio Capture source for all desktop audio or a selected application. The route depends on your OS, OBS version and whether that app's audio is available through the capture path.
Why does my recording have an echo?
A common cause is capturing the same playback through global Desktop Audio and a second source. Disable the redundant route and make another test recording. If the sound remains doubled, check for other active sources or routing paths.
Should I test before going live?
Yes. A short recording lets you hear faults a meter cannot show, including silence, unwanted desktop sounds or duplicate audio. Test the actual application and scene you intend to use, then repeat the check after changing the playback device or capture route.