HeartbeatHocusFocusFilesMacHyperTile
Guide

fseventsd, the daemon that keeps your Mac's diary

fseventsd is the diary macOS keeps of every file change, and the .fseventsd folder on your USB stick. Measured on a real Mac: 89,000 log lines a day, 99.8% of them one line.

By Chethan Kumar S N · Updated

Every daemon in this series gets measured by the same ruler. Processor time, memory, the doors it opens, the words in its manual. fseventsd breaks the ruler before the measuring starts: it is the only daemon so far with no manual page at all, and the only one that does not live in /usr/libexec or /System/Library/CoreServices. It lives inside the framework it serves, two levels deep, at CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/Support/fseventsd. The daemon is furniture inside its own product. That placement is also the job description. fseventsd is not a service you call, it is the floor other software stands on, and almost everything you watch your Mac do, indexing, backing up, syncing, has this daemon somewhere under it.

What it keeps is a diary. Every file created, renamed, moved, deleted or touched on every mounted volume gets an event, and the events get numbers that increase per disk, so a client can ask what changed since event 47 and get an answer without rescanning the drive.

What Apple says about it, all nine years old

There is no fseventsd manual page. Not in section 8 where daemons live, not anywhere. What exists instead is the File System Events Programming Guide in Apple’s documentation archive, updated 13 December 2012, still the canonical description of how this machinery is meant to behave. Its life cycle for an event stream reads:

The application creates a stream by calling FSEventStreamCreate or FSEventStreamCreateRelativeToDevice. The application schedules the stream on the run loop by calling FSEventStreamScheduleWithRunLoop. The application tells the file system events daemon to start sending events by calling FSEventStreamStart.

That third step is the whole relationship: an app asks, and this daemon starts sending. The guide also documents the two shapes of stream, and the distinction explains the folder you will meet further down this page:

A per-host event stream consists of events whose IDs are increasing with respect to other events on that host. … A per-disk event stream, by contrast, consists of events whose IDs are increasing with respect to previous events on that disk.

And it warns the honest warning that backup software lives by:

Because disks can be modified by computers running earlier versions of OS X (or potentially other operating systems), you should treat the events list as advisory rather than a definitive list of all changes to the volume. If a disk is modified by a computer running a previous version of OS X, the historical log is discarded.

Advisory, not definitive. Even Apple does not fully trust the diary. The current Mac User Guide never says the word fseventsd, verified across the pages fetched for this series: Spotlight, backup, file management. Apple documents what the diary is for and never names the clerk.

The identity, measured

On the Mac measured here, a 14 inch M1 Pro laptop running macOS 27.0.1 (build 26A434), 27 days past its last boot:

$ ps -Awwo pid,ppid,user,%cpu,rss,etime,time,args | grep "[f]seventsd"
  414     1 root    0.3  5232  27-00:11:35  141:51.12 .../FSEvents.framework/Versions/A/Support/fseventsd

Process id 414, parent id 1, which is launchd, the parent of every daemon. Running as root, like the privileged half of this series, not as a reserved account: no _fseventsd user exists, the work is considered core system work. The binary is 610,512 bytes, built 24 September 2026, carrying three architectures, x86_64, arm64e and arm64e.x1, so the Intel slice is still in there. The codesign record says Platform identifier=26 and Identifier=com.apple.fseventsd. It holds 476 strings, near the bottom of this series, because the vocabulary lives one directory up in the FSEvents framework binary itself, CFBundleVersion 1433, bundle signature fsev.

The processor arithmetic: 141 minutes 51 seconds across 27 days is about five minutes 15 seconds a day, a bit over a third of one per cent of one core. Middle of the pack. The memory: 5,232 KB resident. Small, and deliberately so, in a way worth its own section.

The doors, and one flag nobody else carries

The launch file is /System/Library/LaunchDaemons/com.apple.fseventsd.plist, and read plainly it is a short document with one surprise in it:

RunAtLoad          => true
KeepAlive          => true
HopefullyExitsLast => true
EnablePressuredExit => false
EnableTransactions => false
PosixSpawnType     => Interactive
MachServices       => { "com.apple.FSEvents" => true }

RunAtLoad and KeepAlive are standard: start when the system does, restart if it dies. Then the unusual pair. EnablePressuredExit false means the system is told not to reclaim this daemon’s memory when memory gets tight, the opposite of the setting nearly every daemon in this series carried, the one that lets idle daemons shrink and get recycled. And HopefullyExitsLast, a flag no other daemon measured in this series has, asks the system to let this process outlive the others when a session winds down. launchctl agrees with both: runs 1, and last exit code, literally, “never exited”. The design logic is not mysterious once you accept what the daemon is. A diary with gaps is worse than no diary, because a client resuming from a lost event ID has to assume everything changed and rescan the whole disk. macOS would rather keep five megabytes pinned than trigger terabyte rescans.

