Pro free for a week: code NETMUTE
NetMute

Two ways to get NetMute

Both are free to download and contain the same features. They differ in how you buy Pro.

Mac App Store

The simple route

  • Pro is bought in the app with your Apple Account
  • No licence key to keep
  • Apple handles payment and refunds
Open the App Store

Direct download

Version 2.3.10 · 13 MB

  • Invoice with VAT ID, ready for expenses
  • 5- and 10-seat licences for teams
  • Unlocked with a licence key
Download the .dmg

The direct build is signed with a Developer ID, notarised by Apple and updates itself. Pro does not carry over between the two: a licence key works only in the direct build, an App Store purchase only in the App Store version.

What Is accountsd on Mac? The Accounts Daemon Explained

accountsd is Apple's accounts daemon, a normal part of macOS that keeps the accounts you add under Internet Accounts (iCloud, Google, Exchange, CalDAV and others) and hands their credentials to apps such as Mail, Calendar and Contacts. It is safe and you should not block it. If it asks to use your login keychain, the usual cause is a keychain password that no longer matches your Mac login password.

8 min readUpdated

What accountsd does

accountsd is the accounts daemon of macOS. Every account you add in System Settings under Internet Accounts, such as iCloud, Google, Microsoft Exchange, Yahoo or a plain CalDAV or CardDAV server, is recorded by accountsd. Every app that wants to use one of those accounts asks accountsd for it.

On macOS 26 the binary sits inside Apple's Accounts framework at /System/Library/Frameworks/Accounts.framework/Versions/A/Support/accountsd. launchd starts it from the launch agent /System/Library/LaunchAgents/com.apple.accountsd.plist, which limits it to graphical login sessions. That is why it runs under your own user name and not as root: each logged-in user gets a separate copy, and it only knows that user's accounts.

The account list itself lives in a database in your home folder, ~/Library/Accounts/Accounts4.sqlite. Support for individual services comes from plug-ins in /System/Library/Accounts, with separate authentication plug-ins for Google, Exchange, Yahoo, iCloud, Game Center and others. Passwords and tokens are kept in the keychain, not in that database.

In practice accountsd works as a gatekeeper. When Calendar, Contacts, Mail or Reminders need to sync, the request goes through accountsd. It checks whether the asking process is entitled to that type of account and, if so, hands over the credentials. The unified log on a test Mac running macOS 26.6 showed both sides of this: dataaccessd (the process that syncs calendars and contacts) receiving credentials, and accountsd turning away other processes that asked for account types they were not allowed to read.

Do not confuse it with three similarly named Apple processes. amsaccountsd handles App Store and Apple Media Services accounts, storeaccountd belongs to the App Store's CommerceKit framework, and appleaccountd in /usr/libexec deals with your Apple Account. All four are legitimate, but they are separate programs with separate jobs.

Why you are seeing it

Most people come across accountsd in one of four places.

Activity Monitor. accountsd appears under your user account. On the test Mac it had been running for more than four days and used about 20 MB of memory and 0.1 percent CPU. It is built to sit idle and wake up when an app needs an account.

A keychain prompt. The dialog "accountsd wants to use the login keychain" is the most common reason people search for the name. It gets its own section below.

A network monitor or outbound firewall. accountsd does go online, but only a little. On the test Mac the unified log showed one HTTPS request roughly every 72 minutes. Each one was requested by dataaccessd and logged by accountsd as a Google access token refresh, and a single request was 444 bytes out and about 1.6 KB back. Accounts that sign in with OAuth, such as Google, work with short-lived access tokens, and accountsd renews them so your calendars and contacts keep syncing. If you have no accounts of that kind, you may see very little traffic from it.

The built-in macOS firewall never asks about accountsd. It filters incoming connections, and accountsd does not listen for any. Only tools that watch outgoing traffic will show it.

High CPU. accountsd is normally close to idle, so sustained CPU use stands out. It usually points to an account that keeps failing to sign in, which the last section covers.

The "accountsd wants to use the login keychain" prompt

The prompt looks alarming, but the cause is usually mundane. Your Mac has a login keychain, a file in ~/Library/Keychains that stores passwords and tokens. It has its own password, which normally matches your Mac login password, so macOS unlocks it automatically when you log in. accountsd reads account credentials from it, and the log shows it using the classic file-based keychain interface that the login keychain belongs to.

