Thrum

What is fskitd, and why is it using CPU on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job, man page and installed FSKit modules checked on macOS 26.3.1.

fskitd is the FSKit mount manager: it mounts volumes whose file system runs as an app extension in user space, and passes file requests from the kernel to that extension. It uses CPU when you read or write files on such a volume, for example during a large copy. It is part of macOS and safe.

fskitd at a glance

fskitd
Made byApple (part of macOS, FSKit)
TypeSystem daemon
Location/usr/libexec/fskitd
Runs asroot
Started bylaunchd job com.apple.filesystems.fskitd
Can you quit it?Not while an FSKit volume is mounted; its file access goes through fskitd.

What is fskitd?

FSKit is Apple's framework for implementing a file system that runs in user space; Apple's documentation lists it from macOS 15.4. A file system built with FSKit ships as an app extension, and FSKit connects it to Disk Arbitration, NetFS and the mount command.

The fskitd(8) man page says fskitd manages the FSKit mount life cycle, coordinates with other daemons, and translates requests from the kernel to the user-space file system servers backing each volume. macOS 26.3.1 ships FSKit modules for exFAT, MS-DOS (FAT) and FTP, and third-party apps can add their own.

Is fskitd safe?

Yes. It is at /usr/libexec/fskitd, runs as root, and is signed by Apple (com.apple.fskitd). The file system modules it talks to run as separate extensions.

Why does fskitd use so much CPU?

How much CPU is normal for fskitd?

Idle near 0% CPU when no FSKit volume is in use. CPU use during file transfers to such a volume is expected and stops when the transfer ends.

How do you stop fskitd from using so much CPU?

  1. Find which volume is in use. Run mount in Terminal to list mounted volumes and their file system types, then see which one you are copying to or from.
  2. Let large copies finish. The activity follows the transfer. Copying fewer, larger files is usually faster than many small ones.
  3. Eject the volume when done. Ejecting the drive ends fskitd's work for it.
  4. Check third-party file system apps. If the busy volume uses a file system added by an app, check that app for updates.

When should you worry about fskitd?

Look into it if fskitd stays busy with no external drives or network volumes in use. Ejecting all volumes or restarting will show whether a mount was stuck.

An fskitd running outside /usr/libexec would not be Apple's.

How do you check fskitd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type fskitd in the search field. 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 fskitd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'fskitd' | grep -v grep

How can Thrum help with fskitd?

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 fskitd 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 fskitd

When did fskitd appear?

Apple's FSKit documentation lists availability from macOS 15.4. On macOS 26 it is present on every Mac.

Does fskitd handle my startup disk?

No. The startup disk uses APFS, which is not an FSKit file system. fskitd handles volumes served by FSKit modules.

Sources