configd, the daemon that sets up every network your Mac joins
The daemon that turns your network settings into a working connection: its 13 bundles, the store scutil reads, and why CPU spikes when Wi-Fi changes.
By Chethan Kumar S N · Updated
Every Mac owner meets configd eventually, usually in Activity Monitor on a day when the Wi-Fi has been troublesome, and the name gives nothing away. A lowercase word ending in d, sitting there using memory, owned by root, with no app icon and no obvious reason to exist. The search that follows usually ends on a forum thread that says “system process, leave it alone”, which is correct and entirely unhelpful.
This page is the fuller answer, and it is one of the few processes where Apple’s own documentation actually carries most of the weight. The man page describes the architecture plainly, the launch job names every door other processes knock on, and the daemon keeps its working state in a store you can read yourself with a tool that ships on every Mac. Everything measured here comes from one Mac running macOS 27.0.1, read only, with the daemon left exactly as it was.
What the process is, in one command
The process table answers the first questions in one line:
$ ps -o pid,ppid,user,etime,time,rss -p 423
PID PPID USER ELAPSED TIME RSS
423 1 root 26-00:12:07 57:33.62 9264
Read it left to right. PID 423, a low number, because it was started early in boot. Parent PID 1, which is launchd, the process that starts everything on a Mac and the only parent a system daemon ever has. User root, because configuring network interfaces, which is what this daemon does, is not something an ordinary user account is allowed to do. Elapsed time 26 days, which on this Mac is the same as the uptime, so it has been running since the machine was last booted. CPU time 57 minutes and 34 seconds, which is the headline number for the question people actually ask, and which is covered properly further down. Memory 9,264 KB, or about 9 MB, which is roughly what the daemon and all of its plugins together cost to keep in memory. Small, stable, and boring in the way a system component should be.
The binary is /usr/libexec/configd, 1,971,008 bytes, built for three architectures at once (x86_64 and two variants of arm64e), which is how Apple ships one file that runs on Intel and Apple silicon Macs.
The man page, which unusually says a lot
Most macOS daemon man pages are a sentence or two of boilerplate that ends with advice not to run the thing by hand. configd’s man page is 4,671 bytes of actual documentation, and its description is the clearest statement of what any system daemon does that you will find on a stock Mac:
The configd daemon is responsible for many configuration aspects of the local system. configd maintains data reflecting the desired and current state of the system, provides notifications to applications when this data changes, and hosts a number of configuration agents in the form of loadable bundles.
That one sentence carries the whole architecture, and every part of it is checkable:
- Desired state: what you have asked the network to be. The Wi-Fi network you chose, the manual address you typed, the service order in System Settings.
- Current state: what the network actually is right now. Which interface is up, what address it got, which router answered.
- Notifications: when the current state moves, applications that care hear about it, without polling.
- Loadable bundles: the pieces that do the work, one job each, loaded into the daemon at startup.
The rest of the page names the bundles and, in the FILES section, tells you where the persistent state lives. Both of those claims are tested against this Mac below, and one of them turns out to be understated.
The store, which you can read with a tool you already have
The desired and current state live in what Apple calls the dynamic store, and the window onto it is scutil, a command line tool that ships with every Mac. Ask it to list the store and it prints 160 keys on this machine. They sort into families:
subKey [4] = Setup:
subKey [8] = Setup:/Network/Interface/en0/AirPort
subKey [62] = State:/Network/Global/IPv4
subKey [86] = State:/Network/Interface/en0/IPv6
The split is exactly the man page’s split. Setup: keys are the desired state: the network services you configured, in the order you set, with the settings you gave them. State: keys, 96 of them on this Mac, are the current state: what interface is primary, what address it holds, what the router is. Show the global IPv4 state and the daemon’s whole job compresses into four lines:
$ printf 'show State:/Network/Global/IPv4\nquit\n' | scutil
<dictionary> {
PrimaryInterface : en0
PrimaryService : FB24DFA3-9426-47F1-82EE-29AA0F905E9A
Router : 192.168.1.1
}
That is the current state of this Mac’s connection, written by configd, read back through its own API. (The command, in full: printf 'show State:/Network/Global/IPv4\nquit\n' | scutil, because scutil’s show command lives inside its interactive mode rather than behind a flag.) Other commands read other slices of the same store. scutil --get ComputerName and scutil --get LocalHostName return the names your Mac advertises, which the daemon also maintains. scutil --nwi prints the network interface information: on this Mac, en0 holding an IPv4 address and an IPv6 address, both marked Reachable. scutil --dns prints the DNS configuration the daemon installed after the last network change, resolver by resolver, which is the configuration mDNSResponder then uses to answer every lookup on the system.
This is the honest answer to a question people arrive with, which is what configd is worth seeing from the outside. It is not a black box. The store is the daemon’s public interface, documented, readable without administrator rights, and stable across macOS versions in a way few internal interfaces are.
The bundles, and the six the man page does not mention
The loadable bundles live in /System/Library/SystemConfiguration/. The man page documents seven of them, each with a one line job description:
| Bundle | Job, in the man page’s words |
|---|---|
| KernelEventMonitor | monitors kernel events and conveys changes to the network state, such as link status |
| InterfaceNamer | provides a name to each network interface, BSD style names such as en0, from the IOKit Registry |
| IPConfiguration | establishes and maintains IPv4 and IPv6 addresses, manually or via DHCP, DHCPv6 and RTADV |
| IPMonitor | establishes the primary network service, the default route, the active DNS configuration and proxies |
| LinkConfiguration | maintains the media type, media options and MTU for ethernet interfaces |
| PreferencesMonitor | conveys the administrator’s network preferences to the other agents |
| PPPController | establishes and maintains PPP connections |
The folder on this Mac holds thirteen. The six the man page never mentions are CaptiveNetworkSupport, now split out into its own on demand agent, EAPOLController, InternetSharingPreference, PrinterNotifications, QoSMarking and USBDeviceConfiguration, and you can guess most of their jobs from the names: detecting hotel and café networks that want a login page, the 802.1X authentication used on enterprise Wi-Fi, the internet sharing feature, network printers, the quality of service marking that keeps video calls smooth, and the configuration of USB network adapters.
Two of the thirteen deserve a sentence each. PPPController is the dial up era’s protocol, point to point protocol over a modem, and it is still loaded into every Mac’s network daemon in 2026, which tells you how conservative this layer of macOS is. And InterfaceNamer is the reason your network interfaces are called en0 at all: it queries the hardware registry and assigns the names, which means the name on the interface and the daemon that gave it the name are one fact, not two.
The launch job, read from its own property list
The job definition is /System/Library/LaunchDaemons/com.apple.configd.plist, 1,547 bytes, and its settings say more about how macOS treats this daemon than any description could:
| Setting | Value | What it means |
|---|---|---|
| KeepAlive | true | if it exits, launchd starts it again immediately |
| MinimalBootProfile | true | it starts even when booting a minimal system, before most of macOS |
| POSIXSpawnType | Interactive | launched as interactive priority, not background |
| EnablePressuredExit | true | the system may reclaim it under memory pressure, and it will come back |
| ExitTimeOut | 6 | given six seconds to finish work when the system shuts down |
launchctl print system/com.apple.configd confirms the runtime side: one run since boot, no exits, started for the reason launchd labels speculative, its word for services started on the system’s own schedule rather than on demand, and 29 forks with a single exec, meaning the daemon briefly forks short lived helpers internally without replacing itself, a pattern old enough that it predates the frameworks everyone else uses now.
The property list also reserves twelve Mach services, which are the doors other processes knock on, and they read like a cast list of macOS networking:
| Mach service | Who knocks |
|---|---|
| com.apple.SystemConfiguration.configd | anything using the SystemConfiguration framework to read or watch the store |
| com.apple.SystemConfiguration.configd.watchdog | the system’s own watchdog for the daemon |
| com.apple.network.IPConfiguration | DHCP and manual address work, inside and outside the daemon |
| com.apple.SystemConfiguration.DNSConfiguration | the DNS settings layer, including encrypted DNS profiles |
| com.apple.SystemConfiguration.IPMonitorControl | route and primary service decisions |
| com.apple.SystemConfiguration.NetworkInformation | the interface information scutil --nwi prints |
| com.apple.SystemConfiguration.NetworkCategoryManager | per network categories, such as work versus home |
| com.apple.network.EAPOLController | 802.1X authentication on enterprise Wi-Fi |
| com.apple.networking.captivenetworksupport | captive portal detection |
| com.apple.SystemConfiguration.PPPController, plus its privileged twin | the dial up legacy, still with two doors |
A watchdog door is worth pausing on. macOS so rarely wants to lose this daemon that the launch job reserves a dedicated service whose job is watching the daemon itself. Whatever else configd is, it is not optional, and the system is built on the assumption that it answers. This is the private, per-daemon kind of watchdog; the system-wide one is a different daemon entirely, the one that can force a restart when the whole machine hangs.
One hour of its log, counted
The unified log records what the daemon did, and unlike the man page, the log lines are tagged with the code that emitted them, and most of the tags are the bundles from the section above, so an hour can be attributed:
| Log tag | Lines in one idle hour |
|---|---|
| IO80211, the Wi-Fi driver layer | 136 |
| IPConfiguration | 130 |
| EAPOLController | 16 |
| CaptiveNetworkSupport | 2 |
The hour was not quite idle, which is the point. At 12:09 the Mac’s Wi-Fi reassociated, and the log shows the whole sequence: the 802.11 service binding and unbinding, the link coming up, and IPConfiguration recording the network it landed on:
en0: SSID <redacted> BSSID <redacted> NetworkID <redacted>
Security WPA2_PSK ConnectionID 59
The redactions are not mine. macOS redacts network identifiers in its own logs unless you unlock that data with a profile Apple issues to developers, so even the daemon that knows your Wi-Fi password’s network prints it behind <private>. Four hundred and twenty one lines in an hour, and every one of them traces back to a single network event. On a genuinely stable hour the count is close to zero, which is the shape of an event driven daemon: silent while nothing changes, briefly busy when something does.
One more line from that hour is worth quoting for what it denies: “Allow Sharing Device Type is false”, the daemon recording that this Mac is not sharing its connection, a check it makes because internet sharing is one of the jobs it would be asked to do.
Why it uses CPU, measured properly
The number that worries people is the one in Activity Monitor, so put the measurement here in full. Fifty seven minutes and thirty four seconds of processor time across twenty six days of uptime is about two minutes and thirteen seconds a day, which is about 0.15 per cent of one core, averaged over the machine’s life. Memory was 9 MB, sampled flat across the day this was written.
The shape matters more than the average. configd does work when the network changes and almost none in between, so the honest reading of a high configd is: something is changing the network repeatedly. The list of things that do that is short. Joining, leaving or roaming between Wi-Fi networks. A DHCP lease being renewed, which happens routinely and in bursts on some routers. An Ethernet or USB adapter appearing and disappearing, a flapping dock connector being the classic. A captive portal that will not complete. A VPN that reconnects in a loop. In each case configd is the messenger doing the paperwork, and the fix is upstream of it: a different network, a renewed lease, an unplugged adapter, a VPN that stays connected.
The one pattern worth acting on is a configd that stays high for an hour on a network that has not changed, because sustained work with no events usually means an interface or a lease misbehaving, and that is a real problem, just not one whose cause is the daemon.
The files it keeps
The persistent store, the part that survives a reboot, lives in /Library/Preferences/SystemConfiguration/, exactly where the man page’s FILES section says it does. On this Mac:
| File | Size | What it holds |
|---|---|---|
| preferences.plist | 10,822 bytes | the network services, their order and settings, the desired state |
| NetworkInterfaces.plist | 11,842 bytes | every interface the Mac knows, with the names InterfaceNamer assigned |
| com.apple.airport.preferences.plist | 1,581 bytes | the known Wi-Fi networks and their preferences |
| com.apple.network.eapolclient.configuration.plist | 18,003 bytes | 802.1X enterprise Wi-Fi configuration |
| com.apple.AutoWake.plist | 982 bytes | scheduled wake events |
Two details in that folder tell their own stories. NetworkInterfaces.plist was rewritten at 13:04 today, minutes before these measurements, because the file tracks live interface state, not just saved preferences. And sitting beside the live files are four with names like preferences-pre-upgrade-source.plist, dated the day this Mac took its macOS upgrade in October: the installer’s own backups of the network configuration from before the upgrade, kept forever, which is how much macOS cares about not losing your network setup.
There is also a preferences.plist.old, same size as the live file, readable only by root. The daemon rotates its own preferences file when it rewrites them wholesale, and the old copy is the previous generation, not a problem.
What to do instead of quitting it
Quitting configd buys you a respawn, because KeepAlive is true, and a brief window in which no network change can be processed, which is strictly worse than doing nothing. The supported moves are all named after features, in System Settings, and the Network pane’s own strings name them exactly:
- Turn Wi-Fi off and on. The bluntest version of “make the network change on purpose”, which gives the daemon one clean event to process instead of a stream of half ones.
- Renew DHCP Lease, under Network, Details, TCP/IP. The pane’s own button, which hands IPConfiguration a fresh lease request. The pane warns, in its own words, that “renewing the DHCP lease will cause any unsaved changes to be lost”, which tells you it is a real state change and not a refresh.
- Switch to a new network location. A location is a whole separate desired state, and switching to a fresh one is the closest thing configd has to a factory reset that you can do from a settings pane.
- Apply, when a new interface is detected. The alert the pane shows for a new adapter reads “A new network interface has been detected” and continues, in the pane’s own words, “Please verify that it is configured correctly, then press Apply to activate it”. That alert is InterfaceNamer’s work surfacing in the UI, which is the closest most people get to seeing this daemon.
None of these need a terminal, and all of them work with the daemon rather than against it, which is the difference between fixing a network and re-rolling the dice on one.
What this page cannot tell you
The daemon runs as root, and reading its open files and sockets with tools like lsof needs the same rights, which was not done here, so nothing on this page claims to know what configd had open. The contents of 802.1X and VPN configuration files were not read either, only their sizes and modification dates, because enterprise credentials are exactly the kind of thing a read only measurement should not go poking through. And the log’s redactions cut both ways: the same privacy protection that keeps a café network’s name out of a shared bug report also keeps it out of this page.
The bundle jobs given here for the six undocumented agents are read from their names, their Mach services and their log lines, not from documentation, because no documentation exists. That is an inference, marked as one, and it is the only inference on this page.
Apple never says its name
The macOS User Guide describes joining Wi-Fi networks, renewing leases, sharing connections and everything else configd does, and a search of the guide’s full table of contents for this macOS version finds the daemon’s name zero times. The pages describe the features; the machinery goes unmentioned, which is the norm for this series of pages and the reason people end up searching process names at all.
The one place Apple does describe the layer in public is aimed at developers, on the page for the SystemConfiguration framework, the API that sits on top of the store: it exists to “allow applications to access a device’s network configuration settings” and to “determine the reachability of the device, such as whether Wi-Fi or cell connectivity are active”. Every app that has ever checked whether the network was up before doing something has gone through that framework, and therefore through this daemon’s store.
Where window managers fit
configd is about the space between your Mac and the network, and nothing on this page changes the space on your screen. The two show up in the same place, though: Activity Monitor, on a slow day, with a list of names you did not choose. Knowing what a daemon is for turns that list from noise into information, and most of it turns out to be machinery quietly doing two minutes of work a day.
Ribbon is for the part of the machine you actually look at. Windows stay at full size on a single scrolling strip instead of stacking, so the window you want is one swipe away and nothing hides behind anything. It is $15, once, for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs. You can drive the strip in your browser before installing anything.
The short version
configd is the daemon that configures your Mac’s networking. It holds a store with the network you asked for and the network you actually have, reconciles the two whenever anything changes, and does the work through thirteen bundles, of which the man page documents seven. It joined your Wi-Fi, got your DHCP address, named your interfaces en0, and wrote the DNS settings every lookup on the system runs through.
It is measurable, and the measurements are small: one process, root owned, 9 MB of memory, fifty eight minutes of processor time in twenty six days, one start and no exits, no crash reports on this Mac. When it spikes, the network changed, and the fix is a feature move in System Settings, not a force quit.
There is nothing to remove and nothing worth quitting, and the system agrees with itself about that: KeepAlive restarts it if it goes, a reserved watchdog service watches it, and it is one of the few things launched even in a minimal boot. The names in Activity Monitor are mostly daemons like this one, earning their two minutes a day, and configd is one of the few whose own manual will actually tell you what it is for.
Questions
What is configd on Mac?
It is the daemon that configures your Mac's networking. Apple's own man page says it is responsible for many configuration aspects of the local system, that it maintains data reflecting the desired and current state of the system, and that it hosts a number of configuration agents in the form of loadable bundles. In practice that means it is the process that joins your Wi-Fi, asks the router for a DHCP address, writes the DNS settings every other process uses, names your network interfaces en0 and friends, and watches for the network to change so it can redo any of those. On this Mac it has been running since boot as PID 423, owned by root, and it is one of the few daemons macOS starts even in a minimal boot, because almost nothing else can come online without it.
Is configd a virus or malware?
No. It is Apple's own code. The binary lives at /usr/libexec/configd on the sealed system volume, it is signed by Apple's system authority, it runs as root because configuring network interfaces requires root, and it was launched by launchd as job com.apple.configd at boot, 26 days before these measurements were taken, with exactly one start and no exits since. People search the name because it appears in Activity Monitor with a lowercase name that looks unlike anything they installed, usually sitting near the top of a memory or CPU sort on a day when the Wi-Fi has been changing.
Why is configd using high CPU or memory?
Almost always because the network changed. The daemon is event driven: it does nearly nothing while the connection is stable, then does a burst of work when a Wi-Fi network is joined or roamed, a DHCP lease is renewed, an interface appears or disappears, or a captive portal has to be checked, a question [the captiveagent daemon](/guides/captiveagent-mac) exists to answer. On this Mac, 57 minutes 34 seconds of processor time across 26 days of uptime works out to a bit over two minutes a day, or about 0.15 per cent of one core. An idle hour produced 421 log lines, and every one of them belonged to a single Wi-Fi rejoin at 12:09, the moment [the airportd daemon](/guides/airportd-mac) handed the radio back and the configuration work began. A configd that stays high for an hour on a stable network is worth investigating, because that pattern usually means an interface flapping or a lease that keeps being renewed, not the daemon itself misbehaving.
Can I quit or disable configd?
You can quit it and it will come straight back. Its launch job has KeepAlive set to true, so launchd restarts it the moment it exits, and while it is gone no new network can be joined, no DHCP lease can be renewed, and the DNS configuration stops tracking the connection you are on. There is no supported way to disable it and no reason to want one. The supported moves for a network that is misbehaving are the ones named after features: turn Wi-Fi off and on, use the Renew DHCP Lease button in System Settings under Network, Details, TCP/IP, or switch to a fresh network location, which resets the desired state the daemon works from.
What are the bundles in /System/Library/SystemConfiguration?
They are configd's configuration agents, and they are the reason one process can do so many unrelated sounding jobs. Each bundle takes responsibility for one slice of the network: IPConfiguration establishes IPv4 and IPv6 addresses including DHCP, InterfaceNamer gives interfaces their en0 style names by reading the IOKit registry, KernelEventMonitor watches for link status changes, IPMonitor maintains the default route, active DNS and proxies, and so on. The man page documents seven of these agents. The folder on a current macOS install holds thirteen, so six of them, including CaptiveNetworkSupport, EAPOLController and QoSMarking, do their work without any documentation at all.
Ready? Buy Ribbon for $15, or read all the guides.