When the two passwords drift apart, the keychain stays locked after login, and the first process that needs it asks you to unlock it. accountsd is often first because it serves every app that syncs an account. Typical reasons for the drift are a login password that was reset rather than changed (for example by an administrator or with a recovery key) and a user account that was migrated from another Mac.

To fix it:

  1. Type your current Mac login password into the prompt. If it is accepted and the prompt does not return, you are done.
  2. If it is refused, try your previous login password. If that one works, the keychain still uses the old password.
  3. To fix this for good, open Keychain Access. On recent macOS it lives in /System/Library/CoreServices/Applications, and you can also open it by typing its name into Spotlight. Choose Edit > Change Password for Keychain "login", enter the old password, then set your current login password as the new one.
  4. If you no longer know the old password, the login keychain cannot be unlocked. The way out is a new login keychain, and anything stored only in the old one is lost. Passwords kept in iCloud Keychain return after syncing. Others you will need to enter again.

Dismissing the dialog makes it go away for the moment, but account sync keeps failing and the prompt will come back.

One caution: a genuine keychain prompt is drawn by macOS itself and names the process that asks. If something asking for your password appears inside a web page or an app you do not trust, close it and work from System Settings instead.

Is accountsd malware? How to check it is the real one

No. accountsd is Apple's own code and part of every macOS installation. Checking is still a good habit, because naming malware after a familiar system process is an old trick. Three checks are enough.

The path. In Activity Monitor, double-click accountsd and open the Open Files and Ports tab. The genuine process runs from /System/Library/Frameworks/Accounts.framework/Versions/A/Support/accountsd. That folder is on the sealed, read-only system volume, which other software cannot modify. An accountsd running from your home folder, a Downloads folder or an app's support folder is not Apple's.

The signature. In Terminal, run codesign -dvv /System/Library/Frameworks/Accounts.framework/Versions/A/Support/accountsd. On macOS 26.6 the output includes Identifier=com.apple.accountsd and the authority chain macOS Software Signing, Apple Code Signing Certification Authority, Apple Root CA. TeamIdentifier reads "not set", which is normal for Apple's own system binaries. A third-party developer name, an ad-hoc signature or no signature at all would be a red flag.

The launcher. Run launchctl print gui/$(id -u)/com.apple.accountsd. It should report type = LaunchAgent, the path /System/Library/LaunchAgents/com.apple.accountsd.plist and the program path above. If the process ID it shows matches the one in Activity Monitor, you are looking at the real daemon.

macOS does not ship a man page for accountsd, so man accountsd returning nothing is expected and says nothing about the process.

Should you block it, and what to do about high CPU

You can block accountsd in an outbound firewall, but it rarely helps. Accounts that rely on it can then no longer renew their sign-in. Google calendars and contacts stop syncing once the current token expires, Exchange and other server accounts can fail, and Mail or Calendar may start asking for passwords. Because the iCloud account entry is managed through accountsd as well, iCloud features can be affected too. Your Mac keeps running, but anything tied to an online account becomes unreliable.

If an account is the problem, deal with the account. Open System Settings > Internet Accounts, remove accounts you no longer use, and switch off the parts you do not need, for example contacts or notes on an account you only use for mail. Fewer accounts means fewer requests, and a removed account cannot fail.

High CPU from accountsd usually comes from an account that keeps failing to sign in, so accountsd and the apps that depend on it retry over and over. These steps usually settle it:

  1. If the keychain prompt appears, fix that first, as described above.
  2. In Internet Accounts, look for an account that asks for attention or a password, and sign in again.
  3. If that does not help, remove the account and add it again.
  4. Restart the Mac.

Quitting accountsd in Activity Monitor only helps for a moment. launchd starts it again the next time an app asks for an account.

If you want to see what accountsd and the other background processes send, NetMute lists every app and system process with its live traffic and the domains it contacted. accountsd appears there together with Apple's iCloud sync processes. One switch blocks one entry, so you can take something offline and switch it back on just as quickly.

Frequently asked questions about accountsd

See which processes on your Mac go online

NetMute shows live traffic for every app and system process, lists the domains each one contacted and blocks what you do not want online. Free on the Mac App Store. Pro is a one-time purchase, no subscription.

Free on the Mac App Store

Free with no time limit · Pro $12.99 one-time

Download free