Mac menu bar keyboard shortcuts: what deserves a key?

Start with macOS commands, then add one global launcher for a utility you use across apps. Reserve media-key interception and Shortcuts workflows for jobs a normal app shortcut cannot handle.

Published May 11, 2026 Updated July 20, 2026 8 min read By John Sciacchitano

Use a Mac menu bar keyboard shortcut only when the command needs to work while another app is active. If the command already appears in the frontmost app's menu, use its built-in shortcut or macOS App Shortcuts. If one utility needs to open from anywhere, give it one global hotkey. If several actions need to run together, use the Shortcuts app.

This guide covers how to choose the trigger. It does not try to list every Mac keyboard shortcut. Apple already maintains that reference, and the exact keys can vary with keyboard layout and app menus.

Disclosure: I build TeenyApps, including TeenyTool and TeenyDisplay. Their implementations are useful examples here, but the built-in macOS route should win whenever it already does the job.

Choose the smallest shortcut layer that works

Job Best first trigger Why
Run a command in the current app Built-in command or macOS App Shortcuts The app menu stays the source of truth.
Open one menu bar utility from anywhere One registered global hotkey It works across apps without building a workflow.
Open one exact tool from anywhere Per-tool hotkey, after the launcher proves useful It saves a second selection for truly frequent tools.
Adjust display brightness repeatedly Brightness keys or custom brightness hotkeys The control is continuous and the result is visible.
Apply a named desk state Shortcuts workflow or app URL command One trigger can represent several related settings.

Use macOS shortcuts for foreground app commands

Apple shows keyboard shortcuts beside commands in Mac app menus. When an app exposes the command you need, that menu is the first place to look. macOS also lets you create an App Shortcut for a menu command that does not already have a convenient key combination.

That route fits actions such as opening a specific editor panel, exporting a document, or running a menu command in one app. It does not create a system-wide launcher for a menu bar utility. App Shortcuts depend on the app's menu command and the app being the target.

Apple also warns that a shortcut assigned to an existing command or another app may not work. Check System Settings > Keyboard > Keyboard Shortcuts for conflict warnings, then check the app menu to confirm which combination macOS sees for that command.

Give a utility one global launcher first

A global hotkey is useful when a menu bar utility should open over whichever app you are using. Start with one launcher. It is easier to remember one entry point than a separate combination for every tool in the app.

TeenyTool follows this pattern. Its source supports a configurable Open / Close App shortcut and optional shortcuts for individual tools. Both use registered system-wide hotkeys, and the settings screen reports a failed registration when macOS or another app already owns the combination.

The source starts with no default global shortcut. That is the right boundary for a configurable utility: the user chooses a combination after checking the shortcuts already in use. The detailed setup is in Mac utility keyboard shortcuts.

Add direct tool shortcuts only after the launcher

A direct shortcut should open one action whose name and result remain obvious weeks later. JSON Formatter, URL Codec, a timer, or a color checker can qualify if you use the same tool every day. A tool you open once a month should stay searchable or clickable.

TeenyTool lets users favorite up to 12 tools and assign per-tool hotkeys. Favorites reduce the search step without consuming another keyboard combination. That makes a useful progression: open the utility with one key, favorite the recurring tools, then add a direct hotkey only for the one or two that still interrupt work.

If a direct shortcut fails to register, do not keep pressing it and guessing. Clear it, choose a combination with Command, Option, or Control, and avoid keys already owned by Spotlight, screenshots, app switching, browser tabs, or your editor.

Separate global hotkeys from media-key interception

Not every system-wide key works through the same macOS mechanism. A normal registered hotkey can work without Input Monitoring or Accessibility permission. Intercepting the brightness or volume media keys uses a different path because the app must catch hardware key events before macOS handles them.

TeenyDisplay makes that difference visible. Its custom brightness, contrast, and volume shortcuts use registered hotkeys. Its option to intercept F1/F2 brightness keys and volume keys uses an event tap and requires Accessibility access.

Choose custom hotkeys when you want explicit combinations that do not replace the normal media keys. Choose interception when you want the physical brightness keys to control external displays and you accept the permission. The refreshed external monitor brightness automation guide maps those choices to Shortcuts and URL commands.

Use Shortcuts when one trigger has several steps

Apple's Shortcuts app can expose a workflow through a keyboard shortcut, the menu bar, Control Center, Quick Actions, Services, or the share sheet. That makes it the better layer when one trigger needs to run several actions or pass selected content into a workflow.

Shortcuts can also open another app's URL scheme. TeenyDisplay exposes commands such as teenydisplay://brightness?display=external&delta=-10 and teenydisplay://preset?name=Work. A shortcut can open one of those URLs, then continue with other actions if needed.

Keep the app command narrow and keep the workflow logic in Shortcuts. A URL scheme is a clean entry point for setting one value or applying one named preset. It is a poor place to hide branching, retries, or private text that another launcher may record in its history.

A five-minute setup test

  1. Write down the exact action and how often it interrupts your work.
  2. Check the current app's menus and macOS Keyboard Shortcuts settings first.
  3. If the action must work across apps, assign one global utility launcher.
  4. Run the shortcut from three different apps and confirm the same result each time.
  5. Remove the shortcut if you forget it or if a conflict appears during normal work.

The last step matters. A shortcut map is not valuable because it is large. It is valuable when each key still has an obvious job and works from the context where you need it.

Common questions

Should a menu bar app use a global keyboard shortcut?

Use a global shortcut when the app or command must open while another app is active. Keep normal foreground-app commands in that app's menus or macOS App Shortcuts settings.

Do global shortcuts need Input Monitoring or Accessibility access?

Not always. A standard registered hotkey can work system-wide without those permissions. Intercepting hardware media keys is different and can require Accessibility access.

When should I use the Shortcuts app instead of one hotkey?

Use Shortcuts when one trigger needs to run several actions, pass content between apps, or call an app's URL scheme. Use a direct hotkey for one frequent action with an obvious result.

Sources checked

Assign one key to one clear job.

TeenyApps are native Mac menu bar utilities for display controls, local tools, colors, screenshots, clipboard history, mic mute, sound, stats, shelves, and screen time.