What is apfsd, and why is it using CPU or disk on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
apfsd is the APFS volume management daemon: it controls volume encryption and decryption, automatic file defragmentation and other housekeeping for APFS disks. It works hardest while a volume is being encrypted or decrypted, for example when FileVault is turned on or off, and otherwise runs short maintenance tasks. It is part of macOS and safe.
apfsd at a glance
| apfsd | |
|---|---|
| Made by | Apple (part of macOS, APFS) |
| Type | System daemon |
| Location | /usr/libexec/apfsd |
| Runs as | root |
| Started by | launchd job com.apple.apfsd |
| Can you quit it? | No. launchd starts it whenever an APFS container is present, which on a Mac is always. |
What is apfsd?
APFS is the file system Macs use for their startup disk. Apple's Disk Utility guide lists its features as strong encryption, space sharing, snapshots, fast directory sizing and improved file system fundamentals. The apfsd(8) man page says apfsd controls volume encryption and decryption, automatic file defragmentation, and other housekeeping as needed.
launchd starts it when the system detects an APFS container. Its job also schedules three reporting tasks (one daily, one weekly, one occasional), all set to run only while the Mac is not being used.
Is apfsd safe?
Yes. It is installed at /usr/libexec/apfsd on the read-only system volume, runs as root, and is signed by Apple (com.apple.apfsd).
Why does apfsd use so much disk and CPU?
- Encrypting or decrypting a volume. Turning FileVault on or off, or encrypting an external APFS drive from Finder or Disk Utility, makes apfsd convert the volume's data in the background. On a large volume that can take a long time.
- Defragmentation. The man page lists automatic file defragmentation among its duties, which reads and rewrites file data when it runs.
- Idle-time reports. Its scheduled statistics tasks require the device to be inactive and one is marked CPU- and disk-intensive, so short activity can appear when you step away from the Mac.
- Connecting APFS drives. Each APFS container that appears, including encrypted external drives, gives apfsd work to set it up.
How much CPU is normal for apfsd?
Most of the time apfsd is idle. Short bursts while the Mac is idle or when an APFS drive is connected are normal.
Sustained CPU and disk use is expected during encryption or decryption and ends when the conversion completes.
How do you stop apfsd from using so much CPU?
- Check whether encryption is in progress. Open System Settings > Privacy & Security and look at the FileVault section, which shows progress while the disk is being encrypted or decrypted.
- Keep the Mac on power. Leave the Mac plugged in during encryption. On battery, FileVault settings can show that encryption is paused until you connect the power adapter.
- Check an external drive. Run
diskutil apfs listin Terminal to see APFS containers and volumes, including whether each volume is encrypted. - Let idle maintenance run. Activity that only appears when you leave the Mac alone is scheduled housekeeping and stops when you return.
When should you worry about apfsd?
Look into it if apfsd uses a lot of CPU for days with no encryption change in progress. Run First Aid on the disk in Disk Utility to check the file system.
An apfsd running outside /usr/libexec would not be Apple's.
How do you check apfsd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type apfsd in the search field. The Disk tab shows its Bytes Written and Bytes Read. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every apfsd 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 'apfsd' | grep -v grep
sudo fs_usage -w -f filesys apfsd
How can Thrum help with apfsd?
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 apfsd 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 apfsd
Does apfsd handle FileVault?
Its man page says it controls volume encryption and decryption, which is the work done when FileVault is turned on or off for an APFS volume.
Can I turn off apfsd?
No. It is part of how macOS manages APFS volumes, including the startup disk.
Sources
- apfsd(8) man page: run man apfsd in Terminal
- Apple Disk Utility User Guide: File system formats available in Disk Utility on Mac