Is it safe to delete .fseventsd on a Mac?
- No, leave it.
.fseventsdis macOS’s running record of which folders changed on a disk. Backup and sync tools use it to catch up on changes without rescanning everything. - What deleting it costs: the tools that rely on that history lose it, and may have to scan the whole disk to work out what changed. Apple tells developers never to work with these files directly.
- Does it come back? At once: macOS’s
fseventsdservice keeps writing it as files change. - SiftMac’s verdict: Leave it
1. What it is
Whenever files are created, changed or deleted, macOS notes which folder it happened in. Apps can ask to hear about changes as they happen, and can also ask what changed since a point in the past, even if they weren’t running at the time. Apple’s own example is a backup app working out which files have changed since its last run.
To answer that, the fseventsd service stores the record as compressed files in .fseventsd at the top of each disk, readable only by the system. Apple calls the history advisory rather than complete, and tells backup software to make a full sweep of a disk from time to time anyway.
2. Where it is
/System/Volumes/Data/.fseventsd
/Volumes/<drive>/.fseventsd
On the startup disk it’s on the data volume, where your files are. External drives used with a Mac get one of their own, which is why .fseventsd turns up on USB sticks and SD cards.
3. How big it gets
Only the system may read it, so measuring it takes an administrator password:
sudo du -sh /System/Volumes/Data/.fseventsd
What it holds is compressed lists of folders that changed, not copies of your files.
4. Why to leave it, and what about external drives
On your Mac’s own disk, leave it. Deleting it gains little and throws away the change history that backup and sync apps depend on. Apple even tells developers not to purge event history, because no app can assume it’s the only one using it.
On an external drive it does no harm either: other computers ignore it, and a Mac creates it again. Apple’s old developer guide describes switching logging off for a volume with an empty file named no_log inside .fseventsd, meant for cases like backup volumes. An Apple engineer has since said he wouldn’t recommend opting general-purpose volumes out, and a developer reported that it no longer seemed to work on an APFS volume in macOS 15.5.
5. What happens afterwards
- Left alone, it needs nothing from you.
- If it were deleted, macOS would start a new history straight away, and apps that rely on it would find their old history no longer applies and rescan.
- Backup tools may then take longer on their next run while they check everything.
Questions
What is .fseventsd on my USB drive?
The same change log, kept for that drive. A Mac creates it when it uses the drive. It’s harmless to leave there, and other computers ignore it.
Can I delete .fseventsd?
On your Mac’s own disk, no: it’s macOS’s record of changes, used by backup and sync tools, and only the system can open it. On an external drive, deleting it does little harm, but it comes straight back.
Does .fseventsd take a lot of space?
Usually not, since it holds compressed lists of folders that changed rather than copies of files. The du command above shows its real size.
Is .fseventsd a virus or a tracker?
No. It’s part of macOS, it records which folders changed, and it stays on the disk.
How SiftMac handles it. SiftMac doesn’t list or touch .fseventsd; it belongs to macOS. Its space map measures your home folder by default, and this folder sits at the top of the disk, outside it.
Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works