How to mute your mic with a keyboard shortcut on Mac

Take any Mac off the shelf in 2026 and you get keys for brightness, volume, screen lock, dictation, Mission Control, even Siri. There is no mic mute key. There has never been one. Apple has been shipping Macs with built-in microphones for over twenty years and a system-wide mute control has not appeared in any version of macOS, including the most recent.

So every conferencing app rolls its own. Zoom uses ⌘⇧A. Slack huddles use ⌘⇧Space. Microsoft Teams uses ⌘⇧M when in focus and an unreliable global hotkey when not. FaceTime hides mute behind a UI button with no shortcut at all. If you sit through five meetings on three platforms, the muscle memory will not stick.

This guide walks through the three real ways to add a working Mac-wide mic mute hotkey, what each does at the system level, and the tradeoffs between them.

Why this is harder than it sounds

The Mac has two ways to silence a microphone, and only one of them is reliable.

The first is the per-app mute that conferencing software ships. Zoom's mute is a UI flag that tells the Zoom client to stop sending audio. The microphone itself is still capturing sound, the OS is still routing audio to Zoom, and Zoom is still receiving samples and discarding them. If you switch apps, Zoom's mute does not apply. If you crash Zoom, Zoom's mute does not apply. If a different app starts using the mic, it gets a hot mic regardless of Zoom's state.

The second is the Core Audio mute property on the input device itself. macOS exposes this through the kAudioDevicePropertyMute selector on every input device that supports it, which is most modern microphones. Toggle that property and the entire OS sees zero audio coming from the device. Every app that uses the mic, every recording session, every voice assistant. All of them get silence at the same time.

The right kind of Mac-wide mute hotkey changes the second one. The wrong kind tries to broadcast a fake keystroke to whichever conferencing app happens to be open and gets it wrong about a third of the time.

Option 1, a small menu bar app that drives Core Audio

The clean fix is a tiny app that registers a global hotkey, listens for the keypress, and toggles the mute property on whatever input device is currently selected as your default. The whole interaction is one keypress, one Core Audio call, done.

I ship one of these. teenymute is $4.99 once with a 3-day free trial. Native Swift, sandboxed, runs on macOS 14 Sonoma and later. The hotkey is registered through Carbon's RegisterEventHotKey API, which is the older but still supported way to register global shortcuts on macOS. The benefit of going through Carbon instead of NSEvent monitors is that Carbon hotkeys work without Accessibility permission, while NSEvent global monitors require it. Most of the older Mac mute utilities use NSEvent because it is easier, then ask the user to grant Accessibility permission to a tiny app, which is a small but real privacy ask. teenymute does not need it.

Push-to-talk does need a different permission. To detect when you release a key (rather than press it), the app has to monitor input events globally, which on modern macOS means Input Monitoring. teenymute only asks for that if you turn push-to-talk on. The default toggle mode does not. For the permission-by-permission version, read Mac mic mute app permissions: what to allow.

The other free options in this category are MicMute by Pareto and MuteKey, both open source. They use the same Core Audio approach and reach the same end state. The reason to pay for the alternative is the polish around it, not the core functionality.

Option 2, a Shortcut wired to a global hotkey

If you want a free path that does not involve installing another app, macOS Shortcuts can call the same Core Audio APIs through the Set Input Volume action. Open Shortcuts.app, create a new shortcut, add Set Input Volume with the value 0 to mute, save it. In System Settings, Keyboard, Shortcuts, App Shortcuts, give that Shortcut a global keyboard combination like ⌥⇧M. Repeat with the value 100 (or whatever your normal level is) for the unmute side. You can fold both into a single shortcut with an If branch that toggles based on the current value.

This works. Two real downsides. The Shortcuts dispatcher takes a noticeable fraction of a second between keypress and mute, sometimes long enough that you miss the window where you wanted to be muted. And you cannot show a HUD or menu bar indicator from the Shortcuts approach, so you never get visual confirmation of your current state. You will press the hotkey twice when you meant to press it once, and end up unmuted in a meeting that you thought you were muted in. That is the muscle memory cost.

For people who only need to mute occasionally, the Shortcuts route is fine and free. For people who mute and unmute several times a meeting, the latency adds up.

Option 3, the per-app shortcut you already have

If your day is one app, just use that app's hotkey and configure its global-shortcut option if it has one. Zoom calls this Enable global shortcut in its keyboard preferences. When enabled, Zoom's ⌘⇧A works even when Zoom is not the foreground app.

