What is warmd on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
warmd is a macOS daemon that controls caches used during startup and login, so that the files needed early on can be loaded efficiently. launchd starts it at boot with low disk and CPU priority, and on the Mac checked here it then exited normally. You may see it briefly after a restart and not again.
warmd at a glance
| warmd | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System daemon |
| Location | /usr/libexec/warmd |
| Runs as | root |
| Started by | launchd job com.apple.warmd |
| Can you quit it? | Not usefully. It runs at startup and exits on its own. |
What is warmd?
The warmd(8) man page says warmd controls caches used during startup and login and is not meant to be invoked directly. Its launchd job, com.apple.warmd, runs it at load, which means at boot.
The job gives it low priority: a nice value of 10 and low-priority disk access, so it yields to everything else. launchd restarts it only if it exits with an error. On the Mac checked here launchd had run it once since startup and it had exited with status 0.
Is warmd safe?
Yes. warmd is part of macOS at /usr/libexec/warmd, runs as root and is signed by Apple.
Why does warmd use so much disk and CPU?
- Startup. It runs at boot to work with the startup and login caches, which involves disk reads and writes.
- Login. Its man page mentions login caches as well, so activity around your login is expected.
- After an update. After a macOS update, startup-related caches are a reason for it to have more to do.
How much disk is normal for warmd?
Typical: a short run at startup with low-priority disk activity, then it exits.
If it stays running for a long time or restarts repeatedly, it is exiting with errors.
How do you check that warmd finished normally?
- Check its last exit. In Terminal,
launchctl print system/com.apple.warmdshows its state, run count and last exit code. Not running with exit code 0 is the normal result. - Wait a few minutes after restart. Startup work, including warmd's, settles a few minutes after login. Judge performance after that.
- Look for repeated runs. A run count that keeps growing means it is failing and being restarted. A restart of the Mac or a macOS update is the first thing to try.
When should you worry about warmd?
warmd is not a concern. A copy outside /usr/libexec would not be Apple's.
How do you check warmd in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type warmd 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 warmd 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 'warmd' | grep -v grep
sudo fs_usage -w -f filesys warmd
How can Thrum help with warmd?
Thrum's Disk tab shows read and write speed for the whole Mac, and its CPU and Memory tabs list warmd 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 warmd 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 warmd
Does warmd slow down startup?
It runs at low priority for CPU and disk, so other startup work goes first. Its purpose is to help startup and login use their caches.
Why can I not find warmd in Activity Monitor?
It normally finishes and exits shortly after startup.
Sources
- warmd(8) man page: run man warmd in Terminal
- launchd.plist(5) man page (Nice, LowPriorityIO, KeepAlive): run man launchd.plist in Terminal