What is installd, and why is it using CPU or disk on my Mac?
Last reviewed: 19 November 2026. Path, accounts, launchd jobs, man page and /var/log/install.log checked on macOS 26.3.1.
installd is the macOS daemon that carries out software package installations. It is busy while an installer package or an App Store app is being installed, writing files to disk and checking them, and it exits when the installation is done. The install log at /var/log/install.log shows what it is installing.
installd at a glance
| installd | |
|---|---|
| Made by | Apple (part of macOS, PackageKit) |
| Type | System daemon (with a per-user agent) |
| Location | /System/Library/PrivateFrameworks/PackageKit.framework/Resources/installd |
| Runs as | root (a per-user copy can also run as your user) |
| Started by | launchd job com.apple.installd |
| Can you quit it? | Not during an installation, which could leave the software half-installed. It exits on its own when idle. |
What is installd?
The installd(8) man page says it is used by the system during package installation and should not be invoked manually. It is part of PackageKit, the framework behind the Installer app and the installer command.
Two launchd jobs run it: com.apple.installd as root, and com.apple.installd.user as a per-user agent. Each installation is recorded in /var/log/install.log. On the Mac checked for this page, that log shows the App Store's agent handing an Xcode installation to PackageKit, which installd then carried out, while Apple's background security and Rosetta updates were installed by system_installd.
Is installd safe?
Yes. It is in the PackageKit private framework on the read-only system volume and signed by Apple (com.apple.installd). It installs what you or the App Store asked for; it does not choose software on its own.
Why does installd use so much disk and CPU?
- Large apps. Installing or updating a large app, such as Xcode, writes many gigabytes and thousands of files, which keeps installd busy for a long time.
- Expanding and checking packages. Packages are compressed and signed. installd expands the payload and checks it, which costs CPU in addition to disk writes.
- App Store updates in the background. With Automatic Updates turned on in the App Store, app updates install on their own, so installd can appear without you starting an install.
- Installer scripts. Many third-party packages run scripts before or after installing files, and those scripts run as part of the installation.
How much disk is normal for installd?
Not running when nothing is being installed. During an installation, high disk activity and moderate CPU for the length of the install is normal; for very large apps that can be many minutes.
It should exit shortly after the installation finishes.
How do you stop installd from using so much disk?
- See what is being installed. Run
tail -f /var/log/install.login Terminal to follow the installation as it happens, and press Control-C to stop. - Let the installation finish. Interrupting an install can leave an app incomplete. Keep the Mac awake and on power until it is done.
- Control App Store updates. Open the App Store app, choose App Store > Settings, and turn Automatic Updates off if you prefer to install app updates yourself from the Updates section.
- Install large apps when you are not busy. Start big installs or updates before a break so the disk activity does not overlap your work.
When should you worry about installd?
Look into it if installd stays busy for a long time and the install log shows no progress, or if the same installation repeats. Restart the Mac and try the installation again.
An installd running outside the PackageKit framework path would not be Apple's.
How do you check installd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type installd 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 installd 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 'installd' | grep -v grep
sudo fs_usage -w -f filesys installd
How can Thrum help with installd?
Thrum's Disk tab shows read and write speed for the whole Mac, and its CPU and Memory tabs list installd 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 installd 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 installd
What is the difference between installd and system_installd?
Both are PackageKit installer daemons with the same man page text. On the Mac checked for this page, the install log shows Apple's background updates such as XProtect data installed by system_installd, and an App Store app (Xcode) installed by installd.
Why is installd running when I am not installing anything?
An App Store app update may be installing in the background. The install log shows which package it is.
Sources
- installd(8) man page: run man installd in Terminal
- Install log: /var/log/install.log on macOS 26.3.1
- Apple App Store User Guide: Update purchased apps on Mac