ControlCenter on Mac: the menu bar process, why it uses CPU, and what to do

What ControlCenter does

ControlCenter is a system app at /System/Library/CoreServices/ControlCenter.app that arrived with macOS Big Sur in 2020. Before that, each status icon in the menu bar (Wi-Fi, volume, battery, Bluetooth, Time Machine) was its own small plug-in loaded by SystemUIServer. Apple folded them into one process, gave it the Control Center panel from iOS, and made the menu bar icons shortcuts into the same panel. Apple's user guide describes it as the place to "quickly change settings" like Wi-Fi, Bluetooth, AirDrop, Focus, display brightness and sound, with an Edit Controls option for choosing what appears.

Because it draws so many live things, ControlCenter listens to a lot of the system. It subscribes to Bluetooth state so the icon updates when your headphones connect, to display changes so Screen Mirroring and brightness stay right, to audio so the Sound slider and Now Playing reflect what is playing, to the battery and to Focus. On macOS Ventura and later it also owns the privacy indicators: the orange dot for microphone, green for camera, purple for location, which appear in the menu bar next to Control Center.

All of that is light work when nothing is changing. ControlCenter only redraws when one of its inputs changes or you open a menu, so on a quiet Mac it sits at zero.

What normal looks like

ControlCenter's CPU follows how often the things it displays change and how often you open it. Here is the range people actually see:

Memory is usually 50 to 150 MB and stays flat. On a Mac with an external display and several Bluetooth devices it runs a little higher, which is fine. A slowly growing number over days is the sign of a leak in a menu bar item, and a quit fixes it until the next time.

Why ControlCenter is using CPU right now

ControlCenter does not get busy on its own. It redraws because something it shows keeps changing, and in practice the something is one of these:

1. A Bluetooth device that keeps connecting and dropping. Headphones at the edge of range, a mouse with a dying battery, or a device paired to two Macs that fight over it. Every connect and drop updates the Bluetooth menu and the Sound menu. Our bluetoothd page covers the daemon on the other side of that.
2. A display that keeps being detected. A loose cable, a dock that renegotiates, or a monitor that sleeps and wakes repeatedly. Each event rebuilds the Display and Screen Mirroring menus and often shows up as WindowServer load too.
3. Now Playing fed by a stuck app. A browser tab or media app that reports a track change many times a second. Pausing or quitting that app is the test.
4. A third-party menu bar app interacting badly. Menu bar managers and some utilities poke at the menu bar constantly. Quitting them one at a time is the test.
5. The first minutes after login or an update. Every item initializes and queries its source at once. This ends on its own.

What it is not: malware. ControlCenter is an Apple app on every Mac since Big Sur, and no cleaner utility has anything to do with it.

Is it safe to quit ControlCenter?

Yes. ControlCenter is one of the safest processes to quit on a Mac. Select it in Activity Monitor, click the stop button and choose Quit. The right side of the menu bar disappears for about a second and then comes back, because launchd relaunches it immediately. You lose nothing: no settings, no connections, no open windows. People do this routinely when the menu bar freezes or the clock stops updating.

What a quit does not do is fix the cause. If a flapping device or a stuck app was driving the CPU, the fresh ControlCenter picks up the same stream of changes and climbs again within minutes. Treat the quit as a reset and a diagnostic: if it stays calm afterwards, it was a one-off glitch; if it climbs again, go find the device or app.

Type any process name above to see which ones relaunch harmlessly like this and which you should leave alone.

What to do, in order

1. Quit ControlCenter once

   In Activity Monitor, select ControlCenter, click the stop button in the toolbar and choose Quit. The menu bar items vanish and return in a second. Watch the CPU for five minutes.

2. Turn Bluetooth off for a minute

   If it climbed again, open Control Center and switch Bluetooth off. If ControlCenter calms down, a Bluetooth device was flapping. Turn Bluetooth back on, then charge, re-pair or move the device that was at the edge of range.

3. Reseat the display cable or dock

   If you use an external display, unplug and replug the cable at both ends, or try a different port on the dock. A display that keeps being redetected shows as both ControlCenter and WindowServer load.

4. Pause whatever is playing

   Open Control Center and look at Now Playing. Pause it, or quit the app or browser tab that is feeding it. A media source reporting constant changes is a common cause on Macs that run a music app or a web player all day.

5. Quit third-party menu bar apps one at a time

   Menu bar managers, clipboard tools and status utilities can poke at the menu bar constantly. Quit each from its own menu and watch ControlCenter. Update or remove the one that was responsible.

6. Log out and back in, or restart

   If none of the above found it, log out and in, which restarts every menu bar item and its sources. A full restart is the last step and clears anything lingering from an update.

When to worry

ControlCenter cannot damage anything. The cost of leaving it busy is battery life and a laggy menu bar. Here is how long each state is reasonable:

The clue that identifies the cause is what else moves at the same moment: bluetoothd, WindowServer, or a media app. Safe to Quit records that alongside each process over hours, which is usually enough to name the device without trial and error.