accountsd high CPU on Mac? A stuck account, usually

accountsd is the Accounts daemon that manages your internet accounts and keeps them available to apps. High CPU almost always means it's stuck in a broken sync loop with one account. The good news: it's usually a single offending account, so it's findable.

What accountsd does

It powers Apple's Accounts framework, which lets apps "access and manage external accounts without requiring you to enter login credentials." It stores and coordinates your internet-account definitions (iCloud, Mail, Contacts, Calendar, Google, Exchange, and the like) in ~/Library/Accounts/, and makes them available to the apps that need them.

Why it's using high CPU

The classic cause is a broken sync or authentication loop: accountsd repeatedly, and unsuccessfully, trying to reconcile an account with iCloud or a mail provider. It surged for many users after macOS Catalina 10.15.7 (reports of 400–500% CPU), typically tied to a specific iCloud or Mail account with an expired or stuck credential.

Is accountsd a virus?

No. It's a legitimate Apple process that must run in the background for account features to work. High CPU is a bug or a stuck state, not malware.

What to do about it (escalating)

1. Restart first: it clears many transient loops.
2. Sign the problem account out and back in. For iCloud: System Settings → Apple ID → Sign Out (then back in). For others: remove and re-add the specific account under System Settings → Internet Accounts.
3. Isolate the offender. Since it's usually one bad account, toggle off individual iCloud services (Contacts, Calendar) or remove accounts one at a time until the CPU drops, which identifies the culprit. Broken mail/iCloud auth is a common cause, related to iCloud sync high CPU.
4. Boot into Safe Mode to rule out other software, and update macOS; a point-release fixed this for many after the Catalina bug.

What people get wrong

You'll see advice to rename or delete Accounts4.sqlite in ~/Library/Accounts. It can work, but it wipes your local account state and affects your ability to log into iCloud; you'll have to re-add every account. That's a last resort, done with a backup, not step one. Removing accounts one at a time to isolate the bad one is both safer and more informative.

Find the account behind the loop

An account stuck retrying in the background is invisible until your fans spin up. Plumby shows live CPU in your menu bar with the process named plainly, so accountsd grinding away reads as what it is, a stuck account sync, letting you act instead of wondering. Measured from your Mac's real state, and nothing about your machine ever leaves it.