HeartbeatHocusFocusFilesMacHyperTile
Guide

apsd, the daemon that keeps one line open to Apple

apsd is the macOS daemon that holds one permanent connection open to Apple so notifications can arrive. Measured live: its couriers, its bouncer, 38 seconds of CPU a day, and the clock it keeps.

By Chethan Kumar S N · Updated

Of all the lowercase names in Activity Monitor, apsd is the one holding a telephone line open to Apple at this very moment. It opened the line when your Mac booted, it has not hung it up since, and it will not. That is the entire job: keep one connection alive, so that when something happens on Apple’s servers, a message, an alert, a Find My ping, the news can travel down a wire that is already warm. Everything else on this page is detail, but the detail turns out to be good.

The measurements come from one Mac: a 10 core MacBook Pro on macOS 27.0.1, up 27 days at the time of writing. Everything was read read only: the manual page, the launch configuration, six hours of unified logs, the binary’s own strings, and the network table. Nothing was quit, killed or changed, and every command is at the end if you want to look at your own machine the same way.

A manual page from 2009

apsd is the fifth daemon in this series that ships with its own manual page, after spindump, usernoted and the installd twins, and its page is the oldest by far. It is dated February 10, 2009, back when the operating system was still called Mac OS X, and it reads, in full:

NAME: apsd, Apple Push Notification service daemon. DESCRIPTION: apsd ApplePushService daemon for Apple Push Notification service. This is part of the ApplePushService framework. There are no configuration options to apsd. Users should not run apsd manually.

Seventeen years of macOS later, the description is still accurate, and the last two sentences are still the best advice about this daemon that exists. There is nothing to configure, and you should not run it yourself. The binary itself, 4.6 MB of it, arm64e only with no Intel slice, built on a September 2026 day and signed by Apple with platform identifier 26, sits directly inside the ApplePushService framework, one directory shallower than the fseventsd and installd binaries that hide in Support folders. It has 11,426 strings in it, and later in this page you will meet some of the stranger ones.

One line, always open

Open a terminal and run netstat, and you can watch the promise being kept. On this Mac there were three established TCP connections on port 5223, each one to an address in Apple’s 17.x.x.x network range: one belonging to the system apsd, and two belonging to the copycats every booted iPhone simulator runs. Port 5223 is the Apple Push Notification service port, the door pushes come through. The log calls the system’s connection C4416 and shows it riding the Wi-Fi interface, renegotiating the path every time the network changes quality, and the daemon’s own vocabulary for these connections is better than any description I could invent: it calls them couriers.

The strings inside the binary read like staffing for a delivery office. A main user courier, protocol connections, a courier redirect hostname for when Apple says to reconnect elsewhere, a proxy agent standing by. The logs back the metaphor up: when the connection flaps, apsd delivers a connectionStatusChange to every client that cares, and if you have read the usernoted page you have seen the receiving end of those deliveries in Notification Center’s own logs. When Wi-Fi drops and comes back, the courier re establishes the route and the deliveries resume. A notification finding your Mac the second the network returns is not magic. It is this, working.

There is even a fallback catalog. Among the strings sits the address of what the daemon calls the server bag, the configuration bundle it fetches on startup to learn today’s rules, plus a sandbox copy for developers and a web copy at web.push.apple.com, because web push notifications, the ones websites can send in Safari, ride through this same daemon too.

The front door, and the bouncer

apsd offers exactly one Mach service to the system, named after itself, and processes connect to it all day. In six hours of logs on this Mac, 51 distinct processes knocked. You would recognise many of them: identityservicesd, which carries iMessage; StatusKitAgent, the Live Activities system; appstoreagent, doing App Store work; cloudphotod, keeping shared iCloud photo albums fresh; amsengagementd and jetpackassetd from Apple’s media stack.

