Thrum

What is fseventsd, and why is it using CPU or disk on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job and code signature checked on macOS 26.3.1.

fseventsd is the macOS daemon behind the File System Events service: it records which folders change and tells apps that asked to be notified. It gets busy when something creates, changes or deletes a very large number of files, and calms down when that stops. It is part of macOS and must keep running.

fseventsd at a glance

fseventsd
Made byApple (part of macOS, File System Events)
TypeSystem daemon
Location/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/Support/fseventsd
Runs asroot
Started bylaunchd job com.apple.fseventsd
Can you quit it?No. launchd starts it at boot and keeps it alive; apps that watch folders depend on it.

What is fseventsd?

Apple's File System Events API lets an app ask to be notified when the contents of a folder tree change, and lets it check cheaply whether anything changed since it last looked. Apple gives a backup app as an example: it can find which files changed since a given time. fseventsd is the daemon that collects those changes from the kernel and delivers them.

It also keeps a log of changes on each volume, in a hidden .fseventsd folder at the top of the disk (on the startup disk, /System/Volumes/Data/.fseventsd). That log is what lets an app that was not running catch up on what changed while it was closed.

Is fseventsd safe?

Yes. fseventsd is part of macOS, lives in the FSEvents framework on the read-only system volume, and is signed by Apple (com.apple.fseventsd). Its own work is light; when it is busy, the cause is almost always another program changing many files.

Why does fseventsd use so much disk and CPU?

How much disk is normal for fseventsd?

On a quiet Mac fseventsd is typically near 0% CPU with little disk activity. Short bursts whenever files are saved are normal.

During a big copy, install or build it can rise for as long as that job runs. If it stays busy with nothing obvious running, some process is still changing files.

How do you stop fseventsd from using so much disk?

  1. Find the program changing files. In Activity Monitor's Disk tab, sort by Bytes Written to see which app is writing the most. That app, not fseventsd, is the source of the load.
  2. Watch file activity live. Run sudo fs_usage -w -f filesys in Terminal for a few seconds and press Control-C. The paths that repeat show which folder is changing.
  3. Pause or reschedule the busy job. Pause a sync client, let a build or install finish, or move a cache folder that is rewritten constantly to a place nothing watches.
  4. Close apps that watch large folders. Editors and tools that watch large project folders get an event for every change inside them. Closing the project when you are not using it reduces the traffic.

When should you worry about fseventsd?

If fseventsd stays at high CPU for a long time while Activity Monitor shows no process writing to disk, restart the Mac. If it returns right away, use fs_usage to find which path keeps changing.

A copy of fseventsd running from outside the FSEvents framework path above would not be Apple's.

How do you check fseventsd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type fseventsd 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 fseventsd 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 'fseventsd' | grep -v grep
sudo fs_usage -w -f filesys fseventsd

How can Thrum help with fseventsd?

Thrum's Disk tab shows read and write speed for the whole Mac, and its CPU and Memory tabs list fseventsd with the rest. macOS does not give per-process disk counters for processes owned by root or other users to an app without administrator rights, so Thrum shows fseventsd by CPU and memory, not by bytes written. 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 fseventsd

Can I delete the .fseventsd folder?

It is protected by macOS and holds the change log apps rely on to catch up. Deleting it is not a fix for high CPU; finding the program that changes files is.

Does fseventsd slow down my Mac?

Not on its own. It reflects file activity caused by other programs, and stops working hard when they stop.

Sources