START HERE
With OBS 30 or later on macOS 13 or later, start with a macOS Audio Capture source and choose the desktop or intended application. Check OBS’s permissions and make a recording. A macOS Screen Capture source can also carry sound, so avoid capturing the same application through both sources.
Check the OBS and macOS versions first
Open About OBS and About This Mac and note both versions. OBS’s native audio guide separates the dedicated macOS Audio Capture source in OBS 30+ from the screen-capture method used in OBS 28/29. Both native audio routes require macOS 13 or later. The modern screen source can capture video on some older systems without also providing sound.
That distinction explains a common false start: a guide written for an older Mac tells you to install a virtual driver even though your current setup has a native audio source. Use an OBS release compatible with your Mac; do not upgrade an unsupported OS or install several audio drivers just to make a missing menu appear.
Review the permissions that match the source
In OBS, open OBS Studio → Review App Permissions. Follow the system prompt for screen capture when capturing displays/apps and microphone access when capturing a microphone or audio input device. On newer macOS versions, open System Settings → Privacy & Security → Screen & System Audio Recording to review that access; older system versions use different labels. Restart OBS if the system requests it after a permission change.
A moving physical-microphone meter proves that microphone input works. It does not prove that application sound is allowed. Conversely, capturing desktop sound does not establish that your USB microphone is selected. Test these as separate sources so a permission problem does not become confused with a device-selection problem.
Add one native audio source
- Create a temporary scene and add macOS Audio Capture from the source picker.
- Select all desktop audio for a broad test, or the specific application if only that program belongs in the broadcast.
- Start a harmless local clip in that application. Ensure the player itself is not muted.
- Watch the new source’s meter, record a short sample, then stop the player and listen to the file.
- For an application-specific source, play a second application separately. Confirm it is absent from the recording before using the scene with private calls or notifications.
Keep the initial scene free of old loopback inputs and duplicate screen-capture sources. Give the new source a descriptive name such as “Presentation app audio” so a later scene change does not leave you guessing which route is active.
Understand when a screen source already supplies sound
macOS Screen Capture is another audio-capable route on supported macOS. If you capture a presentation’s picture and sound there and add a separate audio source for the same presentation, the audience can receive two copies. Mute one route and replay the same clip to check whether it was duplicated.
On older OBS versions using the screen source for audio, hiding that source can also remove its audio. Keeping the screen source visible behind another scene layer is different from toggling its visibility off or deactivating it. For audio-only capture on a current compatible installation, the dedicated audio source avoids relying on an invisible picture. Test the actual scene transitions you use rather than assuming all sources remain active between scenes.
Diagnose silence from the nearest working checkpoint
- No native source is available: confirm the versions before choosing an alternative route. For a Mac that cannot use native capture, follow the virtual-device vendor’s OS-specific setup and document the output device you changed.
- The source exists but the meter is still: replay the local clip, reselect the intended application, and review permissions. Some protected playback cannot be captured; compare an unprotected local file instead of trying to bypass it.
- The meter moves but the recording is silent: check source output mute and the selected recording track. A headphone-monitor setting is a different control.
- Only certain scenes are silent: inspect source visibility, scene membership, and whether the audio depends on a screen-capture source.
Check capture and listening independently
Once a recording is correct, decide whether you need OBS monitoring at all. If the Mac already plays that app to your headphones, monitoring its captured copy can add a second delayed sound. Leave monitoring off for the baseline and use a saved recording as your reference, using the headphone stereo test outside OBS if a captured track sounds one-sided.
Finally test a loud passage, normal speech, a scene change, and the application after closing and reopening it. Once each Mac app sits on its own fader, balance your mic, game, call, and alerts in OBS around your speaking voice. If you also want Mac audio in phone-connected headphones, that is a separate listening route. Native OBS capture does not itself deliver audio to a phone, and adding another route should not require capturing the same program twice.
Sources & version notes
Documentation checked November 18, 2026. Use the platform and version notes in this guide when comparing settings. The troubleshooting checks are intended for your own setup; this review date does not represent hardware testing.