contactsd, the daemon that minds everyone you know
contactsd is the daemon behind the Contacts app on macOS. Measured live: its hidden contact database, its nightly maintenance jobs, and when it runs hot.
By Chethan Kumar S N · Updated
Contactsd is the process that minds your contacts when no app is open. Every entry in the Contacts app, every phone number an app looks up through the system API, every account that syncs contacts from iCloud or Exchange or Google, all of it flows through one quiet daemon whose name shows up in Activity Monitor with no explanation: contactsd.
It has something most of its sibling daemons do not, which is a proper manual page. contactsd(8), dated January 2022, says the whole job in two lines: contactsd manages the information in your contacts database, it provides functionality to apps using the Contacts API, and it performs various background maintenance tasks. This command is not intended to be invoked directly. That last sentence is the only instruction Apple gives, and it is the correct one.
The page that follows measures the daemon the way the other pages in this series do: nothing installed, nothing written, every fact read off a stock Mac running macOS 27.0.1 on Apple silicon.
A daemon that runs as you
Most of the scary sounding daemons in Activity Monitor run as root. contactsd does not. On the measured Mac it runs as the logged-in user, PID 35386, parented by launchd at PID 1, from this path:
/System/Library/Frameworks/Contacts.framework/Support/contactsd
The location is worth a second look. This is not a PrivateFrameworks daemon hidden away from developers. It ships inside the public Contacts framework, the same framework any Mac app links against to look up a phone number, in a Support folder one level down. The daemon and the API are the same citizen, which matches the manual page’s claim that it exists to serve apps.
The binary is 1,300,496 bytes, a universal slice carrying x86_64, arm64e and arm64e.x1, signed by Apple on 9 August 2026 with platform identifier 26. It is a thin front door: just 1,548 strings inside, with the real machinery in the Contacts and AddressBookCore frameworks beside it. If you spot two more contactsd processes with hundreds of kilobytes or tens of megabytes of memory, look at the full path before worrying. On a Mac with iOS simulator runtimes installed, each runtime carries its own copy of the whole Contacts framework, so two extra contactsd processes come along for the ride. The same triple shows up on this machine for apsd, usernoted and logd.
The footprint is the smallest measured in this series so far. 3.3 MB of resident memory, about thirty one seconds of processor time per day, and 0.0 percent in the CPU column at the moment of sampling. For six straight hours around the writing of this page, the unified log recorded not a single line from the process. When your contacts are not changing, contactsd is not just quiet. It is silent.
The schedule only the plist knows
contactsd does not idle randomly. Its launch dictionary, readable at /System/Library/LaunchAgents/com.apple.contactsd.plist, encodes three maintenance jobs and a set of triggers, and the gates on each job explain when you might see the daemon stir.
The first job, com.apple.private.contacts.accounts.validate-cache, is a repeating system task on a 24 hour interval with three conditions attached: RequiresExternalPower, RequiresUserInactivity, and ShouldWakeDevice. It wants your Mac plugged in, asleep or idle, and it is allowed to wake the machine to get its work done. The second and third are XPC activities, com.apple.contactsd.accounts.cleanup and com.apple.contactsd.VerifyCoreSpotlightService, both repeating daily, both with RequireScreenSleep set and AllowBattery false. Your contact accounts get tidied, and their contribution to the Spotlight index gets verified, while the screen is off and the charger is connected.
That last job is the quiet answer to a question people ask about Spotlight: how do my contacts get into search? The metadata server builds the index, but contactsd is scheduled to verify its slice of it nightly. Contacts feed Spotlight, and the daemon that owns contacts is on the hook for keeping that feed honest.
The dictionary also sets LimitLoadToSessionType to Background and ProcessType to Adaptive, which has a consequence worth knowing: the job does not even live in the graphical session domain launchctl prints by default. Asking for it under gui/501 comes back with could not find service. It lives one domain over, under user/501, where a plain query shows the behaviour:
state = running
runs = 20
minimum runtime = 10
immediate reason = ipc (mach)
monitor = com.apple.dasd
Twenty runs means twenty lives. The daemon exits, or is reclaimed, and launchd starts it again, on a machine that has been up for twenty seven days without a reboot. The immediate reason for the current life is a Mach message, which is the general shape of contactsd’s existence: apps and system services send it work through six named front doors, and it does the work in process.
The library it keeps
contactsd is the manager of a library most Mac users have never seen. The library has two rooms.
The first is the account registry, a 76 KB SQLite file at ~/Library/Contacts/accounts.accountdb, which stays small because it holds accounts, not people. Beside it sits a 220 byte plist called iOSLegacyIdentifierSequences, a file whose entire job is keeping identifier numbers straight across a migration from iOS. Names like that are how you can tell a data format has been through a few decades.
The second room is the store itself, under ~/Library/Application Support/AddressBook. An aggregate file, AddressBook-v22.abcddb, 475,136 bytes on this Mac. Then a Sources folder with one subfolder per sync account, each named after a UUID, each holding its own AddressBook-v22.abcddb alongside the write-ahead log and shared-memory files that SQLite uses. The measured Mac has exactly one source store, 757,760 bytes, with a 3.9 MB WAL file beside it, which is the honest tell of an active database: the log of pending changes is five times the size of the committed file, because the daemon checkpoints on its own schedule, not yours.
The abcddb files are SQLite databases driven through Core Data, and the framework ships the proof beside the binary: a model file named CNContactMetadata.momd sits in the Contacts framework’s own Resources folder. The daemon holds all of these files open continuously. Ask it directly with lsof and it will show you the aggregate store, the per-source store, the account registry, and the logs, all mapped at once.
You can see the edges of this library but you cannot walk into it. Listing the AddressBook folder from a terminal returns Operation not permitted. Opening the database file with sqlite3 returns authorization denied. stat on the exact file path still reports its size and its dates, which on this Mac reach back to setup day. This is the privacy layer doing its job: the contacts database is protected from every process that has not been granted access, and the terminal, despite being yours, is one of them. It is the same wall the Photos library has, and it is why guides that tell you to just delete the abcddb files are telling you something your own Mac will not let you do.
The persistence cluster
Ask Google about com.apple.contactsd and the autocomplete adds one word: persistence. It is the one part of the daemon people search for by service name, and the reason is sitting in plain sight in the launch dictionary. Of the six Mach services contactsd answers, one is literally named com.apple.contactsd.persistence. The full list:
com.apple.AddressBook.ContactsAccountsService
com.apple.askto.client.com.apple.contacts.commlimits
com.apple.contacts.account-caching
com.apple.contactsd.contact-provider
com.apple.contactsd.persistence
com.apple.contactsd.support
Persistence, in this context, is not a bug and not a password prompt. It is the database side of the daemon: the part that makes sure a contact saved today still exists tomorrow, across restarts and account changes. The binary’s own strings describe the housekeeping in English. Did clean up stale account persistence. Did delete zombie provider containers. Did remove persistence for account. These are the sentences of a daemon that adds and removes per-account stores as you add and remove accounts in Contacts settings.
The same strings reveal the sync machinery it services: a line for handling Exchange sync persistence endpoints per account identifier, a boolean flag for the moment a remote store account changes over to iCloud, and an Ask To door with its own service name, handling shared contact updates that arrive as vCard data. This is why a misbehaving contact account shows up as contactsd CPU time. The daemon is not malfunctioning. It is servicing a client that keeps asking.
One autocomplete absence is also informative: unlike the notification and keychain daemons, contactsd has no wants rows at all. Nobody’s Mac is showing them a contactsd password prompt. The access prompt people do see, an app asking to use your contacts, belongs to the app and the privacy layer, not to this daemon, and the answer lives in System Settings under Privacy and Security, Contacts.
The old AddressBook, still wired in
The deepest detail in the plist is a set of wake-up triggers the daemon registered with the distributed notification system: ABDatabaseChangedExternallyNotification, and ABDistributedDatabaseChangedNotification, each in a plain and a privileged flavour. Those names predate the Contacts framework entirely. They are the vocabulary of AddressBook, the API that managed contacts on Mac OS X from 2002 until Contacts replaced it, and contactsd still listens for their broadcasts in 2026. The modern Contacts framework has its own change notification, CNContactStoreDidChangeNotification, and at least one system daemon subscribes to it directly: the familycircled page shows the Family Sharing roster daemon asking to be woken by it, because family members are contacts, and an edited card can change who counts as family.
The strings tell the same story from the other side: ABCDContainer, ABAddressBookErrorDomain, a whole AddressBookCore framework linked in behind the thin daemon binary. Apple has carried the contacts database forward through at least three API generations without ever asking users to migrate anything by hand, and contactsd is the layer where that continuity actually happens. Your contacts database file is still named AddressBook-v22.abcddb, v22 being a schema version nobody outside Apple has ever needed to care about.
The framework Resources folder also holds the vocabulary of what a contact is, in the form of localisation tables. CNContact.loctable carries 34 entries in British English, and they are the property names of a contact record: givenName, familyName, emailAddresses, phoneNumbers, contactRelations, departmentName, dates, birthdays, and the rest. Sibling tables describe containers, groups, instant message addresses, and the metadata of dragging a contact between apps. It is a complete answer to what a contact is, as Apple’s own code defines one, sitting in a file any Mac can read.
When contactsd earns its CPU column
Everything measured on this page says the same thing: a healthy contactsd is nearly free. Thirty one seconds of processor time a day. 3.3 MB of memory. Six hours without writing a log line. The system is so relaxed about it that EnablePressuredExit is set to true, meaning memory pressure is allowed to take its memory away and let launchd start a new one, minimum runtime ten seconds. It is not in the club of daemons the kernel refuses to reclaim. It is in the club of daemons that are cheap to replace.
The cases where the CPU column moves are all cases where work genuinely exists. A first sync after adding an account, with an empty store to fill. A large contact list meeting a fresh Spotlight index to verify. An account whose sync keeps failing and retrying, which the Exchange and iCloud persistence strings show the daemon servicing directly. And the nightly maintenance window, on power, screen asleep, which you would have to be watching Activity Monitor at 3 AM to catch.
If contactsd is genuinely pegged on your Mac for an hour, the daemon is the messenger. Open Contacts, open its Settings, and read the sync status off each account. The one still spinning is the one to sign out of and back into. That rebuilds the store through the APIs, keeps the privacy wall intact, and returns the daemon to the state measured here: a clerk with almost nothing to do.
Read it yourself
Every fact above came off a stock Mac. The identity and the quiet:
ps -Awwo pid,ppid,user,%cpu,rss,etime,time,comm | grep "[c]ontactsd"
log show --predicate 'process == "contactsd"' --last 6h
The schedule and the front doors:
plutil -p /System/Library/LaunchAgents/com.apple.contactsd.plist
launchctl print user/$(id -u)/com.apple.contactsd
The one official description, and the wall around the library:
man contactsd
ls ~/Library/Application\ Support/AddressBook
The manual page is two sentences and worth all of them. The last command is the most interesting, because it is the one your Mac will refuse: the folder you own, holding the contacts you added, closed even to you until an app you trust asks on your behalf.
Questions
What is contactsd on Mac?
It is the daemon that manages the contacts database on your Mac. The Contacts app is a window onto that database; contactsd is the thing underneath, serving every app that uses the Contacts framework and running the maintenance jobs that keep the store healthy. Its manual page, contactsd(8), has described the job since January 2022 in two sentences: contactsd manages the information in your contacts database, and it provides functionality to apps using the Contacts API and performs various background maintenance tasks. On the Mac measured here it runs as the logged-in user, not root, waking for about thirty one seconds of processor time a day and staying silent in the logs for hours at a stretch when nothing is syncing.
Why is contactsd using high CPU?
On a healthy Mac it barely registers. The one measured for this page sat at 0.0 percent CPU with forty five seconds of total processor time spread over a day and a half of life, and six hours of unified logging produced not one line from it. When contactsd does run hot, the work is almost always account churn: the daemon's own binary carries strings for servicing Exchange sync persistence endpoints and for handling the moment a remote store account changes over to iCloud, so a contact account that keeps failing and retrying its sync keeps contactsd busy servicing it. The first sync after adding an account is the other honest spike, because an empty store has to be filled. Google's autocomplete even pairs the daemon with a macOS version name, Tahoe, which tells you the complaints cluster on one specific release rather than spread evenly. If it stays hot, open Contacts, open Settings, and look at which account is still syncing. That account, not the daemon, is the problem.
Where is the contacts database on my Mac?
In two places you can see the edges of but not read. The account registry is a small SQLite file at ~/Library/Contacts/accounts.accountdb, 76 KB on the Mac measured here. The contacts themselves live under ~/Library/Application Support/AddressBook: one aggregate file named AddressBook-v22.abcddb, and a Sources folder holding one further store per sync account, each named after a UUID. The files are SQLite databases driven through Core Data, and the daemon holds them open continuously. You cannot browse them from a terminal, and that is deliberate: listing the folder returns Operation not permitted, opening the database returns authorization denied, even though stat on the exact file path still reports its size. The privacy layer protects your contacts from everything, including you. Do not delete these files to fix a sync problem. Remove and re add the account in Contacts settings instead, which rebuilds the store through the front door.
Can I quit or disable contactsd?
You can, and it changes nothing. The daemon is a launchd job whose parent is PID 1, and launchctl shows it has already been restarted twenty times on the Mac measured here, twenty one runs in total, with a minimum runtime of ten seconds between them. Force quitting it in Activity Monitor produces one of those restarts. The system is also free to reclaim its memory whenever it likes, because EnablePressuredExit is set to true in its own launch dictionary, the opposite of the daemons the system has promised to keep. It runs as your user account, so no password is even needed to kill it, which is a hint about how little killing it accomplishes. Nothing you would want is stored only inside the process: the database is on disk, and the daemon is just the clerk on duty.
Ready? Buy Ribbon for $15, or read all the guides.