What is osanalyticshelper on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job, scheduled activities and man page checked on macOS 26.3.1.
osanalyticshelper is a macOS helper process that supports writing and reporting analytics and diagnostics, the reports Apple uses to improve its products. It runs briefly when diagnostic reports are created and for scheduled tasks such as submission and cleanup. It is part of macOS and normally uses very little CPU.
osanalyticshelper at a glance
| osanalyticshelper | |
|---|---|
| Made by | Apple (part of macOS, OSAnalytics) |
| Type | System daemon |
| Location | /System/Library/CoreServices/osanalyticshelper |
| Runs as | root |
| Started by | launchd job com.apple.osanalytics.osanalyticshelper |
| Can you quit it? | Yes, but launchd runs it again for its scheduled tasks. |
What is osanalyticshelper?
Its man page says osanalyticshelper "supports writing and reporting analytics and diagnostics. The reports are used by Apple to improve its products." It runs as root from the com.apple.osanalytics.osanalyticshelper launchd job.
That job schedules several background activities on this Mac, whose names describe its duties: com.apple.osanalytics.submissions.submit, com.apple.osanalytics.submissions.cleanup, com.apple.osanalytics.daily.telemetry, com.apple.osanalytics.postboot.telemetry and com.apple.osanalytics.state-monitor. Whether anything is actually sent to Apple depends on your choices in Analytics & Improvements.
Is osanalyticshelper safe?
Yes. It is part of macOS in /System/Library/CoreServices on the read-only system volume and is signed by Apple.
Why does osanalyticshelper use so much CPU and disk?
- New diagnostic reports. Its man page says it supports writing diagnostics, so periods with many crashes or hangs, each of which produces a diagnostic report, give it more to do.
- Scheduled submission and cleanup. Its submit and cleanup activities run in the background on a schedule chosen by macOS.
- After a restart. A post-boot telemetry activity runs after the Mac starts, so a short burst after login is expected.
- Report files. Writing and tidying report files causes small amounts of disk activity.
How much CPU is normal for osanalyticshelper?
Near 0% CPU most of the time, with short bursts after a restart, after crashes, and during scheduled tasks.
How do you stop osanalyticshelper from using so much CPU?
- Look for crashes. Open Console and check Crash Reports and Spin Reports. Frequent new reports keep it busy; fix the app that produces them.
- Choose what is shared. Open System Settings > Privacy & Security > Analytics & Improvements and turn Share Mac Analytics on or off.
- Restart if it never settles. Sustained activity is not expected. A restart starts its scheduled tasks fresh.
When should you worry about osanalyticshelper?
Long periods of high CPU from osanalyticshelper usually follow a burst of crashes or hangs. The reports in Console show which app is responsible.
A copy outside /System/Library/CoreServices would not be Apple's.
How do you check osanalyticshelper in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type osanalyticshelper in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every osanalyticshelper 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 'osanalyticshelper' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
How can Thrum help with osanalyticshelper?
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 osanalyticshelper 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 osanalyticshelper
Does osanalyticshelper send my data to Apple?
It supports reporting, but sending to Apple follows your Analytics & Improvements settings. SubmitDiagInfo's man page says automatic reporting is off unless you opt in.
How is it different from analyticsd?
analyticsd collects diagnostics and usage data locally; osanalyticshelper helps write and report diagnostic reports such as crash and hang reports.
Sources
- osanalyticshelper(8) man page: run man osanalyticshelper in Terminal
- Apple Support: Share analytics information from your Mac with Apple