Not everyone gets in. Before a client can talk to the push system, apsd checks its entitlements, the code-signed permissions baked into every Apple and App Store binary, and it checks them by name: aps-connection-initiate, secure-apsclient, aps-client-cert-access, dark-wake-push, push-to-wake, interactive-push. In the six hour window the daemon ran 1,229 entitlement checks and failed 536 of them, nearly half. A process that fails gets a brusque refusal in the log, Peer connection lacks APSConnectionInitiateEntitlement, and the door closes. This is a bouncer checking a guest list written by Apple’s own code signing, and it is the reason a random downloaded binary cannot simply subscribe your Mac to a push firehose.

The clock that corrects itself

Buried in the logs is a job nobody advertises. Every time the courier hears from the server, apsd calculates the difference between its own clock and Apple’s, to the nanosecond, and writes the result down. It did this 1,117 times in six hours, once every 19 seconds on average. The last line while this page was being written reported a difference of exactly zero seconds.

Push notifications are worthless if they are late, and late is measured against the sender’s clock, so the daemon that carries them keeps a running correction against the server’s. Your Mac syncs its clock through other channels too, but the push system does not wait for any of them. It brings its own.

The cost, measured honestly

For a daemon that never stops, apsd is remarkably cheap. In 27 days of continuous running it used 17 minutes 21 seconds of processor time, which works out to about 38 seconds a day, or four hundredths of one percent of a single core on this 10 core machine. That is the same class as usernoted, the notification display daemon, and about a third of what fseventsd, the file system diarist, spends. Memory sits at 9 to 10 MB, and it fell between the two samples taken for this page, from 10.4 MB to 9.1 MB, which is a daemon trimming itself, not one leaking.

The launch configuration explains the shape of those numbers. runs equals 1: the daemon started once, when the Mac booted, and has never exited. The reason launchd gives for starting it is speculative, meaning launchd started it early because it knew it would be needed, a small vote of confidence. Minimum runtime is 10 seconds, exit timeout 5, and two settings do the rest of the talking. POSIXSpawnType Interactive puts it in the responsive class, and EnablePressuredExit is set to false, one of the rare daemons, like fseventsd, where the system has explicitly promised not to reclaim its memory under pressure. A process whose whole identity is an open connection cannot afford to be paged out.

The zero-byte file that keeps it alive

KeepAlive on macOS usually means a boolean: if the process dies, start it again. apsd’s version is stranger and more elegant. Its launch file says: stay alive while this file exists, /Library/Preferences/com.apple.apsd.launchd. That file is zero bytes long. It contains nothing. On this Mac it carries a creation date from the day the machine was set up, two months ago, and it has never been written to since.

Its entire job is to exist. It is a dead man’s switch in reverse: the day that file is gone, apsd is allowed to stop, and that is essentially how macOS shuts push down cleanly without killing anything. Alongside it, the configuration carries one environment variable that tells its own story, REACH_DARK_WAKE_NOTIFY set to TRUE, which is how apsd arranges to be woken in dark wake, the asleep-but-listening state, so that pushes arriving on a closed laptop are noticed rather than parked until morning. iMessage lighting up a sleeping Mac’s screen starts here.

There is one more scheduled habit, visible only in the launch configuration’s event triggers: every 12 hours, with a four hour grace period and a rule that it may only run on mains power, an activity called apptokencleanup runs. Push tokens, the per device addresses Apple’s servers deliver to, go stale; this is the daemon tidying its own address book twice a day, and only when the battery is not paying for it.

The Wi-Fi spender

The strangest strings in the binary are about spending money, or the network’s equivalent of it. One line of code, found in the strings dump, weighs whether to toggle Wi-Fi auto association, and it reads like a committee meeting: highEnoughPushCost, wifiHistoricallyOK, serverLoadIsOK, criticalReliability, serverSupportsDualMode, enableDualMode, isPiggybacking, isWoWEnabled, isUltraConstrained.

