macOS process library · System core
What is cfprefsd on Mac?
cfprefsd is the macOS service that reads and writes app preferences. When any app saves a setting, it goes through cfprefsd, which caches preferences in memory and writes them to the .plist files in your Library folder.
- Part of
- macOS’s preferences service, behind the CFPreferences and UserDefaults APIs.
- Safe?
- Yes. The copy at
/usr/sbin/cfprefsdis part of macOS. - Can I quit it?
- Not recommended. macOS restarts it, but settings an app was saving at that moment can be lost.
The short answer
cfprefsd is supposed to be running, and you’ll usually see several copies: one for your account, one for the system, and others for system accounts. Sustained high CPU almost always means one app is reading or writing preferences far too often.
Normal use
What cfprefsd usually looks like.
Each copy of cfprefsd uses little CPU and a few megabytes of memory. It spikes briefly when apps launch and load their settings.
Because it caches preferences in memory, editing a .plist file directly while apps are running may not take effect, and cfprefsd may overwrite your change.
Why cfprefsd uses so much CPU or memory
- An app writing settings in a loop
A buggy app or plugin that saves preferences many times a second keeps cfprefsd busy. This is the most common cause.
- Many apps launching at once
Logging in or opening a batch of apps loads everyone’s settings at the same time.
- Damaged preference files
A corrupted .plist can make an app retry reading it repeatedly.
How to calm cfprefsd down
Start at the top. Each step is more disruptive than the one before.
- Find the app causing it
Quit apps you opened recently one at a time and watch whether cfprefsd calms down. Menu bar utilities and plugins are common culprits.
- Update the app
Once you’ve found it, check for an update. Preference loops are a known kind of bug that developers fix.
- Change settings with defaults, not a text editor
Use the
defaultscommand or the app’s own settings. cfprefsd caches preferences, so editing .plist files directly can be ignored or overwritten. - Restart your Mac
A restart clears cfprefsd’s cache and any stuck state.
Seeing it in Spare
Find what it’s reacting to.
Your account’s copy of cfprefsd runs as you, so Spare measures it directly. When it spikes, look at what Spare shows next to it: an app that just launched or a menu bar utility using CPU at the same time is a good first suspect.
Spare lists cfprefsd as part of macOS and never offers to stop it.
Common questions
About cfprefsd
Why are there several cfprefsd processes?
There’s one for your user account, one for the system, and others for system accounts that macOS uses internally. Each manages its own preferences.
Is cfprefsd a virus?
No. It’s a documented part of macOS in /usr/sbin.
Why didn’t my change to a .plist file stick?
cfprefsd keeps preferences in memory and writes them back later, which can overwrite edits made directly to the file. Use the defaults command instead.
Can I quit cfprefsd?
It isn’t useful. macOS restarts it, and an app saving settings at that moment could lose them. Find the app that’s overusing it instead.
Related processes
Sources: cfprefsd(8) manual page, Apple Developer: UserDefaults. Reviewed October 13, 2026.
Get Spare
Free to use. Yours to explore.
Download Spare for Apple silicon, or explore the MIT-licensed source on GitHub. Free to use, with no subscription or account.
macOS 14+ · Apple silicon · Signed and notarized