What is airportd, 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.
airportd is the macOS daemon that manages the Wi-Fi hardware: it scans for networks, joins and roams between them, and serves Wi-Fi information to apps. It uses CPU when the Mac scans a lot, for example with a weak or unstable signal or many nearby networks. It is part of macOS and cannot be turned off without turning off Wi-Fi.
airportd at a glance
| airportd | |
|---|---|
| Made by | Apple (part of macOS, Wi-Fi) |
| Type | System daemon |
| Location | /usr/libexec/airportd |
| Runs as | root |
| Started by | launchd job com.apple.airportd |
| Can you quit it? | No. It manages the Wi-Fi hardware, and launchd restarts it if it stops. |
What is airportd?
The man page states simply that airportd manages wireless interfaces. Its name comes from AirPort, Apple's old brand for Wi-Fi. launchd starts it when the Wi-Fi controller appears in the hardware registry, and it provides the services that the Wi-Fi menu, System Settings and the CoreWLAN framework use to read signal strength, list networks and join them.
airportd runs as root. Tasks that need your login session, such as asking you to join a network or showing Wi-Fi notifications, are passed to WiFiAgent.
Is airportd safe?
Yes. airportd lives in /usr/libexec on the read-only system volume and is started by an Apple launch daemon. The man page says it should not be invoked directly.
Why does airportd use so much CPU and energy?
- A weak or unstable signal. When the signal is poor, the Mac scans for a better access point and may roam between them. Each scan and roam is work for airportd.
- Many networks nearby. In apartments, offices and airports, scan results are long and change constantly, so processing them costs more.
- Location and nearby-network features. Location Services and features that look for known networks use Wi-Fi scans. Apple's platform security guide notes that these scans use a randomized hardware address when the Mac is not joined to a network.
- Apps polling Wi-Fi details. Menu bar utilities and network tools that ask for signal strength or scan results every second keep airportd answering.
- Enterprise Wi-Fi and captive portals. Networks that need 802.1X sign-in or a login page add extra steps on every join and rejoin.
How much CPU is normal for airportd?
Typical use is near 0% CPU on a stable connection, with short spikes when the Mac wakes, joins a network or scans.
Several percent of CPU for long periods usually means repeated scanning or roaming.
How do you stop airportd from using so much CPU?
- Check signal and noise. Run
sudo wdutil infoin Terminal. It shows the details of the current Wi-Fi connection, including signal (RSSI) and noise. Move closer to the router if the signal is weak. - Forget networks you no longer use. In System Settings > Wi-Fi, remove saved networks you no longer use, especially open ones with common names. The Mac stops looking for them.
- Quit Wi-Fi monitoring apps. Quit any third-party menu bar or scanning utility and see whether airportd calms down.
- Run Wireless Diagnostics. Run
sudo wdutil diagnosein Terminal. It runs the same checks as the Wireless Diagnostics app and saves a report in/var/tmp. - Restart Wi-Fi. Turn Wi-Fi off and on in Control Center. If airportd stays high, restart the Mac.
When should you worry about airportd?
Look closer if airportd stays above about 10% CPU while connected to a strong, stable network, or if Wi-Fi keeps dropping. A Wireless Diagnostics report will show disconnects and roams.
airportd outside /usr/libexec would not be Apple's.
How do you check airportd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type airportd in the search field. The CPU tab shows its % CPU. The Energy tab shows its Energy Impact. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every airportd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'airportd' | grep -v grep
pmset -g assertions # shows processes keeping the Mac awake
How can Thrum help with airportd?
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 airportd 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 airportd
Why is it called airportd?
AirPort was Apple's name for Wi-Fi on earlier Macs. The daemon kept the name.
Does turning Wi-Fi off stop airportd?
It stops scanning and joining, so airportd becomes idle, but the process can stay running to answer requests.
What is the difference between airportd and WiFiAgent?
airportd runs as root and controls the hardware; WiFiAgent runs in your login session and handles prompts and notifications for it.
Sources
- airportd(8) man page: run man airportd in Terminal
- wdutil(8) man page: run man wdutil in Terminal
- Apple Platform Security: Privacy features when connecting to wireless networks