# SystemUIServer, the process that owns the right end of the menu bar

> The process behind the right end of the menu bar and every screenshot shortcut. Measured: 3.6 MB of memory, half a second of CPU a day, runs as you, and a folder of menu extras from Macs that no longer exist.

Source: https://www.ribbonmac.com/guides/systemuiserver-mac · Updated 2026-11-19

You met this one before you ever opened Activity Monitor. Every time a screenshot failed and a dialog apologised, every time a menu bar icon went missing and came back after a restart, the process doing the talking was SystemUIServer. It just never signed its work.

This page is a measurement of it on a Mac running macOS 27.0.1 with 29 and a half days of uptime. Every fact below was read off the system, nothing installed, nothing killed.

## Two sentences of documentation, since 2018

The manual page, read verbatim:

```
NAME
     SystemUIServer - Presents status items in the upper right of
     menu bar

DESCRIPTION
     SystemUIServer is a system service which presents status items
     in your menu bar.

     There are no options for SystemUIServer, and users should not
     run SystemUIServer manually.

macOS                          July 4, 2018                   SystemUIServer(8)
```

One line of job description and one line of please do not touch, last edited in July 2018 and shipped unchanged through nine major macOS versions since. For a process that appears in every Activity Monitor window on every Mac ever sold, that is the entire official literature.

## A daemon's name on an app's birth certificate

launchd's own report on the process, read with launchctl print gui/$(id -u)/com.apple.SystemUIServer.agent, says things a daemon should not say. The spawn type is App. The state is running, active count 8, pid 1648, and the runs counter reads 1: alive since login, 29 days ago, never exited, never restarted. It has forked 69 child processes in that time, roughly two a day, and its environment arrives with a rate limiter, OSLogRateLimit 64, as if launchd already knows this one could talk too much if allowed.

