Thrum

What is calaccessd, and why is it using CPU on my Mac?

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

calaccessd is the macOS calendar data process: it coordinates access to your calendar data for the Calendar app and other apps, and posts calendar notifications. It is busy when calendars change, when apps read many events, and during its maintenance tasks. It is part of macOS and safe.

calaccessd at a glance

calaccessd
Made byApple (part of macOS, Calendar)
TypeLaunch agent (background process for your user)
Location/System/Library/PrivateFrameworks/CalendarDaemon.framework/Support/calaccessd
Runs asyour user
Started bylaunchd job com.apple.calaccessd
Can you quit it?Not usefully. launchd starts it again as soon as an app reads calendar data or an alert is due.

What is calaccessd?

Its man page describes calaccessd as the calendar data process, used to coordinate access to calendar data and to post calendar notifications, with no options. Apps that use Apple's EventKit framework to read or change events go through it, and its launchd job also offers the services com.apple.CalendarAgent (the name of the older calendar process) and a Spotlight feed for calendar items.

launchd wakes it when the calendar database changes, when the time zone or clock changes significantly, when reminders change and when calendar settings change. It also has maintenance tasks for database, change history and attachment cleanup.

Is calaccessd safe?

Yes. It is in the CalendarDaemon framework on the read-only system volume and runs as your user.

Why does calaccessd use so much CPU and disk?

How much CPU is normal for calaccessd?

Short activity when calendars sync or alerts fire is normal. With nothing changing it typically sits near 0% CPU.

How do you stop calaccessd from using so much CPU?

  1. Find the app asking for events. In Activity Monitor, see whether Calendar, a widget or a third-party calendar app is active at the same time as calaccessd.
  2. Remove subscribed calendars you do not need. Subscribed calendars that refresh often, with many events, keep the database changing. Remove them in Calendar.
  3. Check accounts for errors. In System Settings > Internet Accounts, fix or remove calendar accounts that cannot sign in.
  4. Restart the Mac. A restart clears any app stuck in a loop of calendar requests.

When should you worry about calaccessd?

Look closer if calaccessd uses CPU continuously for hours. Quitting third-party apps that read calendars, one at a time, usually identifies the cause.

How do you check calaccessd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type calaccessd 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 calaccessd 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 'calaccessd' | grep -v grep
sudo fs_usage -w -f filesys calaccessd

How can Thrum help with calaccessd?

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

What is the difference between calaccessd and dataaccessd?

calaccessd manages calendar data on the Mac and its notifications; dataaccessd syncs calendar data with calendar servers.

Is calaccessd the same as CalendarAgent?

Its launchd job registers the service name com.apple.CalendarAgent, the name used by the calendar process on older versions of macOS. On macOS 26 the process you see is calaccessd.

Sources