What is analyticsd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job, man page and settings wording checked on macOS 26.3.1.
analyticsd is the macOS daemon that collects diagnostics and usage data locally, for users who have opted in to sharing analytics. It uses short bursts of CPU as the system records events and when it summarises them. Sending the data to Apple is controlled by Share Mac Analytics in System Settings > Privacy & Security > Analytics & Improvements.
analyticsd at a glance
| analyticsd | |
|---|---|
| Made by | Apple (part of macOS, CoreAnalytics) |
| Type | System daemon |
| Location | /System/Library/PrivateFrameworks/CoreAnalytics.framework/Support/analyticsd |
| Runs as | _analyticsd (a system account) |
| Started by | launchd job com.apple.analyticsd |
| Can you quit it? | Not usefully. launchd restarts it when the system logs analytics events. |
What is analyticsd?
The man page says analyticsd "is a system daemon that collects diagnostics and usage data locally for users that have opted in. There are no configuration options to analyticsd, and users should not run analyticsd manually." It belongs to the CoreAnalytics framework and runs as its own system account, _analyticsd, from the com.apple.analyticsd launchd job.
Collecting and sending are separate: analyticsd gathers data on the Mac, and SubmitDiagInfo sends recent diagnostic information to Apple if you have opted in. Apple's guide says the Console app shows analytics data under Mac Analytics Data even if you did not choose to send reports.
Is analyticsd safe?
Yes. It is part of macOS in a framework on the read-only system volume and runs under a restricted system account. What it shares with Apple is your choice in System Settings.
Why does analyticsd use so much CPU, disk and memory?
- Busy periods on the Mac. It collects diagnostics and usage data as the system runs, so periods with a lot going on, such as the first hours after a macOS update, give it more to do.
- Writing its local store. Collected data is kept on disk; on this Mac its folder is
/private/var/db/analyticsd, owned by the system. - Configuration and pending events. It holds its configuration and pending events in memory. About 7 MB was observed on this Mac.
How much CPU is normal for analyticsd?
Usually near 0% CPU, with short bursts. A burst of a few minutes after a macOS update or a restart is also normal.
How do you stop analyticsd sharing data with Apple?
- Open Analytics & Improvements. Open System Settings > Privacy & Security, scroll down and click Analytics & Improvements.
- Turn off Share Mac Analytics. Turn off Share Mac Analytics to stop sending diagnostics and usage data to Apple. Turn off Share with app developers to stop sharing crash and usage data with developers.
- Review iCloud Analytics. On the same page, Share iCloud Analytics controls analytics of usage and data from your iCloud account.
- See what was collected. Open Console, choose Mac Analytics Data in the sidebar, and read the entries. Entries from SubmitDiagInfo show when data was sent.
When should you worry about analyticsd?
Turning sharing off does not necessarily stop analyticsd from running; it is part of macOS. Sustained high CPU from it for long periods is unusual and worth a restart.
A process named analyticsd outside the CoreAnalytics framework path would not be Apple's.
How do you check analyticsd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type analyticsd in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every analyticsd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'analyticsd' | grep -v grep
sudo fs_usage -w -f filesys analyticsd
How can Thrum help with analyticsd?
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 analyticsd 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 analyticsd
Does turning off Share Mac Analytics stop analyticsd?
It stops sending analytics to Apple. The daemon is part of macOS and may still run; its man page describes local collection for users who have opted in.
What is in Mac Analytics data?
Apple's setting text says it is diagnostics and usage data and that diagnostic data may include locations. Console's Mac Analytics Data view shows the actual entries.
Sources
- analyticsd(8) man page: run man analyticsd in Terminal
- Apple Support: Share analytics information from your Mac with Apple