# accountsd, the receptionist for every account

> accountsd manages every internet account on your Mac. Measured: a plugin registry naming Google, Exchange and iMessage, and the login keychain prompt it owns.

Source: https://www.ribbonmac.com/guides/accountsd-mac · Updated 2026-11-19

Open Activity Monitor on a quiet Mac and page down to the a's, and there it is near the top of the alphabet: accountsd, a few megabytes of memory, no CPU to speak of, running as you. The name is almost aggressively vague. Accounts. Of what, for whom, and why does it never stop running?

So here is what it actually is, measured on a Mac that has carried the same accounts for 28 days without a single restart of the process. The short answer: it is the receptionist for every account you have ever signed into on this machine, and most of the strange prompts people blame on their browser or their mail app are this daemon doing its rounds.

## The receipts

The process on the measured Mac, macOS 27.0.1 on a MacBook Pro:

| What | Measured |
|---|---|
| Path | /System/Library/Frameworks/Accounts.framework/Versions/A/Support/accountsd |
| Size | 262,816 bytes, built 24 September, signed as a platform binary |
| Architectures | x86_64, arm64e and arm64e.x1 in one file |
| User | Your user account, not root |
| Parent | launchd, always, process 1 |
| Running | 28 days without exiting, one launch in total |
| Processor time | 3 minutes 23 seconds over 28 days, about seven seconds a day |
| Memory | 6 MB resident, two threads when idle |
| Manual page | None. The closest thing to documentation is the framework it lives in |

It is a launch agent, not a launch daemon, which is the first useful fact about it: it runs as you, in your graphical session, because your accounts are yours. The configuration file at /System/Library/LaunchAgents/com.apple.accountsd.plist starts it in every Aqua session, hands it a five second exit timeout and a ten second minimum runtime, and registers two Mach services, the ports the rest of the system knocks on: com.apple.accountsd.accountmanager, the database counter, and com.apple.accountsd.oauthsigner, the token counter.

There is also a line in the launch file that is easy to skim past and tells you how deep this daemon sits in the furniture: it registers for the didActivateNotification event on its own notifications. When the system shows an account alert and you click it, launchd wakes accountsd to handle the click. The daemon receives its own mail.

## What it actually manages

Here is the part almost nobody gets to see, and it is readable on any Mac with one command, because the daemon keeps its own plugin registry in plain preferences. `defaults read com.apple.accountsd` returns a dictionary called AuthenticationPluginCache, and it is the staff directory for the whole operation:

| Account type | Plugin that handles its sign-in |
|---|---|
| AppleAccount (iCloud) | iCloudIDAuthentication.bundle |
| Apple ID single sign-on | AppleIDSSOAuthentication.bundle |
| Google | GoogleAuthenticationPlugin.bundle |
| Exchange | ExchangeAuthenticationPlugin.bundle |
| CalDAV calendars | DAAccountAuthenticator.bundle |
| CardDAV contacts | ContactsAccountsAuthenticationPlugin.bundle |
| IMAP, POP, SMTP | EmailAuthenticationPlugin.bundle |
| FaceTime, iMessage, Identity Services | AAIDSAuthentication.bundle |
| Game Center | iCloudIDAuthentication.bundle |
| CloudKit | CloudKitAuthenticationPlugin.bundle |
| LDAP directories | ContactsAccountsAuthenticationPlugin.bundle |

Read that as a list of promises. Every account type your Mac knows how to add in System Settings has a matching row here, and every row is a bundle of sign-in code that accountsd loads on demand. When you add a Google account, it is not Mail or Calendar talking to Google. They talk to accountsd, which loads the Google plugin, runs the sign-in, and stores the result.

The framework's own dialogue is on disk too, in a localisation file with nine English strings, and they read like the transcript of your worst week with iCloud. One is the permission dialog text, a format string that fills in an app name and an account type: would like access to your accounts, with buttons for Continue, Don't Allow and OK. Another is titled Verification Required, with the line: log in to your account. A third is an error that explains a rule you have probably hit without knowing its name: an account of this type already exists, and only a single one is allowed to be saved. That is why your Mac will not let you add a second iCloud account, phrased in the daemon's own words.