Two environment variables finish the picture. OSLogRateLimit 64 caps how fast the daemon may write to the unified log. And MallocSpaceEfficient 1 asks its allocator to favour compactness over speed, which is the memory footprint you just read, stated as policy.

The log: second chattiest in the series, and 99.8 per cent of it is one line

Counted over a full day on this Mac: 89,220 log lines. That is the second chattiest daemon measured in this series, behind only searchpartyd at 177,253 and well ahead of symptomsd at 50,726. But the shape is unlike anything else measured so far. Of those 89,220 lines, 89,029, which is 99.8 per cent, are the same eleven words:

2026-11-15 15:11:52.374 A fseventsd[414:2c4f356] (libsystem_info.dylib) Resolve user group list

Resolve user group list, over and over, tens of thousands of times. It is not the daemon talking, it is libsystem_info, the library macOS uses to turn numeric file ownership into names, logging one lookup per batch of events. Every time files change, fseventsd works out who they belong to, and the library announces each attempt. A daemon whose log is one library’s catchphrase is the chattiest-about-the-least in the series outside watchdogd’s all private heartbeat.

The hour by hour shape separates sleep from work. The busiest hour, 11pm on 15 November, wrote 45,878 lines, about 12.7 per second and the busiest single daemon hour measured on this Mac, during an evening of builds and deploys. The two hours before it wrote 24,835 and 15,342. A quiet late morning hour wrote 277. File churn is the throttle, and file churn has a schedule.

Underneath the refrain sit the lines in the daemon’s own category, com.apple.fsevents:daemon, 176 of them, and they include the one that answers a question people ask with a USB stick in one hand:

scan_old: bailing out because device mounted @ [<private>]<private> has dls 0x0 and dls->fci 0x0

The mount point is redacted, but the sentence structure is not: fseventsd scans the old state on a device as it mounts, and bails out when that state is empty or foreign. It reads the diaries other Macs left behind. There is also one scheduled task, an XPC activity named com.apple.fseventsd.daily that fired at 06:55 in the morning: housekeeping, the diary pruning itself.

The folders: your boot disk’s, and the one on your USB stick

On the boot disk the diary is a folder, hidden the same way the Spotlight index is, on the data volume, because the root of a modern Mac is a sealed read only snapshot:

$ ls -ld /System/Volumes/Data/.fseventsd
drwx------+ 28399 root  wheel  908768 Nov 16 13:08 /System/Volumes/Data/.fseventsd

$ ls /System/Volumes/Data/.fseventsd
ls: /System/Volumes/Data/.fseventsd: Permission denied

Root and wheel own it, the plus sign marks an access control list on top, and no normal account may so much as list it. The numbers say it is large: a directory whose own metadata has grown to 908,768 bytes, on a system where ordinary folders weigh 96 bytes, and a link count of 28,399. Whatever is inside, there is a lot of it, and only root gets to know. The same ls treatment the Spotlight index gets, the same Permission denied, and the same honest conclusion: the confident sizes quoted online are guesses.

The USB question deserves its own test rather than folklore, so one was run for this page. A fresh 16 MB exFAT volume was created, mounted, written to, left alone, ejected, and mounted again on the Mac measured here. Result: no .fseventsd folder appeared, at any point. What did appear, instantly, was ._testfile.txt, an AppleDouble file, macOS writing the extended attributes of the test file into a helper file because exFAT has nowhere native to put them. Two kinds of litter, two different causes: the dot underscore files come from metadata that must go somewhere, while the .fseventsd folder is persistent event state that only gets written when a Mac needs to resume from it on that disk, the per disk event IDs of Apple’s 2012 guide, kept on the volume they describe so the next mount can continue the numbering.

That is why the folder on your camera stick says a Mac once did more than read it. Apple’s guide even specifies the failure mode that makes the state disposable: if a disk is modified by a computer running an earlier OS, the historical log is discarded, and if disks move between computers the event IDs can conflict outright. The state is an optimisation, not a record. Delete it if it bothers you. It is not malware, it is not a virus, nothing on the stick needs it, and the worst case is that some Mac somewhere rescans. One neighbour at that same USB port stayed asleep through the whole experiment: usbmuxd, the daemon that multiplexes iPhone traffic, never logged a line all week, because the property it uses to decide a device is its business is literally named SupportsIPhoneOS, and a stick does not have one.

Who actually listens