Translated: keeping the connection alive has a cost, in Wi-Fi radio time and in battery, and the daemon has a policy engine for deciding when that cost is worth paying, when to piggyback the push connection on other traffic instead of holding a dedicated one, and when the network is constrained enough that it should behave like a metered connection. The logs show the verdicts being handed down as a policy state line, recording whether the Mac is clamshelled, in full wake, in dark wake, whether the power mode is elevated, and something called smartPowerNapeState. If you ever wondered how deep the power management rabbit hole goes, one of its residents is the push daemon, deciding in real time whether your Wi-Fi should stay associated for its sake.

Three receipts from the delivery office

Three more strings, quoted as found, because no paraphrase improves them.

First, the address book: Updating device push token in the keychain. Your Mac’s push token, its address at Apple’s delivery office, is a secret, and it lives in the keychain like one. This is also why apsd occasionally appears in keychain access lists: it has a key to mind.

Second, the duplicate detector: Received duplicate push for per-app token and topic. We already received a message with this payload hash for the device token. Apple’s servers send pushes more than once on purpose, expecting at least one copy to be dropped on a flaky mobile network, and the daemon keeps a hash of what it has already delivered so you see one notification, not three.

Third, the blacklist letter, my favourite string in any daemon so far: ERROR: Push failure: Hardware SerialNumber looks incorrect and caused albert.apple.com to reject the request, push is now disabled. On machines whose serial number does not check out, the activation server named albert refuses to issue push credentials, and the daemon logs it and shuts the whole operation down. There is a version of this page somewhere about a Hackintosh, and it ends at that string.

The neighbourhood

apsd does not display anything itself. When a push arrives, it hands the payload to usernoted, which draws the banner and keeps the list in Notification Center, and to whatever app the topic belongs to. It is a client of mDNSResponder, registering a DNS record for itself that on this Mac lived five minutes 49 seconds at a stretch, and cloud daemons like cloudd watch for its connection flaps because a provider announcing a remote change does so by push. Siri has its own daemon and does not need this one. And Apple’s user documentation, the Get notifications page in the Mac User Guide, describes banners appearing in the top-right corner of your screen without once naming the machinery that carries them. That is the division of labour this whole series keeps finding: the manual pages name the daemons, the user guide names the experience, and the gap between the two is where this site lives.

Is it a virus, and can you quit it

It is Apple’s own code, on the sealed system volume, signed with Apple’s platform identifier, root, parented by launchd, documented since 2009. The verification path is in the FAQ above, along with the simulator wrinkle that makes honest people count three apsds.

Quitting it is similarly covered, but the short version deserves repeating here because it is the punchline of the whole page: you cannot meaningfully quit the thing whose job is to stay, and it costs 38 seconds a day, which is cheaper than the time you would spend fighting it. If push traffic is genuinely bothering you, the fixes are per app and per service in System Settings, upstream of this daemon entirely.

The short version

apsd holds one permanent connection to Apple on port 5223, calls it a courier, and has never hung it up since boot. It bounces nearly half of the processes that knock on its door, checks Apple’s clock every 19 seconds, decides in real time whether keeping your Wi-Fi associated is worth the battery, keeps the device’s push secret in the keychain, deletes duplicate deliveries, tidies its token list twice a day on mains power only, and shuts itself down forever on machines whose serial number Apple refuses. All of that for 38 seconds of processor time a day and 10 MB of memory. It is the cheapest always-on employee on the machine, and it has been on staff since 2009.

How to look at your own

All read only, nothing here changes or quits anything.

The process, its parent, user and cost:

ps -Awwo pid,ppid,user,%cpu,rss,etime,args | grep "[/]apsd"

The permanent line to Apple, in the network table:

netstat -an | grep 5223

The manual page, all eight lines of it:

man apsd

The launch configuration, including the zero-byte gate file:

plutil -p /System/Library/LaunchDaemons/com.apple.apsd.plist
launchctl print system/com.apple.apsd
ls -l /Library/Preferences/com.apple.apsd.launchd

And six hours of its logs, which is where the couriers, the bouncer and the clock all show up. On a busy Mac this produces tens of thousands of lines, so pipe it to a file first:

