Thrum

What is symptomsd on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.

symptomsd is an Apple daemon that provides services for the Symptoms framework, part of macOS's network monitoring. launchd starts it when the network changes, when apps are installed or removed, and for a daily maintenance task. It runs as a restricted system account and normally uses very little CPU.

symptomsd at a glance

symptomsd
Made byApple (part of macOS, Symptoms framework)
TypeSystem daemon
Location/usr/libexec/symptomsd
Runs as_networkd (a system account)
Started bylaunchd job com.apple.symptomsd
Can you quit it?Not usefully. launchd starts it again on the next network change.

What is symptomsd?

The man page describes symptomsd only as the daemon that provides services for the Symptom Framework, with no configuration options. Apple does not document the framework publicly. On macOS 26 the Symptoms frameworks sit beside related private frameworks named SymptomNetworkDiagnostics and SymptomReporter, and symptomsd runs as _networkd, the account macOS uses for network services.

Its launchd job shows what wakes it: the system's network-change notification, apps being registered or unregistered with Launch Services, a daily maintenance activity, and changes to /Library/Preferences/com.apple.symptoms.plist. This page describes those triggers and does not guess beyond them.

Is symptomsd safe?

Yes. symptomsd lives in /usr/libexec on the read-only system volume and runs as the _networkd system account, not as root.

Why does symptomsd use so much CPU?

How much CPU is normal for symptomsd?

Typical use is near 0% CPU, with short bursts after network changes and app installs.

Sustained CPU use is not typical and usually lines up with a network that keeps changing.

How do you stop symptomsd from using so much CPU?

  1. Stabilize the network. If Wi-Fi keeps reconnecting, fix that first: move closer to the router, forget unused networks, or try Ethernet. Fewer network changes mean fewer wake-ups.
  2. Check VPN and network tools. Quit VPNs, virtual machines and network utilities one at a time to see whether one of them is causing frequent changes.
  3. Restart the Mac. If symptomsd stays busy on a stable network, a restart resets it.

When should you worry about symptomsd?

symptomsd using CPU for hours on a stable network is not typical; restart once and see whether it returns. A copy outside /usr/libexec would not be Apple's.

How do you check symptomsd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type symptomsd in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every symptomsd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'symptomsd' | grep -v grep

How can Thrum help with symptomsd?

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 symptomsd 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 symptomsd

Can I disable symptomsd?

No. It is protected by System Integrity Protection, and launchd starts it on demand.

Does symptomsd send data to Apple?

Apple does not document what symptomsd records. Whether a Mac shares analytics with Apple is controlled in System Settings > Privacy & Security > Analytics & Improvements.

Sources