If you want viewers to hear your computer’s sound, add it to OBS either as a desktop or application source, or route it through a virtual audio cable. Which method works best depends on your operating system, OBS version and whether you want all computer audio or only one application.
Start by checking what OBS already captures: desktop audio and a microphone may be active by default. If the sound comes from a mixer, console or another computer, that is a different job and may need an audio interface or capture device rather than either software method below.
Decide which computer audio viewers should hear
First identify the sound you want in the broadcast. It might be everything played by the computer, such as music and system sounds, or only one application, such as a browser playing a devotional track while alerts and other desktop sounds stay private. Choosing the source before changing settings makes it easier to avoid capturing unwanted audio.
If you are playing a prepared playlist in a continuous channel, think about what else the computer might play during a long session. Notifications, a second media player, or a video with its own audio can enter a desktop capture route too. An application-specific route gives you more control, where your operating system and OBS version support it.
The two methods in this guide are software routes for computer-generated audio. Direct capture is generally the simpler place to start when OBS can see the source. A virtual cable creates a separate audio device that an application can send sound to and OBS can receive. It offers another route when direct application capture is unsuitable, but you must select the right device at both ends.
| Route | Useful when | Main trade-off |
|---|---|---|
| Desktop or application capture | OBS can capture the computer output or the specific app you want | Availability and controls differ by operating system and OBS version |
| Virtual audio cable | You need to redirect one app into a distinct OBS input | Requires installing and selecting a virtual device, and configuring the app’s output |
| Audio interface or capture device | The sound comes from physical equipment or another device | Requires suitable hardware and a compatible connection; setup varies by source |
Do not assume the same menu names or steps apply on Windows, macOS and Linux. OBS documents different approaches for each, and options can also change between OBS releases. If your goal is to operate a playlist overnight, this audio check belongs alongside the broader playback plan in our guide to scheduling a YouTube channel playlist with OBS and VLC.
Method 1: Capture desktop or application audio in OBS
Open OBS and look at the Audio Mixer before adding anything. The Quick Start Guide explains that desktop audio and microphone capture are enabled by default in many setups. Play the sound you want viewers to hear and watch the meters. If the appropriate meter responds, OBS may already be receiving the signal; adding another source for the same sound could create an echo.
If the meter stays still, or responds to the wrong device, select an audio device in OBS’s settings. In many versions, the route is Settings → Audio, where you can choose desktop audio and microphone devices. Exact labels and available sources can differ across operating systems and versions, so treat the menu path as a starting point rather than a universal sequence. The official OBS Quick Start Guide covers the initial setup and audio mixer.
For a specific application, Windows users can use OBS Application Audio Capture where supported. OBS’s guide describes this source for Windows 10 version 2004 or later and Windows 11. The guide also notes that OBS 30.1 added the option to include audio with Window Capture or Game Capture. These are version- and platform-specific details, not instructions to apply unchanged on a Mac or Linux computer.
Add the application as its own source when you need to keep its audio distinct from other computer sound. For example, a study stream might capture a music player while leaving browser notifications out. Separate sources can also help you adjust levels independently or organise audio tracks, but the routing still needs a test: the source must be active in the scene and its meter must move when the application plays.
If you are using a different operating system, consult the corresponding OBS documentation rather than looking for a Windows source by the same name. OBS’s Audio Sources guide explains adding input or output devices to a scene, and its macOS Desktop Audio Capture guide describes Mac-specific approaches. On Linux, OBS directs users towards ALSA or PulseAudio sources instead of the Windows/macOS Audio Input/Output Capture source.
Check the selected device and audio meters
Meters are the quickest indication that a signal is reaching OBS, but they do not prove that viewers will hear a clean mix. Play the intended sound and confirm that the corresponding mixer channel moves. If a different channel moves, you may have selected system audio, a microphone or another output instead of the application you meant to capture.
Check the scene as well as the global settings. OBS can have audio sources attached to a particular scene, while global desktop and microphone devices apply more broadly. If you switch scenes during a broadcast, confirm that the audio source remains available where you need it. The OBS Audio Sources guide is useful when you need to add an input or output device to a specific scene rather than rely on a global device.
Set a sensible level by listening, not by trying to make every meter reach its maximum. If computer audio is much louder than a spoken introduction, viewers may struggle to hear the voice. If your channel has no microphone, still listen for clipping, abrupt level changes or unexpected notification sounds. A meter can show that audio exists, but only playback lets you judge what it sounds like.
For a long-running channel, test the exact content and sequence you intend to broadcast. A browser may have audio while paused, muted or playing through a different output. A player may switch devices after a restart. Include a short sample of transitions, not only a single moment of playback. For a playlist setup, our guide to streaming a music playlist with OBS discusses the wider playback workflow; remove the space after the opening parenthesis to form the link correctly.
Method 2: Route audio with a virtual audio cable
Use a virtual audio cable when direct application capture is unavailable or not suitable for the application you need. It is software that presents an audio output on one side and a selectable audio input on the other. It is not a physical cable, and the basic routing method does not itself require buying a cable.
The documented VB-CABLE workflow is for Windows. Install the virtual cable from its publisher, then set the target application’s output to CABLE Input in the Windows Volume Mixer. The sound from that application is sent into the virtual device instead of, or in addition to, its usual speakers or headphones, depending on the choices available on your system. You then select the other end, CABLE Output, as an input in OBS.
This can be useful when an app does not appear as a capture source, or when you want it to have a separately selectable path. It adds configuration steps: you need to change the application’s output, add the matching input in OBS, and make sure neither end is muted. If you can already capture the application directly, that is usually less routing to maintain.
Before changing the application output, note its original device. When you direct sound to a virtual cable, you might no longer hear it from your normal speakers or headphones. Some setups allow monitoring or simultaneous output, but the available options depend on the audio devices and operating system. Do not assume the cable will automatically send sound both to OBS and to your listening device.
On macOS, do not follow the Windows Volume Mixer and CABLE Input instructions as if they were universal. OBS’s macOS guide describes other routing approaches. Linux also has its own audio source configuration. If your system’s menus differ from the steps above, use the documentation for that platform and the virtual device you selected.
Add the cable as an OBS audio input
After routing the application to the virtual cable, add the receiving side as a source in OBS. For the Windows VB-CABLE workflow, choose an Audio Input Capture source and select CABLE Output as its device. The name may look counter-intuitive: the application sends sound to CABLE Input, while OBS receives it from CABLE Output. Confirm the selected device by playing the application and watching that source’s meter.
If the source is silent, check the route in order. Confirm that the application is playing and not muted; confirm its output device is CABLE Input; check that the OBS source is set to CABLE Output; and check the source’s mute and volume controls. A silent meter usually means the signal is not reaching that source, whereas a moving meter with no audible result may point to monitoring, scene or output settings.
Keep the cable source in the scene that will actually be live. OBS sources can be scene-specific, so a source added to a test scene might not appear in the broadcast scene. Give the source a clear name, such as “Browser audio cable”, if you have several inputs. Clear names make it easier to spot an inactive or duplicate source later, especially when you return to the setup after a restart.
The cable route is a way to direct audio, not a guarantee that every application will behave identically. Applications can retain their previous output device, and device names or selections may change when hardware is disconnected. Recheck the selected output after changing headphones, interfaces or other audio devices. A short test recording will reveal whether the sound is arriving in OBS even when your normal speakers are quiet.
Prevent duplicate audio and test the result
Echo often comes from capturing one signal twice. For example, OBS may capture desktop audio globally and also receive the same application through an application-capture source or virtual cable. You may hear a doubled sound or a slight delay. OBS advises disabling global Desktop Audio when using application-capture sources to avoid capturing the same sound twice.
Review the Audio Mixer and identify every active route. If you are testing a cable input for an application, consider disabling the global desktop source for that test, provided you do not need it for other sounds. If the same physical device is selected globally and again as a scene source, that can also create duplication. Change one route at a time, then listen again so you know which adjustment fixed the problem.
Make a short test recording before your first live session. Include the exact application and scene you plan to use, then play the recording back through headphones. Listen for missing sound, echo, clipping, unwanted notifications and a volume balance that makes sense. A meter moving during setup is useful evidence, but it does not replace hearing the recorded output.
For a stream that will stay on for hours, check that the audio source remains active after the media changes or the scene switches. If you use a scheduled playlist, test a transition between items. Keep the computer’s normal notification sounds under control, and avoid relying on a sound that only plays while you are present to click a prompt. OBS recommends testing a recording or stream before the first live broadcast; that small rehearsal is easier than diagnosing a silent channel after it has started.
Audio is only one part of a stable broadcast. If OBS reports that the encoder settings are incompatible, resolve that separately from audio routing; our resolution mismatch guide for YouTube Live encoder settings covers that distinct issue. A correct audio input cannot fix an encoder or video configuration problem.
When a mixer or external source needs extra hardware
Desktop capture and virtual cables handle sound generated on the computer. A physical microphone, mixer, keyboard or other external audio source has to enter the computer through a compatible input. Depending on its outputs and the computer’s available ports, you may need a USB audio interface, a suitable adapter or another device. Check the source’s connection and the computer’s supported inputs before assuming a direct connection will work.
An interface converts or presents an external audio signal in a form OBS can select as an input. After connecting it, choose that device in OBS and check its meter, then make a test recording. The exact connections, gain controls and routing depend on the interface and source. Focusrite, for example, provides a manufacturer setup guide for using a Focusrite interface in OBS; its steps apply to that manufacturer’s equipment, not every interface.
A console or second computer may send both video and sound, and a video capture device may be relevant. But there is no single connection path that works for every console, computer and capture device. Check the outputs on the source, the capture device’s supported connections and the instructions for the hardware you own. If you only need computer-generated audio, adding physical equipment is unnecessary.
Keep physical-source troubleshooting separate from the two software methods. If an interface input meter is silent, check the cable, input selection and source output before changing desktop audio. If OBS receives the source but your test recording does not, check the scene and output mix. A clear signal path helps you find the fault without adding another route that could create echo.
If you are deciding what should run locally and what should run without leaving a particular computer on, consider the operational needs separately from audio setup. A device choice guide such as our Mac mini overview for a 24/7 YouTube playlist stream may help frame that question, but it does not change which audio source OBS needs to receive.
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 computer audio without a microphone?
Yes. Desktop audio or an application source can carry the computer’s sound without adding a microphone. Check the Audio Mixer to confirm the right source is active, and mute or disable any unused microphone input if it is not part of the programme.
Should I use direct capture or a virtual audio cable?
Start with direct desktop or application capture when your operating system and OBS version support the source you need. Use a virtual cable when you need a separate route for an application that direct capture does not handle suitably. The cable adds device and output-selection steps.
Why is my OBS audio doubled or echoing?
The same sound may be reaching OBS through two sources, such as global Desktop Audio and an application source or cable input. Disable one route at a time and listen to a new test recording. Keep only the sources needed for the intended mix.
Can I connect a mixer or another computer directly to OBS?
Not always. A physical source may need an audio interface, adapter or capture device, depending on its outputs and your computer’s inputs. Check the hardware instructions and test the complete signal path before going live.