What is configd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
configd is the macOS System Configuration daemon: it gives each network interface its address, picks the primary connection, and applies DNS and proxy settings. It uses CPU when the network changes, for example when Wi-Fi reconnects, a VPN starts or a dock with Ethernet is plugged in. It is essential and cannot be stopped.
configd at a glance
| configd | |
|---|---|
| Made by | Apple (part of macOS, System Configuration) |
| Type | System daemon |
| Location | /usr/libexec/configd |
| Runs as | root |
| Started by | launchd job com.apple.configd |
| Can you quit it? | No. launchd keeps it running, and networking stops working while it is gone. |
What is configd?
The man page describes configd as responsible for many configuration aspects of the local system. It keeps a live store of the current and desired state, notifies apps when that state changes, and hosts configuration agents as loadable bundles in /System/Library/SystemConfiguration/.
Most of those agents handle networking. On macOS 26 they include InterfaceNamer (names interfaces such as en0), IPConfiguration (DHCP and IPv6 addresses), IPMonitor (the primary service, default route, DNS and proxies), EAPOLController (802.1X login on enterprise Wi-Fi), PPPController and CaptiveNetworkSupport. Apps read configd's data through the SystemConfiguration framework, and the scutil command reads it in Terminal.
Is configd safe?
Yes. configd is a core part of macOS, lives in /usr/libexec on the read-only system volume and is started by launchd at boot with KeepAlive set, so it always runs as root.
Why does configd use so much CPU?
- Network connections coming and going. Every time Wi-Fi drops and rejoins, configd requests a new address, recomputes routes and DNS, and tells every interested app. A weak signal that keeps reconnecting keeps it busy.
- VPNs and many interfaces. VPNs, virtual machines, Docker and USB or Thunderbolt network adapters each add interfaces and services. Each change makes configd recompute which service is primary.
- Apps watching network state. Apps that ask configd for network details very often, or register many change notifications, add to its work. This shows as configd CPU even though another app is asking.
- Sleep and wake. On wake, interfaces come back one by one and configd re-applies the whole configuration.
How much CPU is normal for configd?
Typical use is 0 to 1% CPU with short bursts during network changes. A burst of a few seconds after wake or when joining Wi-Fi is normal.
configd above 10% CPU for minutes at a time is not typical and usually means the network configuration is changing over and over.
How do you stop configd from using so much CPU?
- Check for a flapping connection. Watch the Wi-Fi icon or run
scutil --nwia few times. If the primary interface or address keeps changing, the connection is unstable; move closer to the router or try Ethernet. - Disconnect VPNs and virtual networks. Quit VPN clients, virtual machines and container tools one at a time and watch configd in Activity Monitor.
- Remove unused network services. In System Settings > Network, delete services you no longer use, such as old VPN entries or adapters you no longer own.
- Restart the Mac. If configd stays high on a stable network, restart. Its configuration is rebuilt cleanly at boot.
When should you worry about configd?
Look closer if configd stays above about 10% CPU for a long time on a stable connection, or if the network keeps dropping. Running log show --last 5m --predicate 'process == "configd"' shows what it has been doing.
configd running from any path other than /usr/libexec/configd would not be Apple's.
How do you check configd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type configd in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every configd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'configd' | grep -v grep
How can Thrum help with configd?
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 configd 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 configd
Can I quit configd?
No. launchd keeps it alive, and without it the Mac cannot set up its network connections.
What does scutil show?
scutil --dns shows the DNS setup configd has applied, scutil --nwi shows the active network interfaces, and scutil --proxy shows proxy settings.
Is configd related to mDNSResponder?
Yes. configd decides which DNS servers are active and mDNSResponder uses them to answer lookups.
Sources
- configd(8) man page: run man configd in Terminal
- scutil(8) man page: run man scutil in Terminal