Mac screen recording audio levels: capture vs playback

The short answer: select the microphone and system-audio tracks in the recorder, watch its meter when one is available, and record a 30-second test. Set local playback only as loud as you need for monitoring. Play the saved file before changing any control based on what you heard live.

Apple's current Screenshot and QuickTime instructions document microphone selection, not a built-in system-audio switch. A third-party recorder can use Apple's ScreenCaptureKit to capture screen and audio, but that app decides the track, mix, and level written to the file.

TeenySound works on the monitored output path. It gives audio-producing apps 0-to-100-percent sliders, mute, mute-all with restore, and per-app output routing. Its source uses Core Audio taps and private aggregate devices to process and replay app audio; it does not write audio to disk. That makes it useful for comfortable monitoring, not proof of a recorder's captured level.

This is the TeenySound spoke for the TeenyApps hub Mac screen recording setup: capture, paste, and playback. Pair it with Mac clipboard manager for screen recording when the take also depends on a safe paste sequence.

Match each symptom to the owning control

01State which tracks the file should contain

Choose one intended result before touching levels: microphone only, system audio only, both as separate tracks, both as a mixed track, or silence. Then select those sources in the recorder.

Apple's built-in recording paths expose a microphone choice. If you need app or system audio, use a recorder that exposes that track. macOS can grant an app access to both screen and system audio or to system audio only, but permission alone does not select a track inside the recorder.

For a live screen share, use the separate Mac app audio before screen sharing guide. A meeting app decides what remote viewers receive. This page is about audio written into a saved recording.

02Use the recorder meter as the first level check

If the recorder provides separate meters, speak and play the exact source app while watching them. Avoid obvious clipping, confirm that the intended track moves, and confirm that an excluded track stays still. A meter proves signal presence, not final intelligibility.

If the recorder has no useful meter, make the first test shorter. Record voice, a quiet source moment, a loud source moment, and five seconds of intended silence. This exposes missing tracks, overload, background noise, and unexpected app audio quickly.

Fix a bad microphone at the recorder, macOS input setting, or microphone hardware. Fix a missing system-audio track in the recorder and its permission. Those are capture-path problems.

03Set a separate monitoring level

Open Sound settings, choose the actual output device, and set a comfortable local volume. If a monitor, dock, AirPlay target, or headphones took over output, correct the route before adjusting individual apps.

Use the source app's own control when it is clear. Use TeenySound when one app needs a different monitored level or output route from the rest of the Mac. The app appears when it produces audio; its slider, mute state, and route apply to TeenySound's playthrough path.

A monitored level is not a target loudness for the saved file. A recorder may capture before or after another processing point. TeenySound cannot promise that its 50-percent slider becomes a particular recorded level.

For monitor-output surprises, use Mac audio switches to monitor speakers. For a live class, use Mac workshop audio checklist.

04Keep capture silence and monitoring silence distinct

Focus, quitting an app, or disabling its own notification sound is the strongest way to keep irrelevant audio out. A local mute can make an app inaudible to you without proving that the recorder excluded it.

TeenySound's per-app mute and Option-Shift-A mute-all shortcut are useful for the monitored output. Mute-all stores prior app values and restores them on the next toggle. Its Option-Shift-S shortcut opens the mixer.

After muting locally, watch the recorder meter or make a saved test while the muted app produces a harmless sound. If that sound remains in the file, exclude it at the source or recorder. Do not treat quiet headphones as capture evidence.

05Judge the saved file, then change one path

Play the test from its real save location. Check every intended track, voice clarity, source clarity, the balance between tracks, silence where expected, and any notification or app sound that should be absent.

Change one owning control at a time. Use recorder gain or input hardware for the microphone. Use recorder track level or source capture control for saved system audio. Use Sound settings or TeenySound for comfortable local playback.

Repeat the same 30-second script after each change. A consistent test makes it clear whether the capture changed or only the monitoring path changed.

Screen recording audio proof

1. Write down the intended microphone and system-audio tracks.
2. Select those tracks in the recorder and confirm its macOS permission.
3. Watch the recorder meter while speaking and playing the exact source.
4. Choose a comfortable Mac output and monitored app level.
5. Test local mutes against the recorder meter instead of assuming capture silence.
6. Record voice, quiet source, loud source, and intended silence for 30 seconds.
7. Play the saved file and inspect every intended and excluded track.
8. Fix capture in the recorder; fix monitoring in Sound settings or TeenySound.

Common questions

How do I set audio levels before recording my Mac screen?

Choose the microphone and system-audio tracks in the recorder, use its meter when available, set a comfortable local monitoring level, then record and play a saved test file. The saved file is the final evidence.

Does TeenySound set the system-audio level in a screen recording?

Not reliably. TeenySound changes the app audio you monitor through Mac outputs. A recorder can capture audio at another point in the signal path, so use the recorder's track controls and the saved file to judge captured level.

Can Apple's built-in screen recorder capture system audio?

Apple's current Screenshot and QuickTime instructions document microphone selection, not a system-audio switch. For app or system audio, use a recorder that exposes that capture track and confirm its permission and saved result.

Sources checked

• TeenySound claims were checked against the TeenySound homepage and local Swift source for 0-to-100-percent app sliders, mute and restore, output routing, device-specific volume memory, shortcuts, Core Audio taps, private aggregate devices, mutedWhenTapped playthrough, audio-only permission, and macOS 14.2 requirements.
• Apple Support: How to record the screen on Mac, published April 9, 2026.
• Apple Support: Control access to screen and system audio recording on Mac.
• Apple Support: Change the sound output settings on Mac.
• Apple Developer Documentation: ScreenCaptureKit.