log show --last 6h --predicate 'process == "apsd"' > /tmp/apsd.txt

Search that file for connectionStatusChange to watch deliveries, for the word entitlement to watch the bouncer work, and for Calculated server time to watch the clock correct itself. If your Mac has been up for weeks, the last of those will almost always read zero, which is a small, satisfying thing to verify.

Questions

What is apsd on Mac?

It is the Apple Push Notification service daemon, the process that keeps a permanent connection open between your Mac and Apple's push servers so that messages, alerts and updates can arrive the moment they happen. Every notification you get from an app that is not running, every iMessage that lands while the lid was closed, every Find My ping: the radio link underneath all of it is held by apsd. Its manual page, apsd(8), has said so since February 2009 in four words and a warning: apsd is the ApplePushService daemon, and users should not run it manually. On the Mac measured here it has held the line open for 27 days straight without ever exiting, at a cost of about 38 seconds of processor time a day.

Why is apsd using CPU or memory?

Some of it is the connection itself. The daemon watches the network path, reconnects when Wi-Fi changes, and recalculates the offset between its clock and Apple's servers, which it did 1,117 times in six hours on this machine, roughly once every 19 seconds. The rest is usually a client, not the daemon: in one six hour window, 51 different processes connected to apsd to send or receive pushes, among them identityservicesd for iMessage, cloudphotod for shared photo updates, appstoreagent for App Store work and [CommCenter](/guides/commcenter-mac) for iPhone call relays. apsd is the switchboard, and a busy switchboard moves when its callers do. The memory figure in Activity Monitor, around 9 to 10 MB here, is the address book of that switchboard: the list of topics every client listens for. It sits flat for weeks at a time, and it fell, not grew, between two samples taken while writing this page.

What is apsd in a router or Wi-Fi settings?

Almost certainly a different thing that happens to share the acronym. In Wi-Fi settings, APSD usually means Automatic Power Save Delivery, part of the WMM power save standard, and you will sometimes see U-APSD, unscheduled APSD, listed per network. That APSD is about a phone or laptop sleeping its radio between beacons to save battery, and it is negotiated between your device and the router. It has nothing to do with the macOS process named apsd, which is Apple's push daemon. If you found this page from a router manual, the setting you are looking at is the Wi-Fi one; if you found it in Activity Monitor on a Mac, the process is the push daemon this page measures.

Is apsd a virus or malware?

No. The copy measured here lives at /System/Library/PrivateFrameworks/ApplePushService.framework/apsd, on the sealed read-only system volume, is signed by Apple with platform identifier 26, runs as root with launchd, process ID 1, as its parent, and was built in September 2026. It also holds a manual page that has been in macOS since 2009. The quick checks if you want to verify a process is the real one: the path must contain ApplePushService.framework, the user must be root, the parent must be launchd. One wrinkle worth knowing before you count processes: if you develop iOS apps, every booted iPhone simulator runs its own copy of apsd under your user account. Three apsds in Activity Monitor on this machine, one from the system and two from simulators, is normal, not an infestation.

Can I quit or disable apsd?

Not really, and the system agrees. The daemon's launch configuration keeps it alive through a gate file whose entire job is to exist, /Library/Preferences/com.apple.apsd.launchd, zero bytes, present on this Mac since the day it was set up, and apsd is one of the few daemons with memory pressure exit explicitly turned off, so launchd will not reclaim it under load. There is no switch in System Settings, because notifications, Find My, iMessage delivery and a fair amount of iCloud all sit on top of it. Force quitting it buys you a second of quiet and then launchd starts it again. The lever that actually exists is upstream, per app: turn off notifications for an app in System Settings, or sign out of the service, and the traffic that would have arrived simply never gets sent. The daemon costs about 38 seconds of CPU a day, which is a price worth knowing before deciding it is the problem.

Ready? Buy Ribbon for $15, or read all the guides.