What is sysextd, and why is it running on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
sysextd is the macOS daemon that manages system extensions: the modern replacement for kernel extensions, used by VPNs, network filters, security tools and some drivers. It runs when an app installs, updates, activates or removes one, and on Macs that have such extensions it stays around to coordinate them. It is part of macOS and usually idle.
sysextd at a glance
| sysextd | |
|---|---|
| Made by | Apple (part of macOS, SystemExtensions framework) |
| Type | System daemon |
| Location | /System/Library/Frameworks/SystemExtensions.framework/Versions/A/Helpers/sysextd |
| Runs as | root |
| Started by | launchd job com.apple.sysextd |
| Can you quit it? | Not usefully. It starts automatically when system extensions need managing. |
What is sysextd?
A system extension runs outside the kernel but with special privileges, for example to filter network traffic or watch security events. Its man page says sysextd helps manage system extensions in coordination with other daemons, with the extensions' host apps and with the extensions themselves, and that it was introduced in macOS Catalina 10.15.
Installed system extensions and their data live in /Library/SystemExtensions. launchd starts sysextd as root through the com.apple.sysextd job when its services are needed. The systemextensionsctl list command shows every extension it manages.
Is sysextd safe?
Yes. sysextd is inside SystemExtensions.framework on the read-only system volume and signed by Apple. The extensions it manages come from apps you installed, and macOS asks for your approval before a new one is allowed. Review that list if you do not recognize an extension.
Why does sysextd use so much CPU and memory?
- Installing or updating an extension. When a VPN, filter or security app installs or updates its extension, sysextd validates and activates it, which is a short burst of work.
- An extension that fails to activate. If an app keeps asking to activate an extension that is not approved or fails to load, each request gives sysextd more work.
- Several installed extensions. On Macs with several system extensions, sysextd keeps track of their state while it runs.
How much CPU is normal for sysextd?
sysextd should be at or near 0% CPU. Short spikes when you install, update or remove an app with a system extension, or at startup, are expected.
On a Mac with no third-party system extensions it is rarely seen.
How do you see and manage system extensions?
- List system extensions. In Terminal, run
systemextensionsctl list. Each line shows the developer's team ID, bundle ID, name and state. - Review them in System Settings. Open System Settings > General > Login Items & Extensions and scroll to the extension categories, such as Network Extensions, to see and turn off extensions.
- Update the app that owns a failing extension. If sysextd is busy repeatedly, the app whose extension keeps failing is the cause. Update it, or approve its extension if you trust it.
- Remove extensions you no longer use. Uninstall the app with the app's own uninstaller or by moving it to the Trash; macOS then removes its system extension.
When should you worry about sysextd?
Worry about a system extension from a developer you do not recognize. Network and endpoint security extensions can see a lot of what the Mac does.
sysextd with steady CPU for a long time points to an extension stuck in a loop of activation requests.
How do you check sysextd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type sysextd in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every sysextd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'sysextd' | grep -v grep
How can Thrum help with sysextd?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when sysextd is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about sysextd
What is the difference between a system extension and a kernel extension?
Kernel extensions run inside the macOS kernel. System extensions run in user space with specific privileges, so a fault in one is less likely to crash the whole Mac.
Can I remove sysextd?
No. It is part of macOS. You can remove the extensions it manages by removing the apps that installed them.
Sources
- sysextd(8) man page: run man sysextd in Terminal
- systemextensionsctl(8) man page: run man systemextensionsctl in Terminal