The daemon never acts on what it sees. It is the town crier, not the guard, so the CPU and disk you attribute to fseventsd is nearly always somebody else’s errand. The client family on a stock Mac: mds, the Spotlight indexer that hears a file changed and queues it for the index, backup software walking event IDs instead of whole volumes, sync clients such as bird reconciling iCloud Drive, and anything developer shaped watching a folder for changes. When fseventsd looks busy, the interesting question is not what is wrong with the daemon, it is which of those is running.

Can you turn it off

No, and there is nothing to want. There is no row for it in System Settings, no defaults key that disables it, no supported unload. The switches that exist are the clients’: Spotlight’s indexing on and off, the backup schedule, the sync client’s own settings. fseventsd with no clients is a clerk with an empty counter, writing the diary at whatever rate your files change and nothing more.

Two read only commands if you want to watch it work:

$ log stream --predicate 'process == "fseventsd"' --style compact

Save a file anywhere and watch the resolve lines tick within seconds. And the folder check that needs no administrator rights:

$ ls -ld /System/Volumes/Data/.fseventsd

The short version

fseventsd is the diary clerk of macOS. Root owned, never exited in 27 days, five megabytes that the system has explicitly forbidden itself from reclaiming, because a gap in the record costs every client a full rescan. Its log is a single repeated library line 99.8 per cent of the time, its busiest hour tracked an evening of builds at 12 lines a second, and the mystery folder on your USB stick is its per disk state, safe to delete, written only when a Mac needs to resume the numbering. Apple documented the machinery in 2012 and has never put the daemon’s name in a manual. Now you have read further into it than the manual would ever go, in both directions.

Questions

What is fseventsd on Mac?

It is the daemon that keeps the log of file changes on your disks. When any app creates, renames, moves or deletes a file, the kernel notes it and fseventsd records it, so that other software can ask what changed since it last looked instead of rescanning the whole drive. Spotlight's indexer, backup software and sync tools such as iCloud Drive all work this way. On the Mac measured here it ran as root with process id 414, had not exited once in 27 days of uptime, and used about five minutes of processor time a day. It lives inside the FSEvents framework it serves, and it has no manual page at all.

Why is fseventsd using so much CPU?

On the Mac measured here, 141 minutes and 51 seconds of processor time across 27 days works out at about five minutes 15 seconds a day, roughly a third of one per cent of a single core. The work is not on a timer, it tracks file changes, so it arrives in storms. Its busiest measured hour wrote 45,878 log lines, about 12 a second, during an evening of builds and file churn, and a quiet morning hour wrote 277. If Activity Monitor shows fseventsd genuinely pegged for a sustained period, something is churning files: a big build, a backup, a sync client reconciling, or an app writing thousands of small files. The daemon's own log names the mounted device on every scan, so log stream will tell you which disk the storm is on.

What is the .fseventsd folder on my USB drive, and can I delete it?

It is the persistent event state a Mac wrote onto that disk, the same diary the daemon keeps on your internal drive. Apple's File System Events documentation calls this the historical log and says event IDs are per disk so that software can resume where it left off, which is why the state lives on the volume it describes. Deleting it is safe: nothing on the stick needs it to open your photos or videos, and a Mac that backs the stick up will quietly rewrite it. In a live test for this page, a Mac running macOS 27 mounted a fresh exFAT volume, wrote a file to it, ejected it and mounted it again, and never created a .fseventsd folder at all, so a stick that only gets read mostly stays clean.

Why does fseventsd never quit, and is its memory a problem?

Its launch configuration sets KeepAlive and RunAtLoad, and also HopefullyExitsLast, a flag no other daemon in this series has carried, which tells the system this process should outlive the others when a session ends. The same file sets EnablePressuredExit to false, meaning macOS is told not to reclaim its memory during pressure. That sounds alarming and is not: the daemon measured 5,232 KB of resident memory, about five megabytes. The design logic is that a diary with gaps is worse than no diary, because software resuming from a lost event ID would have to rescan everything.

Can I stop macOS writing .fseventsd and ._ files to a USB stick?

There is no supported switch for either. The dot-underscore files, like ._photo.jpg, are AppleDouble files, the way macOS stores extended attributes and Finder info on disks that have no place for them, such as exFAT and FAT32. The .fseventsd folder only appears when a Mac writes persistent event state to the disk. Your options are practical ones: delete the files on whatever device the stick also gets plugged into, run dot_clean on the stick from a Mac, or reformat the stick as APFS or HFS+ if only Macs will ever read it, since those file systems store the metadata natively and need no helper files.

Ready? Buy Ribbon for $15, or read all the guides.