Thrum

What is storagekitd, and why is it running on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job, man page and linked frameworks checked on macOS 26.3.1.

storagekitd is the helper daemon for StorageKit, the framework Disk Utility and the diskutil command use to track disks and to carry out operations that need system privileges. It runs while those tools work with disks and is otherwise idle. It is part of macOS and safe.

storagekitd at a glance

storagekitd
Made byApple (part of macOS, StorageKit)
TypeSystem daemon
Location/usr/libexec/storagekitd
Runs asroot
Started bylaunchd job com.apple.storagekitd
Can you quit it?Not during a disk operation. Otherwise it exits on its own when idle.

What is storagekitd?

The storagekitd(8) man page says it is used by the StorageKit framework for disk state keeping and privileged operations, by various clients in macOS. On macOS 26, both Disk Utility and /usr/sbin/diskutil link against StorageKit.

Its launchd job also starts it at boot if the system has a pending disk resize recorded in its startup settings, so it can finish that operation.

Is storagekitd safe?

Yes. It is at /usr/libexec/storagekitd on the read-only system volume, runs as root, and is signed by Apple (com.apple.storagekitd).

Why does storagekitd use so much CPU and disk?

How much CPU is normal for storagekitd?

Idle or not running most of the time. Activity while Disk Utility is open or during a disk operation is expected and ends when the operation does.

What should you do if storagekitd stays busy?

  1. Check for an operation in progress. Look in Disk Utility for a running erase, partition or First Aid task and let it finish.
  2. Quit Disk Utility when done. Closing Disk Utility ends its requests to the daemon, which then exits when idle.
  3. Disconnect a problem disk. If a connected disk is behaving oddly, eject and disconnect it and see whether the activity stops.

When should you worry about storagekitd?

Look into it if storagekitd uses CPU for a long time with Disk Utility closed and no disk operation running. A restart clears a stuck state.

A storagekitd outside /usr/libexec would not be Apple's.

How do you check storagekitd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type storagekitd in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every storagekitd 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 'storagekitd' | grep -v grep
sudo fs_usage -w -f filesys storagekitd

How can Thrum help with storagekitd?

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

Is storagekitd related to diskmanagementd?

Older versions of macOS used a daemon called diskmanagementd. On macOS 26.3.1 that daemon is not present, while storagekitd is, and Disk Utility uses StorageKit.

Can I stop storagekitd?

There is no need. It runs on demand and exits when it has nothing to do.

Sources