# airportd, the Wi-Fi daemon

> airportd is the daemon that runs the Wi-Fi radio in your Mac, scanning, roaming and AWDL included. Measured live: its real CPU cost and its log firehose.

Source: https://www.ribbonmac.com/guides/airportd-mac · Updated 2026-11-18

Three things bring people to this page, and the third is the best one. First, Activity Monitor, CPU column, where a lowercase word with no app icon sits using a percent or two and a forum says system process, leave it alone. Second, Console, where airportd is the loudest process on the machine, eight lines a second, every line packed with numbers, like a stock ticker nobody asked for. Third, the name itself: this Mac has never seen an AirPort base station, Apple stopped making those in 2018, and yet the Wi-Fi daemon on a macOS 27 machine in 2026 is still called the airport daemon.

This page answers all three the way the rest of this series does: from the daemon's own files, read only, on a MacBook Pro on macOS 27.0.1, nothing installed and no setting changed.

## The receipts

```
$ ps -Awwo pid,ppid,user,%cpu,rss,etime,time,comm
  PID  PPID USER  %CPU    RSS     ELAPSED      TIME COMMAND
  550     1 root   0.0  12896  28-01:12:05 140:36.39 /usr/libexec/airportd

$ ls -l /usr/libexec/airportd
-rwxr-xr-x  1 root  wheel  3213008 Sep 24 12:40 /usr/libexec/airportd

$ codesign -dv /usr/libexec/airportd
Identifier=com.apple.airport.airportd
Format=Mach-O universal (arm64e arm64e.x1)
Platform identifier=26
```

Process 550, parent 1, user root, alive for every second of the machine's 28 day uptime. The binary is 3.2 MB of Apple signed code, arm64e and arm64e.x1 only, no Intel slice, which is the same shape the push and identity daemons in this series carry. The man page is the shortest in the series since the location daemon's: one sentence, dated 7/5/2006, and worth quoting whole because there is nothing else. airportd manages wireless interfaces. airportd should not be invoked directly.

The launch configuration is where this daemon is unusual, and it is worth slowing down on, because it explains a complaint people have about Wi-Fi after boot.

## A daemon that starts with the hardware

Most daemons in this series are started by a timer, a socket knock, or the login. airportd is started by the device. Its launch job carries a device match, not a schedule:

```
LaunchEvents = {
  "com.apple.iokit.matching" = {
    "com.apple.wifi.controller" = {
      "IOMatchLaunchStream" = true;
      "IOProviderClass" = "IO80211Controller";
    };
  };
};
```

That reads: when the kernel registers a driver of class IO80211Controller, in plain words, when the Wi-Fi chip shows up on the bus, start this job. No Wi-Fi chip, no airportd. The practical consequence is that the daemon's life and the radio's life are the same life, and on this Mac the two have been inseparable since 12:55 on 20 October, when the kernel booted the machine.

Two more lines from its launch record finish the picture. `runs = 1`, `last exit code = (never exited)`: in 28 days it has not been restarted, reclaimed or recycled once. And `EnablePressuredExit = false` with `KeepAlive = { Crashed = true }`: the memory system is forbidden from reclaiming it when idle, and if it ever crashes, launchd brings it straight back. The bluetooth daemon in this series makes the same pair of choices for the same reason. A radio stack that vanishes under memory pressure stops being a radio.

## The firehose, and why it is not CPU

Here is the number that worries people. In half an hour of ordinary, working Wi-Fi, this daemon wrote 14,690 lines to the unified log. That is the chattiest process measured in this entire series, five and a half times the identity daemon, and unlike most of the series it is not logging events. It is logging measurements, continuously:

```
[corewifi] LQM: rssi=-41dBm per_ant_rssi=(-45dBm, -41dBm)
  noise=-90dBm snr=16 cca=2.0% txRate=907.4Mbps rxRate=1201.0Mbps
  txFrames=35 txFail=0 beaconRecv=50 channel = 60 BW = 80 band = 2
```

This is the link quality monitor, LQM, airportd's dashboard for the connection it is holding. Signal minus 41 dBm, a strong connection. Signal to noise of 16. Transmitting at 907 megabits, receiving at 1,201. Zero failed frames out of 35 sent. Channel 60, 80 megahertz wide, on the 5 GHz band. On a Wi-Fi 7 machine it logs these per MLO link, per multi link operation, because the radio is holding two connections at once and scoring each. Every line a second, every second of the day.

The mistake is reading that volume as work. The line that proves it is buried in the same stream, and it is the daemon reporting its own cost for one whole event:

```
airportdProcessTrafficEngineeringEvents: <en0> eventType[39]
  took 0.000048
```

Forty eight microseconds. The firehose is a ruler, not an engine. Logging is nearly free, which is lucky, because this daemon cannot help measuring.

