What is iconservicesd, and why is it running on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
iconservicesd is the macOS daemon that manages the shared icon cache, adding and removing the icon images that Finder, the Dock and other apps display. It runs as its own system account from startup and is busy only when many icons are added, for example after installing apps. It is part of macOS and safe.
iconservicesd at a glance
| iconservicesd | |
|---|---|
| Made by | Apple (part of macOS, Icon Services) |
| Type | System daemon |
| Location | /System/Library/CoreServices/iconservicesd |
| Runs as | _iconservices (a system account) |
| Started by | launchd job com.apple.iconservices.iconservicesd |
| Can you quit it? | Not usefully. launchd starts it at boot and again whenever it is needed. |
What is iconservicesd?
Its man page says iconservicesd is used by the system to add and remove images to and from the shared icon cache. The images themselves are drawn by iconservicesagent; iconservicesd stores them so every app can reuse them.
It runs as the _iconservices system account and launchd starts it at boot. Its launchd job also wakes it when the system reports low or very low disk space, so it can respond by trimming the cache, and on a notification that asks it to clear the cache immediately.
Is iconservicesd safe?
Yes. It is in /System/Library/CoreServices on the read-only system volume and runs under a dedicated system account, not as your user or as root.
Why does iconservicesd use so much disk and CPU?
- Adding many icons to the cache. After many apps are installed or updated, new icon images are written to the cache.
- Low disk space. When macOS reports low disk space, iconservicesd is woken to respond, which can mean removing cached images.
- Requests from many apps. Every app that shows icons reads from the shared cache through it, so busy moments in Finder show up here too.
How much disk is normal for iconservicesd?
iconservicesd is always running and typically uses close to 0% CPU and very little disk outside of app installs and updates.
What can you do if iconservicesd stays busy?
- Let installs and updates finish. Activity after updating many apps settles once their icons are cached.
- Free up disk space. If the disk is nearly full, the low-space notices it reacts to will keep coming. Free space through System Settings > General > Storage.
- Restart the Mac. A restart clears any stuck request; launchd starts iconservicesd again at boot.
When should you worry about iconservicesd?
Constant disk writes from iconservicesd for a long time, with no apps being installed, are unusual. Check free disk space first, since low-space notices wake it.
How do you check iconservicesd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type iconservicesd in the search field. The Disk tab shows its Bytes Written and Bytes Read. 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 iconservicesd 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 'iconservicesd' | grep -v grep
sudo fs_usage -w -f filesys iconservicesd
How can Thrum help with iconservicesd?
Thrum's Disk tab shows read and write speed for the whole Mac, and its CPU and Memory tabs list iconservicesd with the rest. macOS does not give per-process disk counters for processes owned by root or other users to an app without administrator rights, so Thrum shows iconservicesd by CPU and memory, not by bytes written. 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 iconservicesd
Why does iconservicesd run as _iconservices?
Running under its own system account limits what it can access to what it needs for the icon cache.
Why can my user not quit iconservicesd?
It runs as another account, so macOS asks for an administrator password to quit it, and launchd would start it again anyway.
Sources
- iconservicesd(1) man page: run man iconservicesd in Terminal
- launchd job: /System/Library/LaunchDaemons/com.apple.iconservices.iconservicesd.plist