What is UsageTrackingAgent, and why is it running on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job, scheduled activities and man page checked on macOS 26.3.1.
UsageTrackingAgent is the macOS agent that, according to its man page, monitors and reports the limits set by Screen Time, such as App Limits and Downtime. It runs in short scheduled bursts to collect device activity and reset limit timers, and it normally uses very little CPU. If you do not use Screen Time limits, turning them off leaves it almost nothing to do.
UsageTrackingAgent at a glance
| UsageTrackingAgent | |
|---|---|
| Made by | Apple (part of macOS, Screen Time) |
| Type | Launch agent |
| Location | /System/Library/PrivateFrameworks/UsageTracking.framework/Versions/A/UsageTrackingAgent |
| Runs as | your user |
| Started by | launchd job com.apple.UsageTrackingAgent |
| Can you quit it? | Yes. launchd starts it again for its scheduled tasks and when Screen Time limits need checking. |
What is UsageTrackingAgent?
Its man page describes UsageTrackingAgent as the agent that monitors and reports limits set by Screen Time. Its launchd job registers scheduled background tasks named device-activity-collection, reset-device-activity-alarms and uncategorized-web-usage (each prefixed com.apple.UsageTrackingAgent.activity), which macOS runs when it chooses.
launchd starts it for your user through the com.apple.UsageTrackingAgent job, so it runs only when one of those tasks or a Screen Time check needs it. Screen Time's reports and data cleanup belong to its sibling, ScreenTimeAgent.
Is UsageTrackingAgent safe?
Yes. UsageTrackingAgent is part of macOS, signed by Apple, and lives in /System/Library/PrivateFrameworks/UsageTracking.framework on the read-only system volume. It runs as your user.
Why does UsageTrackingAgent use so much CPU?
- Device activity collection. The scheduled collection task gathers how long apps and websites have been used, so that limits can be checked against it.
- App Limits and Downtime. With App Limits or Downtime on, usage has to be compared with the limits and alarms reset as days and schedules change.
- Website usage. A separate task handles web usage that has not yet been sorted into a category, so heavy browsing gives it more to process.
How much CPU is normal for UsageTrackingAgent?
Absent or near 0% CPU most of the time, with short runs when its scheduled tasks fire, typically after login, after waking, and around Downtime or limit boundaries.
Memory use is typically in the tens of megabytes while it runs.
What can you do if UsageTrackingAgent keeps running?
- Turn off limits you do not use. Open System Settings > Screen Time and turn off App Limits and Downtime if you do not need them.
- Turn off App & Website Activity. If you do not use Screen Time at all, turn off App & Website Activity in Screen Time settings. That stops usage tracking.
- Give it a few minutes after login. Short activity right after login or wake is its scheduled work catching up; it stops on its own.
When should you worry about UsageTrackingAgent?
Look closer if UsageTrackingAgent stays above a few percent CPU for many minutes with Screen Time off. A restart of the Mac normally clears it.
It should run only from the UsageTracking framework path above.
How do you check UsageTrackingAgent in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type UsageTrackingAgent 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 UsageTrackingAgent process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'UsageTrackingAgent' | grep -v grep
How can Thrum help with UsageTrackingAgent?
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 UsageTrackingAgent 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. Click UsageTrackingAgent in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
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 UsageTrackingAgent
What is the difference between UsageTrackingAgent and ScreenTimeAgent?
Both serve Screen Time. UsageTrackingAgent's man page says it monitors and reports Screen Time limits; ScreenTimeAgent supports Screen Time more generally, including usage collection, analytics and cleanup.
Does a parent's Screen Time setup use UsageTrackingAgent?
Limits set for a child's account are Screen Time limits, which is what UsageTrackingAgent monitors on the child's Mac.
Sources
- UsageTrackingAgent(8) man page: run man UsageTrackingAgent in Terminal
- Apple Support: Set up Screen Time for yourself on Mac