Mac presentation audio settings for app volume

Start with macOS Sound settings. Choose the output device, set output volume, check alert volume, and test the source you will actually play. If one app needs to be loud and three others need to stay quiet, use per-app volume instead of fighting one system slider.

TeenySound is built for that app layer. It gives apps that are producing audio their own sliders, mute buttons, a mute-all shortcut, restore-all behavior, and per-app output routing. Use it when system audio is too broad, not as a replacement for the first macOS check.

This is the TeenySound spoke for the Mac presentation display and audio checklist. Pair it with Mac presentation display settings when the same presentation also depends on an external monitor. If the deliverable is a saved tutorial instead of a live presentation, use Mac screen recording audio levels.

Quick audio decision table

01Choose the output before the app

Apple's Sound settings list the output devices available to the Mac: internal speakers, display speakers, wired audio, USB speakers, headphones, and AirPlay devices. Pick the real target before you open the meeting or recording flow.

Do this before joining. Meeting apps, browsers, and recording tools may cache device choices or need a restart of the share session after an output change.

If a connected monitor keeps taking over output, use the Mac audio switches to monitor speakers checklist before adjusting app levels for the presentation.

If you use display speakers, confirm the display is still selected after reconnecting the cable or waking the Mac. If you use headphones, confirm the Mac did not switch back to a monitor, dock, or AirPlay device.

02Separate output volume from alert volume

A presentation can sound correct while alert sounds are still wrong. Apple separates output volume from alert volume in Sound settings. Use that separation.

For a demo, lower alerts or route sound effects away from the room speakers. For a recorded walkthrough, consider muting alerts entirely. For a live class, keep the source material audible but stop chat pings from becoming part of the lesson. The narrower live-teaching version is Mac workshop audio checklist.

This is where system mute is too blunt. It protects you from noise, but it can also silence the thing you are trying to present.

03Check the apps that can make noise

Presentation audio rarely comes from one clean source. A browser tab can autoplay, a music app can keep playing, a message app can ping, a video app can stay paused at a loud point, and the meeting app can have its own volume behavior.

TeenySound shows apps when they are producing audio. Its per-app manager tracks volume and mute state by bundle ID, and its mixer view exposes app sliders, app mute, output-device controls, and a system volume row.

The practical rule is simple: make the source app audible, then lower or mute every app that is not part of the presentation. If nothing else should make sound, use mute-all before you start and restore afterward.

04Route only when routing solves a real problem

Per-app routing is powerful, but it is not the first fix. Use it when you need a call in headphones while a browser demo plays through speakers, or when a recorder should capture one app without room-notification noise.

The TeenySound source stores selected output device UIDs per app and remembers per-device volumes. That makes sense for repeatable presentation stacks. It is overkill if all audio should go to one headset.

For the deeper routing workflow, use route Mac app audio to different outputs. The presentation version is narrower: route only the apps the audience or recording needs.

05Run one private audio test

Do not trust the slider position. Test sound.

Play the exact browser tab, video, audio clip, app demo, or recording source. Speak if the presentation includes voice. Start the screen share if the app has a different "share computer audio" mode. Watch which apps appear in the mixer, then lower what does not belong.

One minute is enough. If the test fails, you still have time to change the output, mute an app, switch devices, or use a simpler fallback.

Presentation audio checklist

1. Open System Settings, Sound, then choose the output device.
2. Set output volume and alert volume separately.
3. Play the exact audio source you plan to present.
4. Open TeenySound if multiple apps can make noise.
5. Lower or mute apps that are not part of the presentation.
6. Use per-app routing only if two apps need different output devices.
7. Use mute-all as a temporary quiet state, then restore when the presentation is over.
8. Repeat the test inside the meeting, recording, or screen-share mode you will actually use.

Sources checked

• TeenySound claims were checked against the TeenySound homepage and local Swift source for per-app sliders, app mute, mute-all, restore-all, output routing, device-specific volume memory, shortcuts, and permission handling.
• Apple Support: Change the sound output settings on Mac.
• Apple Support: Change Sound settings on Mac.
• Apple Developer Documentation: Capturing system audio with Core Audio taps.

Common questions

What Mac audio settings should I check before a presentation?

Check the output device, output volume, alert volume, app-specific volumes, mute state, and whether any browser tab or app can play sound during the presentation.

Should I use system mute or per-app mute before presenting?

Use system mute when the whole output should go silent. Use per-app mute when you need the presentation app or browser audible while other apps stay quiet.

Can TeenySound help with presentation audio?

Yes. TeenySound can show apps that are producing audio, adjust per-app volume, mute apps, mute all controlled apps, restore prior levels, and route apps to selected output devices.