← All processes

macOS process library · System core

What is fseventsd on Mac?

fseventsd keeps a running record of which folders changed on each disk. Spotlight, Time Machine, Finder, cloud storage apps, and developer tools all use that record to find out what’s new without rescanning everything.

Part of
macOS’s File System Events service.
Safe?
Yes. It lives inside macOS’s CoreServices framework in /System/Library.
Can I quit it?
No. It runs as root, and Spotlight, Time Machine, and many apps depend on it. macOS restarts it immediately.

The short answer

fseventsd is supposed to be running. When it’s busy, something is changing a large number of files: an install, a build, a sync, or a backup. The fix is almost always to let that work finish or to find what’s causing it, not to touch fseventsd.

Normal use

What fseventsd usually looks like.

fseventsd usually sits near 0% CPU with a small memory footprint. It spikes when many files change in a short time, then returns to idle.

It stores its records in a hidden .fseventsd folder at the top of each disk, which is why it also does work when you connect an external drive.

Why fseventsd uses so much CPU or memory

How to calm fseventsd down

Start at the top. Each step is more disruptive than the one before.

  1. Let the file-heavy work finish

    Installs, builds, and syncs end. fseventsd quiets down when they do.

  2. Find what’s changing files

    Look for a build, a watcher, a sync app, or an AI agent rewriting a project. Pause the one you don’t need right now.

  3. Pause cloud sync temporarily

    If a sync app is downloading many files, pausing it gives fseventsd a break.

  4. Run First Aid on the disk

    Open Disk Utility, select the disk, and click First Aid if fseventsd is busy even when nothing is changing.

  5. Restart your Mac

    A restart clears a stuck state if none of the above help.

Seeing it in Spare

Find what it’s reacting to.

fseventsd reacts to file changes, so the real question is what’s changing them. Spare groups development projects and AI agents by folder, so a build, an install, or an agent rewriting a project shows up as one line with its CPU and memory next to fseventsd.

Spare lists fseventsd as part of macOS and never offers to stop it.

SpareMemory pressure · Normal
◎
fseventsdmacOS · System core
12% CPU18 MB
▢
web-appDevelopment · npm install
38% CPU1.1 GB
✦
Claude Code · web-appAI agent
7% CPU560 MB
Illustration with example readings

Common questions

About fseventsd

Is fseventsd a virus?

No. It’s part of macOS’s CoreServices framework and runs on every Mac.

Can I delete the .fseventsd folder?

You shouldn’t. It’s how macOS knows what changed. Deleting it forces Spotlight and backup tools to rescan everything, which costs more.

Why does fseventsd spike when I run npm install?

Installing packages writes huge numbers of small files. fseventsd records each change so tools like Spotlight and file watchers can react.

Does fseventsd slow down Time Machine?

No. Time Machine relies on it to back up only what changed, which makes backups much faster.

Related processes

Sources: Apple Developer: File System Events, Apple: File System Events Programming Guide. 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