What is cfprefsd, and why is it using CPU on my Mac?
Last reviewed: 19 November 2026. Path, accounts, launchd jobs and man page checked on macOS 26.3.1.
cfprefsd is the macOS defaults server: every app reads and saves its settings through it instead of opening its preference files directly. It is normally idle, and high CPU almost always means an app is writing or reading its settings far more often than it should. Find that app and update, reset or quit it; cfprefsd itself should be left alone.
cfprefsd at a glance
| cfprefsd | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System daemon and per-user agent |
| Location | /usr/sbin/cfprefsd |
| Runs as | root, plus one copy as your user (and some system accounts) |
| Started by | launchd job com.apple.cfprefsd.xpc.daemon (root) and com.apple.cfprefsd.xpc.agent (your user) |
| Can you quit it? | Not usefully. launchd restarts it at once, and apps may lose preference changes that were not yet written. |
What is cfprefsd?
The cfprefsd(8) man page describes it as the defaults server that provides preferences services for the CFPreferences and NSUserDefaults APIs, the interfaces apps use to store their settings. When an app saves a setting, such as a window position or a checkbox, cfprefsd keeps the value and writes it to the right property list file, for example in ~/Library/Preferences.
There are two kinds of copy. The com.apple.cfprefsd.xpc.agent job runs as your user and handles your apps' preferences; the com.apple.cfprefsd.xpc.daemon job runs as root and handles system-wide preferences in /Library/Preferences. Some system accounts get their own copy too.
Is cfprefsd safe?
Yes. cfprefsd is part of macOS at /usr/sbin/cfprefsd, started by launchd. The man page says there are no configuration options and that users should not run it manually.
Why does cfprefsd use so much CPU and disk?
- An app writing settings in a loop. Some apps save the same preference many times a second, for example while tracking a window or playback position. Every write goes through cfprefsd, so the CPU shows up under cfprefsd rather than under the app.
- Very large preference files. Apps that store large amounts of data, such as caches or long lists, in their preferences make every read and write expensive. Preferences are meant for small values.
- Frequent saves to disk. Each change has to be written back to the app's property list file eventually, so an app that changes settings constantly also causes small, repeated disk writes.
- Scripts using the defaults command. The
defaultscommand and configuration-management tools read and write through cfprefsd too. A script that runsdefaultsin a tight loop keeps it busy.
How much CPU is normal for cfprefsd?
Typical: near 0% CPU, with brief spikes when apps launch, quit or change settings. Memory is usually small because it holds only the preferences in use.
A copy that stays at 20% CPU or more for minutes while you are not changing anything is not normal and points to one app.
How do you stop cfprefsd from using so much CPU?
- Find the app that is writing. In Terminal,
sudo fs_usage -w -f filesys cfprefsd | grep plistshows which preference files are being written. The file name, such ascom.example.app.plist, names the app. Press Control-C to stop. - Quit or update that app. Quit the app named in the file and watch whether cfprefsd drops back to near 0%. If it does, check for an update to the app.
- Look for an oversized preference file. In Finder, choose Go > Go to Folder, enter
~/Library/Preferences, and sort by size. A preference file of many megabytes is unusual and is a candidate for the problem. - Reset one app's settings the supported way. Quit the app, then run
defaults delete <domain>(for exampledefaults delete com.example.app). This goes through cfprefsd, which avoids the problem of an edited file being overwritten. The app returns to its default settings.
When should you worry about cfprefsd?
Worry if cfprefsd stays busy after you quit every app you opened, or comes back to high CPU right after a restart. Then a background agent or login item is the likely writer; the fs_usage step names it.
Deleting or editing files in ~/Library/Preferences while apps are running often does not work: the defaults man page notes that a running app will not see the change and may overwrite it.
How do you check cfprefsd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type cfprefsd in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every cfprefsd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). fs_usage prints each file it reads or writes until you press Control-C; it needs an administrator password.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'cfprefsd' | grep -v grep
sudo fs_usage -w -f filesys cfprefsd
How can Thrum help with cfprefsd?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when cfprefsd is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. macOS does not let apps quit processes owned by root or other users, so Thrum shows them for information and leaves stopping them to the steps above.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about cfprefsd
Why are there several cfprefsd processes?
One runs as root for system preferences and one runs for each logged-in user. Some system accounts used by macOS services also get their own copy.
Can I delete a .plist file to reset an app?
It can work if the app is quit, but cfprefsd may still hold the old values in memory. defaults delete with the app's domain is the more reliable way.
Sources
- cfprefsd(8) man page: run man cfprefsd in Terminal
- defaults(1) man page: run man defaults in Terminal
- fs_usage(1) man page: run man fs_usage in Terminal