The split from real daemons is the story. The Mac UI stack has layers: WindowServer composites every pixel, the Dock owns the bottom edge, and this process owns the right end of the bar, the status area, where items from different apps all live side by side. Its binary carries the classes for exactly that job, NSMenuExtraController and NSStatusItemDelegate, read straight out of its symbol table. It is an app that behaves like furniture. The rest of the family lives in the same CoreServices folder, and the biggest piece is [loginwindow](https://www.ribbonmac.com/guides/loginwindow-mac), which draws the sign in screen and then stays for the whole session as the registrar of everything that opens.

## The screenshot machine

Here is the part the search results are really about. The launch file registers six Mach services, and one of them is named com.apple.systemuiserver.screencapture. Not screen sharing, not monitoring. Screencapture, the exact name of the /usr/sbin/screencapture tool, whose path also appears inside the binary.

The binary's own strings narrate a capture lifecycle in plain English: Already started screencapture. Finished screencapture. No screencapture to stop. The attempt to take a screen capture has failed. Your screen recording can't be saved. And its resources folder carries ScreenCapture.loctable, the translated text of every failure dialog a screenshot can produce. Read in English:

```
"Screenshots are not allowed."
"Screen grabs are unavailable during DVD playback."
"Please quit DVD Player first."
"Error saving recording."
"Failure to write image data."
"You dont have permission to save files in the location
 where screenshots are stored."
```

That last one is quoted exactly. The key really is missing its apostrophe, and has been for years; the rendered dialog gets a corrected copy. The DVD line is even better: macOS 27 cannot play DVDs, yet the screenshot flow still politely asks you to quit DVD Player first.

So when Command-Shift-3 fires, this process is in the path: the shortcut lands, the capture service it hosts runs, and if the save fails, the apology on screen came from this exact table. The frame grabbing underneath belongs to other processes; replayd, which this series measured on its own page, takes the frame, and the screen recording permission is a different daemon's database. SystemUIServer is the front desk of the operation.

## The museum drawer

The deepest cut is Extras.plist, the file that registers which menu extras exist. Twelve are listed. Nine bundles actually exist in the Menu Extras folder. Read both together:

```
on disk:   AirPort, DwellControl, Eject, ExpressCard,
           PPP, PPPoE, SafeEjectGPUExtra, TimeMachine, VPN
registered but gone: RemoteDesktop, WWAN, iChat, Ink, IrDA,
           Script Menu
```

PPP is dial-up. PPPoE is DSL over Ethernet. WWAN is a 3G data card. IrDA is infrared beaming, a PowerBook feature from the 1990s. ExpressCard is an expansion slot last seen in a 2012 MacBook Pro. Ink is handwriting recognition. Five of the twelve registered items do not exist on disk anymore, and the registrations still carry their era's engineering: PPP only loads if a function named _pppCanLoad answers yes.

The same drawer holds BundleIDMapper.plist, which still maps numeric IDs to com.apple.iDVD, com.apple.BlurayPlayer and com.apple.iChat, and the Mach service named com.apple.ipodserver, registered and waiting for an iPod that will never dock. There is also SUISVisualIntelligenceAvailability, a class from 2026, proof the drawer is still being added to at the other end. None of the fossils load at startup. Keeping them costs nothing, and deleting them is impossible on a sealed volume, so they ride along, a changelog you can plutil.

## What it costs

The bill for owning the right end of the menu bar for a month: 17.01 seconds of processor time across 29 days and 14 hours. About half a second a day. That is cheaper than the iPhone cable daemon usbmuxd, cheaper than the phone call daemon CommCenter, cheaper than anything else measured in this series. In a 20 minute log window it wrote zero lines. The log stream did not merely go quiet, it went empty.

Memory matches. Resident size is 3,648 KB, under four megabytes, smaller than a single website tab, for a process that draws part of every Mac screen. The virtual size is the familiar 466 GB of reserved address space that 64-bit processes on this platform carry around, and it means the same thing it always does: nothing. The old advice about editing its defaults to fix menu bar items has gone quiet too, because defaults read com.apple.systemuiserver on this machine returns exactly two keys, and the menuExtras list that a decade of forum posts told you to rewrite is simply no longer there. The menu bar moved on. The process stayed.

## See for yourself

Every fact above came from read only commands:

```
ps -p $(pgrep -x SystemUIServer) -o pid,user,etime,rss,vsz,time
man SystemUIServer
plutil -p /System/Library/LaunchAgents/com.apple.systemuiserver.plist
launchctl print gui/$(id -u)/com.apple.SystemUIServer.agent
plutil -p /System/Library/CoreServices/SystemUIServer.app/Contents/Resources/Extras.plist
ls /System/Library/CoreServices/Menu\ Extras/
plutil -p /System/Library/CoreServices/SystemUIServer.app/Contents/Resources/ScreenCapture.loctable
log show --predicate 'process == "SystemUIServer"' --last 20m
```

Run the log line and expect silence. The stranger that owns half your menu bar, every screenshot dialog you have ever dismissed and a drawer of dead hardware icons turns out to be the quietest process on the machine.

## FAQ

### What is SystemUIServer on my Mac?

It is the process that has always owned the right end of the menu bar. Its manual page, one of the shortest in this series, gives it a single line of work: presents status items in the upper right of menu bar. The clock area, the status icons, the bits of menu bar that are not an app's own menus, those belong to SystemUIServer. On the measured Mac it runs as your own account, not root, out of /System/Library/CoreServices/SystemUIServer.app, and it has been alive without a single restart for the entire 29 day uptime. The searches that find this page, systemuiserver mac, systemuiserver process, systemuiserver activity monitor, are people who met the name in Activity Monitor and found nobody had ever introduced it.

### Why is SystemUIServer using high CPU or not responding?

Because something on the right end of the menu bar is being drawn, animated or asked a question. Unlike the daemons in this series it is a user interface process, spawned as an app, so its CPU column tracks visible work: menus opening, status items updating, a screenshot being taken. The measurement says how rare that is: 17 seconds of processor time across 29 and a half days, about half a second a day, the cheapest process measured in this entire series. When it does hang, the classic remedy from two decades of Mac troubleshooting still works: killall SystemUIServer in Terminal. The menu bar blanks for a moment and relaunches, because its launch file's KeepAlive rule brings it straight back. Nothing is lost and nothing else on the Mac is touched.

### Is SystemUIServer recording my screen?

Not secretly, no. The confusion is understandable because the name genuinely appears next to screen capture machinery: the process hosts a Mach service literally named com.apple.systemuiserver.screencapture, and its resources carry every error dialog a failed screenshot can produce. That is the screenshot shortcut flow, the one you fire with Command-Shift-3. The frame grabbing underneath is done by other processes, replayd among them, and the permission to record is a different daemon's database. Forum threads that name SystemUIServer in screen sharing warnings mostly date from older macOS versions, when the sharing indicators were menu extras hosted by this very process. On a current Mac the sharing indicator is drawn by the Control Center status area, and the Menu Extras folder it reads today contains no screen sharing item at all.

### Can I quit or disable SystemUIServer?

You can quit it and you cannot disable it. killall SystemUIServer makes the menu bar vanish for a beat and return, which is precisely what the KeepAlive entry in its launch file is for: relaunch on anything but a clean exit. launchd also holds it to a minimum runtime of 10 seconds, so a crash loop is stopped by design. The launch file itself sits in /System/Library/LaunchAgents on the sealed system volume, which means there is no supported way to remove it, and no reason to: at 3.6 MB of memory and half a second of CPU a day, it is cheaper to leave running than to think about.

### Is SystemUIServer a virus or malware?

No. The genuine binary lives at /System/Library/CoreServices/SystemUIServer.app on the sealed, read-only system volume, 1.3 MB, owned by root, and signed by Apple as part of the OS. It runs as your user account, which is worth knowing: a process with this name running from a downloads folder or a browser profile would be a costume, and the path in Activity Monitor's Sample Process dialog is how you check. There is no malware family that impersonates this name in the wild, which fits a process whose visible worst symptom is a menu bar that needs a nudge.

### Why does SystemUIServer still have files for dial-up modems and infrared in 2026?

Because Apple ships its history. The configuration file that registers menu extras, Extras.plist, still lists PPP.menu and PPPoE.menu, the dial-up and DSL modem indicators, alongside WWAN.menu for 3G data cards, IrDA.menu for infrared beaming, iChat.menu, Ink.menu for handwriting recognition and ExpressCard.menu for a slot last seen in a 2012 MacBook Pro. The registration even carries load gates from that era: a menu extra called PPP is only loaded if a function named _pppCanLoad says yes. Five of the twelve registered extras no longer exist on disk at all. None of this loads at startup. It is a museum drawer, and the cost of keeping it is zero.
