MacBook clamshell sound output: prove the audio path
Treat lid close as an audio transition. Verify the selected device and the speaker you can actually hear before changing any app level or route.
The short answer: wait until the external display is stable and the lid is closed. Open macOS Sound settings, select the intended output by name, play one known sound, and confirm the physical destination. Record output volume and whether macOS exposes a volume control. Only then set the real app's volume or route. Repeat the same proof after wake and after reconnecting the desk.
TeenySound is my app, so the bias is clear. Its source watches the current default output device and saves app levels under that device's UID. It can also give an audio-producing app its own level, mute state, or selected outputs. It does not choose the Mac's default output or repair an unavailable speaker path.
This is the TeenySound spoke for the TeenyApps MacBook clamshell mode checklist. If the monitor has not passed its closed-lid test, use the TeenyDisplay guide for MacBook clamshell external monitor setup before diagnosing audio.
Read the closed-lid audio evidence
| Evidence | Owning layer | Next action |
|---|---|---|
| The selected output name is wrong. | macOS Sound settings. | Select the intended device and replay the known sound. |
| The name is right, but sound comes from somewhere else or stays silent. | Physical device, connection, or app-specific output. | Check the monitor, headset, USB, AirPlay, and the source app's own device setting. |
| Every source is too loud or quiet. | Selected output or physical speaker volume. | Set output volume before changing app sliders. |
| One audio-producing app is wrong. | The app, its own player, or TeenySound. | Check the app's level and device setting, then use a per-app level or route if needed. |
| Wake or reconnect changes the output or level. | Transition state. | Repeat the device-name and physical-destination proof before trusting saved levels. |
01Finish the display transition first
Close the lid only after the external display, power, keyboard, and mouse or trackpad work. Wait for the display and dock to settle, then wake and unlock the Mac. Audio evidence collected before that transition describes a different device inventory.
If the monitor disappears or the dock does not reconnect, fix that layer first. The closed-lid monitor evidence guide separates missing displays from mode and monitor-control problems.
Now list the audio hardware that is actually attached: display speakers, a headphone jack, USB audio, Bluetooth, AirPlay, or desk speakers. Do not assume the newest device is the selected one.
02Prove the selected output and physical destination
Open System Settings, Sound, Output. Apple says this list can include internal speakers, display speakers, wired and USB speakers, headphones, AirPlay devices, and other connected outputs. Select the intended device by name.
Play one known local sound and listen at the device itself. Record the selected name, physical destination, output volume, mute state, and whether the volume control is available. Some output devices expose no software volume control, so the speaker or monitor may own the final level.
Apple notes that an app's own volume cannot exceed the selected output volume. If everything is quiet, raise the output layer first. If only the real source app is quiet, move to the app layer.
03Handle the display-speaker edge case
An external display can add its speakers to the available outputs. That does not mean macOS must use them, and a checked name still needs the listening test.
Apple documents a specific case: when headphones or external speakers remain connected, selecting a display's built-in speakers may not persist and the Mac can switch back to the attached audio device. Simplify that path or choose the output again after the lid closes.
If the selected device stays right but a meeting app or player uses another device, check that app's own audio setting. An app-level device choice can disagree with the Mac's default output.
04Move to app audio only after output passes
Start the actual browser, music, meeting, or training source. TeenySound lists apps that are producing audio. Its per-app processing uses Apple's CATap API, so it requires macOS 14.2 or later and the System Audio Recording permission described on the TeenySound homepage.
The source saves normal app volumes by bundle ID under the current default output device UID. When that device changes, it saves the old levels, loads levels for the new UID, applies them to running apps, and clears their mute state.
Use a per-app route only when one source genuinely belongs on a different output. If every app should move together, macOS Sound output is the simpler and correct layer.
05Test two transitions before saving the desk
Run the proof after lid close and wake, then again after disconnecting and reconnecting the dock or display. Each pass should preserve the intended output name, physical destination, output volume, real app level, and any deliberate app route.
For explicit app routes, TeenySound stores selected output device UIDs and separate per-device levels. For mute-all, its source keeps pre-mute app levels so restore can return them instead of setting every app to one value.
If a transition fails, remove special app routing and return to one macOS default output. Prove the simple path, then add one app-level exception and test again.
Clamshell audio acceptance checklist
- Stabilize the external display, power, keyboard, and pointer.
- Close the lid, wait, then wake and unlock the Mac.
- Open Sound settings and select the intended output by name.
- Play one known sound and confirm the physical destination.
- Record output volume, mute state, and whether software volume is available.
- Start the real source app and check any device setting inside it.
- Set a per-app level or route only if the default output already passes.
- Disconnect and reconnect the desk, then repeat the proof.
- Remove special routing if the simple default-output path fails.
FAQ
How do I set sound output in MacBook clamshell mode?
After the external display is stable, close the lid, open Sound settings, and select the intended output by name. Play one known sound, confirm its physical destination, then set output volume before any per-app level or route.
Why did audio switch to monitor speakers in clamshell mode?
An external display can add its speakers to the available outputs. Apple also notes that display speakers may not stay selected while headphones or external speakers remain connected, so verify the accepted output after lid close, wake, and reconnect.
Can TeenySound remember different app volumes for clamshell mode?
Yes. TeenySound saves app levels under the current default output device and can retain per-app routes and per-device levels. It works on audio-producing apps after macOS has selected a valid output; it does not choose the Mac's default output.
Sources checked
- TeenySound claims were checked against the TeenySound homepage and local Swift source for
AudioDeviceManager,PerAppAudioManager,PlaythroughEngine, andMixerViewModel, including default-output listeners, device-UID volume storage, CATap requirements, app routing, mute-all, and restore. - Apple Support: Change the sound output settings on Mac.
- Apple Support: If your Mac switches to a different audio device.
Keep clamshell audio predictable.
teenysound is a Mac menu bar app for per-app volume, app mute, mute-all, restore, output routing, device-specific volume, and quick audio control. $9.99 once, 3-day free trial.