Mac screen share audio: what can viewers hear?

Your Mac's output and the meeting's transmitted stream are different paths. Set both, then let a remote listener prove the result.

Published June 17, 2026 · Updated August 5, 2026 8 min read By John Sciacchitano

The short answer: hearing the right mix on your Mac does not prove viewers hear it. First set the local output device, source level, alerts, and background apps. Then choose the meeting app's share-audio control and verify the transmitted stream from another device or with another participant.

TeenySound is my app, so the bias is obvious. It is useful here because it gives each audio-producing app its own slider, mute control, mute-all with restore, and output routing. Still, Apple's Sound settings and the meeting app come first. If the wrong device is selected, a per-app mixer is fixing the wrong layer.

This is the TeenySound spoke for the TeenyApps Mac screen sharing privacy checklist. The matching clipboard spoke is Mac clipboard history before screen sharing.

Separate local audio from transmitted audio

Layer Main control What proves it
Local Mac output Sound settings: output device, output volume, and alert volume. You hear the correct device and levels.
Source and background apps The app's own control or TeenySound's per-app volume and mute. The local mix contains only the intended source.
Transmitted computer audio Zoom Share sound, Meet audio sharing, or Teams Include sound. A remote listener hears the intended source and no interruption.
Capture permission Privacy & Security > Screen & System Audio Recording. The meeting or recording app can capture the allowed source.

01Pick the output device first

Apple's Sound settings choose where your Mac plays audio: internal speakers, display speakers, headphones, USB audio, AirPlay, or another connected device. Start there. If the Mac is playing through the wrong output, app sliders will not make the shared session sound predictable.

Then check alert volume. Alerts and sound effects can be louder than the demo source, especially when a Mac has moved between headphones, display speakers, and desk speakers. Lower alerts or use Focus if notifications do not belong in the session.

If the session is a support call, use the narrower Mac support call audio test. It separates local playback from the meeting app's transmitted computer audio, then uses a remote positive and negative check.

Only after that should you change one app's level. The order matters because system output changes the room. App volume changes one source.

02Choose the meeting app's audio switch

If the audience only needs to see the app, leave computer audio out of the share. If they need to hear a video, tutorial, product sound, or music example, enable audio deliberately and test that exact path.

Meeting app Current control Important scope detail
Zoom desktop Select Share sound in the Share Screen window. Leaving it unchecked keeps computer sound out of the screen share.
Google Meet A shared tab sends tab audio by default. A window or entire screen can use Also share system audio. Confirm the selected surface and its audio option together.
Microsoft Teams Turn on Include sound. Teams desktop says all computer audio, including notifications, becomes part of the meeting. Teams on the web varies scope by tab, window, or entire screen.

For a live slide deck or hybrid room, use the refreshed Mac presentation audio checklist. It separates the Mac's local output from the meeting app's shared-audio path and adds a remote-listener test.

Apple's Privacy & Security settings let you control which apps and websites can record screen and audio. An app can be allowed to record both or audio only. Permission enables capture, but it does not turn the meeting app's share-audio control on.

When computer audio is part of the share, treat every audible app as eligible for the session until the remote test proves otherwise. This is when per-app volume and mute become useful.

03Mute background apps before they surprise you

Close apps that do not need to run. Pause music, videos, games, social apps, and chat apps. If an app should keep running but stay quiet, mute it instead of quitting it.

teenysound shows audio-producing apps in a menu bar mixer. The local Swift source discovers audio processes with Core Audio, groups helper processes under the responsible app where possible, and gives each app a volume and mute state. The app row includes volume, mute, reset, hide, output-device, and per-device volume actions.

TeenySound changes the local app mix. It does not enable Zoom Share sound, Meet's audio option, or Teams Include sound. Those controls still decide whether the meeting transmits computer audio.

Use the app's own mute when that is the clearest control. Use TeenySound when the app control is missing, buried, inconsistent, or too broad for the session.

04Use mute-all when you need a quiet baseline

Mute-all is the fastest way to make controlled app audio quiet before a sensitive share. TeenySound uses Option-Shift-A by default. Press it once and controlled apps go silent. Press it again and TeenySound restores the prior per-app levels.

The restore part matters. The source stores pre-mute app volumes by bundle ID, marks apps muted, then restores those previous volumes when you toggle back. That makes it useful before screen sharing because you can get a quiet baseline without rebuilding the mix from scratch afterward.

For the shortcut-specific guide, read Mute all Mac apps with one keyboard shortcut.

05Test from the listener's side

Do not test with a random YouTube tab if the share will use Keynote, QuickTime, a browser product demo, or a meeting app. Play the exact source that the audience should hear. Then test the exact share path.

Join from another device with its microphone muted, or ask another participant to listen. Check for three failures: the source is silent, the source is too loud, or another app is audible. If the source is silent, check the meeting's share-audio control before changing the local mix. If another app is audible, mute or quit it.

If the issue is routing rather than volume, use Route Mac app audio to different outputs. If the issue is a dock or monitor taking over audio, use Mac audio switches to monitor speakers.

Five-minute pre-share audio pass

  1. Choose the macOS output device in Sound settings.
  2. Lower alert volume or use Focus if notifications do not belong in the session.
  3. Choose the meeting app's computer-audio setting, or leave it off for a visual-only share.
  4. Play the exact source app and set its level.
  5. Mute, lower, pause, or quit unrelated audio apps.
  6. Verify the transmitted result from another device or with another participant.
  7. Restore the per-app mix after the session if you used mute-all.

Common questions

What Mac audio should I check before screen sharing?

Check two paths: local output in Mac Sound settings and transmitted audio in the meeting app. Set the source and background app levels, then have a remote listener confirm what the meeting actually sends.

Should I share system audio during a Mac screen share?

Only when the audience needs it. Zoom uses Share sound, Google Meet varies audio sharing by tab, window, or entire screen, and Teams uses Include sound. Leave that control off for a visual-only share.

Can I mute background apps without muting the whole Mac?

Yes. Use the app's own mute or a per-app mixer such as TeenySound when one background app should be quiet while the meeting or demo source stays audible.

Sources checked

Keep only the right app audible.

teenysound is a native Mac per-app audio mixer with app sliders, mute, mute-all restore, routing, device volume memory, and keyboard shortcuts. $9.99 once, 3-day free trial.