What is configd on Mac?
Mac users occasionally encounter a peculiar situation where an otherwise inconspicuous system process starts gobbling up CPU resources for no apparent reason. One such culprit is configd, a background daemon that may suddenly climb to 100% CPU usage or higher, making the computer sluggish, draining the battery, and causing the fans to run at full blast. The issue has been making the rounds across Apple support discussions and Mac forums for years, affecting different generations of Apple computers and macOS versions.

So, what is configd, and why does it sometimes go haywire? First things first, it's a legitimate Apple process, not malware. Short for System Configuration Daemon, configd helps macOS manage network settings and respond to configuration changes. Its responsibilities include monitoring network interfaces, maintaining information about IP addresses and DNS settings, and notifying other system components when connectivity parameters change.
Under normal circumstances, configd does its job quietly in the background. However, if another component repeatedly changes network settings or an internal configuration agent gets stuck, the daemon may enter a processing loop. That said, the high CPU usage is often a symptom of an underlying network-related problem rather than a malfunction of configd itself.
Why configd uses too much CPU on Mac
There are several plausible triggers for excessive resource consumption by this daemon. The most common ones include:
- VPN software conflicts. VPN clients create virtual network interfaces and modify routing or DNS settings. An incompatible or malfunctioning client may repeatedly trigger configd.
- Unstable network connections. Wi-Fi dropouts, faulty Ethernet adapters, or problematic USB-C docks can cause recurring network configuration changes.
- Outdated network extensions. Firewalls, DNS filters, and other third-party networking tools may interfere with configd, particularly after a macOS upgrade.
- Corrupted or conflicting network preferences. Inconsistent settings may cause configuration operations to fail or repeat.
- Hardware-related anomalies. Some owners of older MacBooks have reported unusual configd CPU activity after battery replacements, particularly when running on battery power. The connection is anecdotal rather than a confirmed root cause.
The process may also appear to use excessive memory. However, an unusually large memory footprint isn't necessarily evidence of a leak. Activity Monitor's Memory Pressure indicator provides better insight into whether RAM consumption is actually affecting performance.
How to fix configd high CPU usage on Mac
Since configd is an essential macOS component, removing or permanently disabling it isn't an option. The following troubleshooting steps focus on identifying the underlying trigger and restoring normal resource consumption.
1. Check configd in Activity Monitor and restart your Mac
Before making changes, verify that configd is consistently consuming excessive resources rather than experiencing a temporary spike.
- Open Finder > Applications > Utilities > Activity Monitor.
- Select View > All Processes.
- Open the CPU tab and search for
configd. - Check whether its CPU usage remains abnormally high for several minutes.
- Restart your Mac and see whether the problem returns.

If the daemon settles down after a restart, you may have been dealing with a temporary configuration glitch. If the spike returns, proceed with the following methods.
2. Check configd errors in Console
The built-in Console app can help identify recurring errors or network configuration events associated with excessive configd activity.
- Open Finder > Applications > Utilities > Console.
- Select your Mac in the sidebar and click Start if live log streaming isn't already active.
- Type
configdinto the search field and filter the results by process if that option is available. - Look for recurring errors, warnings, or messages about network interfaces and configuration changes.
- Compare the timestamps with the CPU spikes observed in Activity Monitor.

An occasional warning isn't necessarily a sign of trouble. What matters is a recurring pattern that coincides with abnormal CPU usage. If the messages consistently point to a particular network component, that may help narrow down the culprit.
3. Check network connections and renew the DHCP lease
An unstable connection or recurring IP address configuration error may keep configd unnecessarily busy.
First, disconnect external Ethernet adapters, USB-C hubs, and docking stations. If possible, test another Wi-Fi network and observe whether the CPU spike persists.
You can also renew the DHCP lease:
- Open Network settings and select your active connection.
- Locate the TCP/IP options, using the Advanced or Details button if applicable.
- Click Renew DHCP Lease.
- Check whether the connection operates normally and configd's CPU usage decreases.

