apsd on Mac: what the push notification daemon does and why it is busy

What apsd does

apsd stands for Apple Push Service daemon. It is the part of macOS that keeps a single, always-on connection to Apple's push notification servers, the same APNs service that iPhones and iPads use. Instead of every app on your Mac polling Apple on its own schedule, apsd holds one connection and hands out whatever arrives: a new iMessage, an incoming FaceTime call, a change to an iCloud note or calendar, a Mail push for iCloud accounts, a Find My request, and notifications from any Mac App Store app that supports them.

It lives inside the ApplePushService framework at /System/Library/PrivateFrameworks/ApplePushService.framework/apsd, runs as root, and is launched by the system at boot. Because so much of the Mac's "things just appear" experience depends on it, Apple protects it: System Integrity Protection stops you from unloading it, and if it is killed it comes straight back.

Most of the time the connection is idle. The daemon wakes when a push arrives, delivers it to the right app, and goes back to waiting. That is why, on a healthy Mac, apsd sits at the bottom of Activity Monitor with a CPU figure of 0.0 and a memory figure of a few tens of megabytes.

What normal looks like

The pattern to expect is long stretches of nothing with short, sharp bursts. The bursts line up with moments when apsd has to re-establish its connection and catch up on anything it missed:

A reader on a Mac user group forum described the normal spike exactly: apsd jumps to the top of the CPU list for a moment after startup and then drops back to nothing. A regular there confirmed that this is expected, since the daemon is contacting Apple to see what notifications are waiting. Memory should stay in the tens of megabytes. Reports of apsd holding gigabytes are almost all from older macOS versions running in virtual machines, and they went away with updates.

Why apsd is using CPU right now

When apsd is busy, it is almost always because its connection to Apple keeps breaking and it keeps rebuilding it. Work through these in order:

1. You just logged in, woke the Mac, or changed networks. This is the built-in spike. Give it a minute before doing anything.
2. A VPN is dropping and reconnecting. Every time the VPN tunnel goes up or down, the Mac's network path changes and apsd has to reconnect. Some VPN clients also block or slow the ports apsd uses, so the connection never settles. Turning the VPN off for ten minutes is the quickest test.
3. Wi-Fi is roaming or weak. A laptop on the edge of two access points, or on a mesh network that hands it between nodes, triggers the same reconnect over and over.
4. A captive portal or proxy is in the way. Hotel and office networks that intercept traffic can leave apsd half-connected, retrying forever until you sign in to the portal.
5. A stale push state after an update. Rarely, after a macOS update, apsd gets into a loop that only a restart clears. Several Apple Community threads end this way.

What it is not: apsd is not malware, not a sign someone is watching you, and not something a cleaner app can fix. It is one of the most ordinary processes on the Mac.

Is it safe to quit apsd?

You cannot really quit it, and you should not try. apsd runs as root under the protection of System Integrity Protection. Activity Monitor will let you force quit it, and it will relaunch within seconds and reconnect to Apple, which is the same work you were trying to stop. One Apple Community poster who did exactly that found the process came back and, after a day, "is running as one would expect a background process," which tells you the restart of the daemon did nothing the next reboot would not have done anyway.

Unloading it with Terminal commands is blocked on modern macOS, and on older systems it silently breaks iMessage, FaceTime and iCloud sync until you undo it. There is no setting that turns apsd off, because there is no sensible Mac without it.

Type any process name above to get the same plain-English verdict. For apsd it will always say the same thing: leave it, fix the network.

What to do, in order

1. Wait one minute

   If you just logged in, woke the Mac or joined a network, the spike is apsd reconnecting. It should be back to 0 percent before you finish reading this.

2. Turn the VPN off, then on

   If you run a VPN, disconnect it and watch apsd for a few minutes. If it calms down, the VPN was breaking the push connection. Reconnect and see whether it stays calm; if not, check the VPN app for a "split tunneling" or "allow Apple services" option.

3. Rejoin the Wi-Fi

   Open System Settings, click Wi-Fi, click Details next to your network and choose Forget This Network. Then join it again. This clears a stuck lease or captive portal state in one go.

4. Sign out and back in to iMessage or iCloud

   If notifications are also missing or late, open Messages, go to Settings, iMessage, and sign out and in. apsd re-registers with Apple when you do. Only do this if the network steps did not help.

5. Restart the Mac

   A restart is the one reliable fix for a daemon stuck in a bad state. If apsd is pinned again within an hour of restarting with no network changes, the problem is upstream: a router, a DNS filter, or a security tool that is interfering with Apple's push ports.

When to worry

Almost never. apsd using CPU costs you some battery while it retries, and in the worst case delays your messages, but it does not damage anything. The one real signal is time. Here is how long each state is allowed to last:

The hard part is noticing whether it is bursting or stuck when you only glance at Activity Monitor once. Safe to Quit watches each process over hours and tells you whether it settled on its own, which is usually the whole answer for apsd.