Slack does not offer a global mute hotkey for huddles. Microsoft Teams does, but the implementation is buggy, and it has been buggy for years. FaceTime has no shortcut at all. So this option works only if you can promise to never mix tools, and most people who do calls for a living cannot promise that.

What system-wide actually buys you

People sometimes ask whether a Core Audio mute is overkill compared to the per-app version. A few things that the system-level mute gives you that the per-app one does not.

One key for every app. Zoom in the morning, Google Meet at noon, Teams in the afternoon, a browser call at the end of the day. Same hotkey across all of them. No more accidentally pressing Zoom's shortcut while another app is in focus. The focused version of this workflow is Mute Mac microphone across Zoom, Meet, Teams.

Belt and suspenders for privacy. If you have ever wondered whether some piece of software is listening when you did not ask it to, a Core Audio mute removes the doubt. The mic is electrically muted. Even apps that capture without showing UI cannot get audio.

Hardware indicator on supported Macs. Several MacBook models light up an orange dot in the FaceTime camera area when the mic is being captured. A Core Audio mute makes that dot go dark. Per-app mutes do not.

Reliability across crashes. If your conferencing app freezes mid-meeting and the mute UI is unresponsive, the OS-level mute still works. You can still kill audio.

Picking your hotkey

The chord you bind matters. Avoid anything that collides with system shortcuts (most ⌘-based combinations are taken). Avoid anything a conferencing app already uses, otherwise you will fire two mutes that fight each other. The combinations that work well in practice:

• ⌥⇧M. Common, easy to find blind, no system collision.
• ⌃⇧M. Same idea, different finger position.
• F19, on full-size keyboards. A single key, hardest to misfire.
• A Stream Deck button or Elgato XLR mute switch. Worth it if you stream or podcast.

Stay away from ⌘M (system Minimize) and ⌘⇧M (used by Teams when foregrounded). These will produce confusing dual behavior.

Toggle vs push-to-talk

Toggle is the right default. Press once to mute, press again to unmute. It matches how most people use mute in meetings: muted by default, unmuted when speaking, muted again when done. The cognitive load is one key for one state change.

Push-to-talk is better for a narrower set of use cases. Streaming when there is keyboard noise. Recording a podcast. Gaming with friends in a noisy environment. The trick is that holding a key for an entire sentence trains your hand into a specific posture and any drift unmutes you mid-thought. Most people who try push-to-talk for general meetings drop it within a week. The focused version is push to talk on Mac: meeting apps vs system mute.

If you want both, both teenymute and MicMute let you switch in settings. The hotkey is the same. The behavior is what changes.

Common questions

Does it work with AirPods?

Yes. AirPods, Beats Studio, any Bluetooth headset with a mic. The Core Audio mute property is per device. Whatever device is currently the system input, that is what gets muted.

What about USB and XLR microphones?

Most USB mics support the Core Audio mute property directly. A few cheaper ones do not, in which case the mute hotkey falls back to setting input volume to 0, which has the same audible effect (silence) but does not light up some apps' "mute" indicator. XLR mics route through an audio interface, and the same rule applies to the interface.

Does it know which mic I am using right now?

It uses whatever macOS has selected as the default input. If you switch from internal to AirPods mid-meeting, the mute follows. teenymute watches Core Audio's default-device-changed notification and re-arms automatically.

Will it interfere with Zoom's mute UI?

Zoom shows its own mute icon based on its own state. With a Core Audio mute applied, Zoom may still show "unmuted" but no audio reaches the call. The discrepancy can be confusing for the first few meetings. Most people leave Zoom's mute as on by default and use the system mute as the unmute, which keeps both UIs in agreement.

Does the hardware mic indicator light up?

On Macs with the orange capture indicator, the light tracks Core Audio capture state, not per-app mute state. A system mute turns the dot off. A Zoom mute leaves the dot on. This is one of the underrated reasons to use a real Core Audio mute.

The focused guide is Mac microphone indicator vs mute button, which explains why the orange dot, app mute, and system mute can disagree.

The bottom line

The thing you want is one keypress that silences the microphone everywhere, regardless of which app is open. The native macOS path is missing. The closest free option is a Shortcuts.app workflow with some latency. The closest paid option is a $4.99 menu bar app, either MicMute (free, open source) or teenymute. They use the same underlying Core Audio call. The difference between them is polish, not capability.

Pick whichever fits your tolerance for installing things. Either way, the result is the muscle memory you wish your Mac shipped with.