This method applies to connections using DHCP and may briefly interrupt network access. If the issue persists, continue with the next step.
4. Create a new network location
If your Mac has accumulated conflicting network preferences, creating a separate configuration can help determine whether the existing settings are responsible.
- Open Network settings and find the Locations menu or Edit Locations option.
- Create a new location using the plus (+) button.
- Give it a descriptive name, such as Network Test.
- Apply the changes and configure the connection if necessary.
- Check whether configd's CPU usage returns to normal.

If this helps, review the original location's DNS, proxy, VPN, and network service settings. You can switch back to the previous configuration whenever necessary.
5. Restart the configd daemon
When configd appears stuck in a processing loop, restarting the service may temporarily clear the condition.
- Open Finder > Applications > Utilities > Terminal.
- Enter the following command:
sudo killall configd - Press Return and enter your administrator password when prompted.
- Allow macOS to relaunch the daemon automatically.
- Reopen Activity Monitor to check its CPU usage.

Note that this operation may briefly disrupt network connectivity. If the problem returns immediately, something else is probably triggering the process repeatedly. Don't attempt to disable configd permanently or delete its system files.
6. Use Safe Mode to check for software conflicts
If the previous methods haven't helped, Safe Mode can indicate whether third-party components contribute to the problem.
On an Intel-based Mac:
- Shut down the computer.
- Turn it on while holding Shift.
- Release the key at the login screen.
- Sign in and check configd in Activity Monitor.
On a Mac with Apple silicon:
- Shut down the computer.
- Hold the power button until startup options appear.
- Select your startup disk.
- Hold Shift and click Continue in Safe Mode.
- Sign in and examine configd's CPU usage.
If the daemon behaves normally in Safe Mode, a third-party extension, startup component, or another difference in the reduced startup environment may explain the issue. Restart normally and review recently installed networking utilities.
Is configd a virus?
No. The genuine configd daemon is a standard macOS component responsible for system configuration management, particularly networking. Its legitimate executable is located at /usr/libexec/configd.
High CPU or memory usage doesn't mean the process is malicious. Nevertheless, malware sometimes masquerades as legitimate system components, so an unfamiliar executable with a similar name warrants closer examination.
If you suspect foul play, inspect the process information in Activity Monitor and check for other signs of compromise, such as unknown login items, unauthorized browser changes, or unexpected network activity. Avoid deleting the genuine Apple daemon.
How to prevent configd CPU spikes going forward
Keeping your Mac's networking environment tidy can go a long way toward preventing this problem. Update VPN clients, firewalls, and network extensions regularly, especially after upgrading macOS. Remove unused network utilities and obsolete VPN configurations, and make sure external adapters and docking stations work reliably.
It's also worth avoiding unnecessary changes to protected system components. Some advanced troubleshooting discussions recommend disabling System Integrity Protection or modifying configuration agents, but these measures introduce security risks that generally outweigh their potential benefits.
The bottom line
Configd is a legitimate macOS service, but network configuration conflicts can sometimes push its CPU consumption well beyond normal levels. VPN applications, unstable connections, and outdated network extensions are among the first suspects worth investigating.
In most cases, a systematic check of the network setup is more productive than repeatedly terminating the daemon. The goal is to eliminate whatever keeps triggering it, not interfere with an essential part of macOS.
FAQ
Why does configd use 100% CPU on Mac?
The daemon may become overloaded when repeatedly processing network configuration changes. Common suspects include VPN conflicts, unstable connections, malfunctioning network extensions, and inconsistent network settings.
Can I quit configd in Activity Monitor?
Yes, macOS normally relaunches the daemon automatically. However, terminating it may temporarily interrupt network connectivity, and the CPU spike can return if the underlying problem remains unresolved.
Is configd high CPU usage related to VPN software?
Why is configd using so much memory?
The process maintains configuration data and hosts system agents, so it naturally uses RAM. Abnormally high or steadily increasing consumption may indicate an issue, but check Activity Monitor's Memory Pressure and swap usage before concluding that there's a memory leak.
Is it safe to delete configd from my Mac?
No. Configd is an essential Apple system daemon. Removing or disabling it can interfere with networking and other system functions. Troubleshoot the components interacting with it instead.
