OBS Studio · Practical guide

Capture Mac Desktop or App Audio in OBS Without an Extra Driver

Use the native macOS audio source on supported versions, choose all desktop sound or one application, and verify what the recording includes.

START HERE

On OBS 30 or later with macOS 13 or later, macOS Audio Capture can capture the desktop or a chosen application. Select the narrowest route that matches the recording and check for duplicate capture.

Use the native macOS audio source on supported versions, choose all desktop sound or one application, and verify what the recording includes.

In this guide
Before you start
  • OBS 30+ and macOS 13+ for the native audio-only workflow.
  • A permitted test sound in the target app and headphones for playback.

Check the software generation before installing another route

Older tutorials may start by installing a virtual audio device because they describe an earlier macOS capture workflow. Check your installed OBS and macOS versions first. Adding another route when native capture already serves the task can make it harder to know which source produced the sound.

OBS documents macOS Audio Capture for OBS 30 and later on macOS 13 and later. It can target the desktop or a single application. This guide uses that native source; older operating systems require a different route and should not be expected to show the same source choices.

Decide which sounds belong in the file

Write down the intended mix before adding a source. A software lesson may need one application and your microphone, while a general demonstration might intentionally include several system sounds. Choose the route that matches that purpose, then use a harmless second app to test the boundary.

Inspect existing audio sources, including audio captured by a macOS Screen Capture source. If two sources include the same application, the saved mix may contain duplicate sound. Keep the test simple enough that you can identify each meter and explain why it is present.

Add and verify native app audio

  1. Create a clearly named audio source

    Add macOS Audio Capture to the intended scene. Select all desktop audio or the chosen application, then name it for that scope.

    Look for: The mixer contains an identifiable source for the sound you intend to capture.

  2. Exercise the target and a comparison app

    Play a permitted sound in the target application, stop it, then play a harmless sound in a different app. Observe which meter responds.

    Look for: A single-app route responds to the target; a desktop route includes the broader scope you deliberately selected.

  3. Record the mix and listen

    Make a short recording with the microphone and app sound, then play the saved file through headphones. Temporarily isolate sources if the sound is doubled.

    Look for: The recording contains the intended application sound once, alongside the other sources you chose.

Keep picture and sound choices understandable

A screen capture may bring its own audio behavior, while an audio-only source serves a different purpose. Name both by their roles so hiding a visual element does not become a confusing way to control sound. For the modern audio-only workflow, use the dedicated source rather than copying an old workaround without understanding it.

Test every scene used in the session. An audio source added only to one scene is not proof that the sound will continue in another. Plan whether it should stay present across scene changes and check that plan with an actual recorded transition.

Use the meter to choose the next check

If no meter responds, verify the selected app is really producing audio and confirm the version requirements and source selection. If the meter moves but the file is silent, inspect output mute and recording-track assignments rather than installing another capture driver immediately.

When the target sound is right, repeat the boundary test after restarting the application. Keep a note of the chosen app and source name. A short check after an update or source change is more useful than assuming that a working desktop-wide route proves single-app privacy and routing are also correct.

Still stuck?

The meter moves but the saved file is silent.

Check output mute and the enabled recording tracks before adding another audio capture route.

Keep troubleshooting

Check the model and connection before trying another change. The device page gathers the related symptoms.

More help with OBS Studio ↗

Sources & references

Based on the linked first-party OBS documentation checked on 4 November 2026. The exercises and acceptance checks are editorial workflows for you to run; no hands-on OBS session or hardware benchmark is claimed.

  1. OBS — macOS Desktop Audio Capture Guide ↗Checked 2026-11-04
  2. OBS — Audio Sources ↗Checked 2026-11-04

Spotted something out of date? Let Alex know.

How we put our guides together ↗
READ NEXT

A few places to go from here.

All stories

OBS Recording Has No Sound? Check Your Audio Tracks

The meters move but your OBS recording is silent? Follow the sound from your mic and desktop to the recorded track, then play the right track back.

Why Is My Audio Doubled in OBS? (Easy Fix)

Hearing your voice or game twice in OBS? Usually the same sound is being picked up two times. Here's how to find the extra one and turn it off.