How to Fix accountsd High CPU Usage on Mac

Hearing your Mac cooling fans spin up to maximum velocity only to discover in Activity Monitor that the process accountsd is consuming 100% to 300% CPU causes battery drain and thermal throttling. The accountsd daemon is a fundamental macOS background service responsible for managing centralized accounts, iCloud synchronization tokens, Mail credentials, and Apple Account authentication handshakes. When an expired token creates an infinite retry loop, local Keychain access permissions become desynchronized, or SQLite database stores inside the Accounts framework become corrupted, accountsd locks into a persistent high-utilization cycle. This guide outlines how to diagnose the runaway process, safely purge corrupted accounts databases, and restore normal CPU temperatures.

What Causes accountsd to Consume Excessive CPU?

The Accounts daemon communicates with multiple local databases and Apple cloud servers:

  • Corrupted Accounts SQLite Database: Damaged index records within Accounts4.sqlite in the user Application Support directory causing database read lockups.
  • iCloud Credential Authentication Loop: An expired password or two-factor authentication token causing the daemon to ping Apple authentication servers repeatedly every few milliseconds.
  • Apple Mail or Calendar Sync Hang: Third-party IMAP/Exchange email accounts or Google calendar accounts failing to complete token verification.
  • Keychain Access Permission Conflicts: Stale security certificates in the macOS login keychain blocking accountsd from reading saved credentials.
  • Spotlight Indexing Contention: Metadata indexing daemons attempting to parse the Accounts database simultaneously while writes are committed.

Method 1: Identify and Force Quit accountsd in Activity Monitor

Terminating the hanging process provides immediate relief while macOS relaunches the daemon with fresh memory handles.

  1. Press Cmd + Space to open Spotlight, type Activity Monitor, and press Return.
  2. Click the CPU tab at the top of the window.
  3. Click the % CPU column header to sort processes in descending order of utilization.
  4. Locate accountsd. Verify whether it is consuming anomalous CPU percentages.
  5. Select accountsd, then click the Stop (X) icon in the top toolbar.
  6. Choose Force Quit.
  7. Monitor CPU activity for 30 seconds. If the daemon restarts and immediately returns to high CPU load, proceed to database remediation below.

Method 2: Sign Out of Apple Account and Re-Authenticate

Re-authenticating your primary Apple Account flushes stale iCloud synchronization tokens across all native applications.

  1. Click the Apple menu in the top-left corner and select System Settings.
  2. Click your Name / Apple Account at the top of the left sidebar.
  3. Scroll down to the bottom of the right pane and click Sign Out.
  4. When prompted whether to keep a copy of your iCloud data (Contacts, Calendars, Safari data) on this Mac, choose Keep a Copy.
  5. Enter your Apple Account password to disable Find My Mac and confirm sign out.
  6. Restart your Mac cleanly (Apple menu > Restart…).
  7. Upon rebooting, open System Settings, sign back into your Apple Account, and complete two-factor authentication.

Method 3: Reset the Corrupted Accounts Database via Terminal

Purging corrupted SQLite accounts cache files forces macOS to generate a clean, unfragmented database.

  1. Open Terminal (Cmd + Space > Terminal).
  2. Stop the daemon process temporarily:
    killall accountsd
  3. Navigate to the hidden Accounts database directory:
    cd ~/Library/Accounts/
  4. Rename the existing database files to create a safe backup while letting macOS recreate pristine stores:
    mv Accounts4.sqlite Accounts4.sqlite.old
    mv Accounts4.sqlite-shm Accounts4.sqlite-shm.old
    mv Accounts4.sqlite-wal Accounts4.sqlite-wal.old
  5. Restart your Mac:
    sudo shutdown -r now
  6. Upon rebooting, macOS automatically initializes fresh Accounts database structures, resolving CPU lockups.

Method 4: Toggle Sync for Third-Party Mail and Internet Accounts

Desynchronized third-party mailboxes or corporate calendars frequently stall the account verification pipeline.

  1. Open System Settings > Internet Accounts.
  2. Select any non-Apple accounts (such as Google, Microsoft Exchange, or Yahoo).
  3. Temporarily disable Mail, Contacts, and Calendars for each account.
  4. Open Activity Monitor and check if accountsd CPU utilization drops to below 1%.
  5. Re-enable services one by one to pinpoint the specific account generating synchronization errors.
  6. If an account triggers the stall, remove it by clicking Delete Account and re-add it cleanly.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.