Apple's developer documentation for the framework is still online, and its opening sentence for the central class is as clean a summary as any: ACAccountStore is the object you use to request, manage, and store the user's account information. The same page carries a deprecation notice telling new apps to use each account type's own SDK instead, which tells you something about the direction of travel: the framework is legacy for third-party developers, but the daemon underneath it still carries every account on the system, because Apple's own apps never left.

## The keychain prompt, explained properly

This is the reason most people end up searching the name. The search box autocompletes accountsd wants to use login keychain before you finish typing it, which tells you how many people have met this prompt.

The mechanics are not mysterious. Your login keychain, the default one in Keychain Access, is encrypted with a key derived from your login password. accountsd keeps its tokens and passwords inside it, and the daemon that guards the vault and runs every lookup is [secd, the keychain daemon](https://www.ribbonmac.com/guides/secd-mac), which this same machine measured answering 85 database queries in 45 minutes, 86 percent of them from a single office suite. Most password changes update the keychain's encryption at the same time, and you never notice a thing. But when the change arrives by a route that does not, a forced reset, an admin change from another account, some directory policy flows, the keychain keeps its old key, and now the items inside it are locked behind a password that no longer matches your login.

Every process with items in the login keychain then starts asking to be let in, and accountsd asks loudest, because it holds tokens for all of your accounts at once. The prompt names it because it is the process doing the asking, not because it did anything wrong.

The fix is two clicks: when the prompt appears, enter your current login password, and choose Always Allow rather than just Allow. Allow answers the question once; Always Allow re-trusts the daemon, and the prompt retires permanently. If it comes back after every reboot, the account behind it has a half-broken token, and the clean fix is to sign that account out in Internet Accounts or iCloud settings and sign back in. The sign-in rewrites the token under the new password, which is the operation the prompt was trying to avoid.

## The visitor's book

A day of the daemon's log, on a Mac doing nothing in particular, is a census of everything in the system that needs an account. Over 24 hours it wrote 2,195 lines, and the great majority are handshakes, a client connecting, asking its question, disconnecting. The top callers, counted from the log itself:

| Caller | Visits per day | Why it calls |
|---|---|---|
| amsaccountsd, the App Store's account agent | 58 | store sign-ins, purchases, receipts |
| cloudd, the iCloud transfer daemon | 34 | reading the iCloud account it works for |
| identityservicesd, the identity daemon | 24 | vouching that this Mac is really yours |
| contactsd, the contacts daemon | 16 | CardDAV and iCloud contacts |
| suggestd, search | 4 | account-scoped suggestions |
| searchpartyuseragent, Find My | 4 | the Find My account |

If you have read the other pages in this series, that table is the payoff: the iCloud daemon, the identity daemon, the contacts daemon, all of them clients of this one. The account daemon sits one layer below the services you can see, which is why it never appears in a settings pane but appears in every crash log.

## The database you are not allowed to read

The accounts themselves live in a folder in your own Library: ~/Library/Accounts. It is your folder, in your home directory, holding your accounts. Try to list it from the terminal and the system refuses: Operation not permitted. It holds a handful of items, and is walled off by data protection, readable only by processes granted Full Disk Access, which is a short list that does not include your terminal by default.

The folder's date is its own small piece of evidence: 20 October at 12:57, which on this Mac is five minutes after the current macOS version finished installing. The accounts database is rewritten as part of an OS update, accounts re-registered under the new system, which is also why the daemon's preferences file carries the same minute.

That wall is the honest answer to the spyware question. The daemon that everyone suspects of hoarding account data stores it in a database the system will not let you casually read, and when an app wants at it, the framework shows a dialog with your two options printed on it. Whatever else you might say about the arrangement, it is not covert.

## The twin with the longer name

Open Activity Monitor, type account in the filter box, and on many Macs two rows survive. The second is amsaccountsd, out of the AppleMediaServices framework, and the m-s in its name stands for media services: it is the App Store's own account handler, the one that knows your purchase history. It is a separate launch agent with its own life, nine launches in the same 28 days on the measured Mac, reclaimed by the memory compressor between jobs, and its favourite activity is calling the main accountsd, 58 times in the day counted above. A purchase is an account event, and account events belong to the account daemon.

There is a third class of almost-twins worth naming for developers: Xcode's simulators run their own copies of accountsd inside each iOS runtime, paths running through the simulator runtime mounts. They belong to the simulated phones. If you are ever unsure which row is the system's, click the row, press Command-I, and read the path: the real one starts with /System/Library/Frameworks/Accounts.framework.

## What it costs

Seven seconds of processor time a day, six megabytes, two threads, one launch in 28 days. That puts it in the cheap band of every daemon measured in this series, a little above the App Store agent's five seconds and the phone call daemon's two. There is no switch to turn it off, no reason to look for one, and the only maintenance it ever needs is the two-click answer to the one prompt it is famous for.

If accountsd is ever the name in your CPU column, remember what it is: a receptionist with a phone that will not stop ringing. The fix is never to fire the receptionist. It is to quiet the account on the line, in Internet Accounts, one re-entered password at a time.

## FAQ

### What is accountsd on my Mac?

It is the process that stores and manages every internet account signed in on your Mac: iCloud, Google, Exchange, CalDAV calendars, CardDAV contacts, IMAP mail, LDAP directories. It lives inside the Accounts framework at /System/Library/Frameworks/Accounts.framework, runs as your user account from the moment you log in, and offers two services to the rest of the system through Mach ports: an account manager and an OAuth signer. Every app that shows your Google calendar or your work contacts is reading them through this one process. It is signed by Apple on the sealed system volume, it has run once and never exited on the measured Mac, and it is not malware. There is nothing to remove and nothing you need to do about it.

### Why does accountsd want to use the login keychain?

Because that is where it keeps the tokens. accountsd stores each account's authentication tokens and passwords in your login keychain, which is encrypted with your login password. When you change that password by a route that does not also update the keychain, say a forced password policy or an admin reset, the keychain keeps its old encryption key and every process with tokens inside it starts asking to be let back in. That is the whole prompt: accountsd wants to use the login keychain. Click Always Allow, give it your current login password when asked, and the asking stops for good. If the prompt returns every reboot, the cleaner fix is to sign out of the complaining account in Internet Accounts or iCloud settings and sign back in, which rewrites the token under the new password.

### Why is accountsd using so much CPU?

On the measured Mac it was not: 3 minutes 23 seconds of processor time across 28 days of running, about seven seconds a day, with 6 MB of memory and two idle threads. But the search rows for accountsd high cpu are real, and the mechanism is simple: when one account's token is rejected, the account can re-authenticate in a loop, and every attempt passes through this daemon. The fix ladder, in order: open Internet Accounts in System Settings and look for the account with a warning badge asking you to re-enter its password, and re-enter it. If none shows, sign the noisy account out and back in. A restart of the Mac clears the loop's state but not its cause. The daemon itself is cheap; a stuck account is what makes it expensive.

### Why are there two accountsd processes on my Mac?

The second one is probably not a second one at all. The App Store runs its own account daemon, amsaccountsd, out of the AppleMediaServices framework, and its name is close enough to confuse anyone; on the measured Mac it called the main accountsd 58 times in one day, because store sign-ins are still accounts. If you develop with Xcode, you may also see extra copies of accountsd whose paths run through the iOS simulator runtimes; those belong to simulated phones, not your Mac. The reliable test is the path: the real one starts with /System/Library/Frameworks/Accounts.framework. Anything through a simulator runtime or a cryptex mount is not the system daemon.

### Can I quit or disable accountsd?

No, and there is nothing to win. It is a launch agent with no off switch in System Settings, and if you kill it, launchd starts it again; its configuration even includes a minimum runtime of ten seconds, the system telling it not to flap. Quitting it would break every signed-in account at once: mail, calendars, contacts, iCloud Drive sign-in state, all of which read through this process. The honest advice is the boring kind: it costs about seven seconds of processor time a day and 6 MB of memory, which is to say, leave it alone. If it is misbehaving, fix the account, not the daemon.

### Is accountsd a virus or spyware?

No. It is part of macOS, on the sealed system volume, which cannot be modified without breaking the boot-time seal. The name shows up in virus searches for the same reason every system process does: people see an unfamiliar name in Activity Monitor, type the name plus the word virus, and the search box autocompletes the fear. The accounts it manages are the ones you signed into yourself, its database in your own Library folder is walled off even from your own terminal without Full Disk Access, and every app that wants at those accounts has to show a dialog whose text lives in the framework itself: an app would like access to your accounts, with a Don't Allow button. That is the opposite of how spyware behaves.