## The real cost

```
140:36.39 of CPU over 28.05 days = 5 min 01 s a day = 0.35% of one core
RSS 12,896 KB -> 23,808 KB across two samples seven minutes apart
```

Five minutes a day is middleweight territory in this series: half the logging clerk's nine minutes, a shade under the file event daemon's five minutes fifteen. Memory doubled between two samples, which looks alarming and is not; the daemon buffers its statistics tables and the system, barred from pressuring it out, simply lets it hold what it needs. It settled, as these things do, the moment the sampling stopped.

When airportd's CPU column climbs and stays up for an hour, the environment is misbehaving, not the daemon. Four patterns cover almost all of it. A signal that flaps, visible in its own LQM lines as an RSSI that swings tens of dBm. A hidden network saved in your preferences, which the daemon must keep actively scanning for because hidden networks never announce themselves. A captive portal that never completes, so the join restarts, and [the daemon that probes those portals](https://www.ribbonmac.com/guides/captiveagent-mac) has its own page. And a roam loop, two access points with similar signal, the machine ping ponging between them, each roam logged by name and reason. In all four cases the log names the problem in the first twenty lines. Forget the flapping network, move closer to the router, or change the channel. The daemon was only ever the messenger with the clipboard.

## The name, or why your Mac still says AirPort

Apple launched AirPort in 1999, sold base stations for nineteen years, ended the line in 2018, and never renamed the software. The receipts, all from this machine, today:

```
$ man airportd
airportd(8) - airport daemon

$ plutil -p /Library/Preferences/SystemConfiguration/com.apple.airport.preferences.plist
couldn't be opened because you don't have permission to view it

$ networksetup -getairportnetwork en1
en1 is not a Wi-Fi interface.
You are not associated with an AirPort network.
```

That last one is my favourite receipt in the series. A command line tool, on macOS 27, in 2026, answering a Wi-Fi question with an error message written for hardware discontinued eight years ago. The plist is real too, 1,581 bytes, modified this morning at 06:11 when the network last changed, sitting in a world readable folder and readable by nobody, because your saved Wi-Fi networks are exactly the kind of thing that lives behind the privacy wall.

One piece of the heritage really is gone. The airport command, the power user tool for scanning and sniffing that lived at /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport, returns No such file or directory on macOS 27. Fifteen years of forum posts now point at a file that no longer exists.

## Ten doors, one of them public

The plist lists ten message services, and the count says something about how Apple builds this stack:

```
com.apple.airportd            com.apple.wifi-xpc
com.apple.corewlan-xpc        com.apple.wifi.sharekit
com.apple.private.corewifi-xpc        com.apple.wifi.useragent
com.apple.private.corewifi.internal-xpc
com.apple.private.corewifi.readonly-xpc
com.apple.private.corewifi.unrestricted-xpc
com.apple.private.corewifi.user-agent-xpc
```

Nine of the ten are private doors for Apple's own frameworks, graded by privilege: one read only, one unrestricted, one for internal use, one for user agents. The tenth is the one you have used without knowing: com.apple.corewlan-xpc. CoreWLAN is the public Wi-Fi framework, the one whose documentation tells you how to list networks and read signal strength, and every call in it crosses into airportd through that door. When a Wi-Fi stumbler app shows channels, it is reading airportd's measurements. The daemon also carries an environment flag for dark wake, REACH_DARK_WAKE_CONTROL, which is how it participates in wake for network access: the Mac can be asleep, the radio briefly up, the connection kept alive, all without the screen.

## The second network: awdl0

```
$ ifconfig awdl0
awdl0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether 6a:7d:ea:a2:01:85
```

en0 is your Wi-Fi interface, and awdl0 is the other one, up and running beside it with a different hardware address. AWDL, Apple Wireless Direct Link, is a peer to peer network protocol that runs on the same radio, time sliced against your ordinary traffic, and airportd schedules the slices. AirDrop, AirPlay, Sidecar, and every Continuity handoff between your Apple devices ride on it. Its address differs from en0's because AWDL rotates its identity rather than broadcasting your real one. The binary's strings include a line that describes the whole arrangement better than any marketing page: AWDL real time device to device migration is active. When AirDrop crawls in a crowded room, this is the mechanism under the symptom: peers, channels and slices competing.

## The neighbours

The radio comparison in this series now has both radios measured. bluetoothd runs the other radio from a 37 MB binary, nearly twelve times airportd's size, because Bluetooth carries audio timing, a dozen profiles and a certification suite in one process. airportd's 3.2 MB is the smaller job done tighter. Around it sit the same supporting cast the network guides in this series named: configd, which decides what the network should look like while airportd makes the radio do it, and mDNSResponder, which turns the working connection into names. Three daemons, three verbs: configure, transmit, resolve.

## What Apple says, and does not

The Mac User Guide's table of contents is 250,885 bytes of everything Apple will tell you about macOS by name, and the string airportd appears in it zero times. As with every daemon in this series, the feature is documented and the machinery is not: the guide will tell you how to join a Wi-Fi network, share your Wi-Fi password with another device, and diagnose a connection, and none of those pages will ever mention the process doing the work. Zero crash reports on this machine in 28 days, in either Diagnostic Reports folder. That is the quietest scorecard a radio manager can post.

If it ever dies anyway, launchd has instructions: restart it, keep it, never let the memory system take it. The one sentence from 2006 covers the rest. Should not be invoked directly. Neither, really, should you care to. The measurements above are the closest look the system ever intends to give you, and it writes them down continuously, eight lines a second, in a log anyone can read.

## FAQ

### What is airportd on Mac?

It is the daemon that runs your Mac's Wi-Fi radio. It scans for networks, joins them, roams between access points, keeps the link quality statistics, and runs AWDL, the peer to peer side channel that AirDrop and Continuity use, all in one process. On the Mac measured here, a MacBook Pro on macOS 27.0.1, it has been running as root since boot without exiting once in 28 days, costs about five minutes of processor time a day, and describes its entire job in a manual page of one sentence dated 2006. Apps never talk to it directly. They talk through CoreWLAN, the Wi-Fi framework, which passes the request over one of the ten private message services airportd listens on.

### Why is airportd using so much CPU?

Measured over 28 days it averages five minutes and one second of processor time a day, about a third of one per cent of a single core, sampling between 0.0 and 0.9 per cent while this page was written. When it climbs and stays up, the work almost always belongs to the environment, not the daemon: a signal that keeps flapping, a hidden network it has been told to keep scanning for, a captive portal that never finishes its login page, or two access points it keeps roaming between. The daemon's own log makes the culprit easy to find, because it writes link quality lines continuously and they carry the evidence: a signal reading that swings, a channel that is crowded, retransmit counts climbing. airportd logs an enormous amount, eight lines a second here, but logging is not the same as working. The busiest line in its log reports its own cost, and that cost was 48 microseconds.

### What does AirPort have to do with my Mac?

Only the name. Apple called its Wi-Fi products AirPort from 1999, kept the word in the software when the hardware line ended in 2018, and never went back to rename the daemon. The receipts are on the disk today: the manual page is titled airport daemon, the system settings file it keeps is still named com.apple.airport.preferences.plist, its code signing identifier is com.apple.airport.airportd, and if you ask the networksetup command about Wi-Fi on a machine with the radio off it answers, word for word, You are not associated with an AirPort network. The old airport command line tool that power users remember is gone entirely; the binary is no longer in the framework folder where it lived for fifteen years.

### What is com.apple.airportd?

It is airportd's launch job name and one of its own message services. launchd starts airportd when the Wi-Fi driver appears, using a device match on the driver class rather than a timer, and the daemon then listens on ten private message services. The one that matters to you as an app developer or a curious reader is com.apple.corewlan-xpc, because CoreWLAN is the public Wi-Fi framework: every app that lists networks, reads the current signal, or joins a hotspot is talking to airportd through that door without ever naming it. The other nine are private doors for Apple's own frameworks, including a separate one for [the captiveagent daemon](/guides/captiveagent-mac), the user agent that handles captive network login pages.

### Can I quit or stop airportd?

Not in any way that helps. It runs as root, launchd restarts it if it crashes, and it has not exited once in 28 days on the measured Mac. Its manual page puts it in one line: airportd should not be invoked directly. What you can do is turn Wi-Fi off, which stops the radio work and the log firehose but leaves the daemon in place, waiting for the driver, which is exactly the design: the system would rather keep a quiet 13 to 24 MB process resident than bring the whole Wi-Fi stack back from nothing every time you click the menu bar icon. If airportd is the reason you are asking, the answer is almost always upstream of the daemon: the router, the channel, the distance, or one saved network that should be forgotten.

### What is AWDL on my Mac?

Apple Wireless Direct Link, the second network your Mac runs over the same Wi-Fi radio, and airportd runs it too. It shows up as the awdl0 interface, up and running alongside en0, with its own different media access address because it periodically changes identity rather than broadcasting your real one. AirDrop, AirPlay, Sidecar, and the Continuity handoffs between your devices all ride on it, time sliced against ordinary Wi-Fi traffic under airportd's control. One of the daemon's own log strings describes the mechanism plainly: AWDL real time device to device migration is active. When AirDrop is slow at a crowded coffee shop, the usual suspect is that time slicing competing with a noisy channel, not a setting you have wrong.
