What is trustdFileHelper on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
trustdFileHelper is a small helper daemon that modifies files on behalf of trustd, the part of macOS that checks whether certificates can be trusted. It runs as root because trustd itself runs under a restricted account. It is part of macOS, uses almost no CPU or memory, and needs no action.
trustdFileHelper at a glance
| trustdFileHelper | |
|---|---|
| Made by | Apple (part of macOS, Security framework) |
| Type | System daemon (helper) |
| Location | /usr/libexec/trustdFileHelper |
| Runs as | root |
| Started by | launchd job com.apple.trustdFileHelper |
| Can you quit it? | Not usefully. launchd starts it again when trustd needs it. |
What is trustdFileHelper?
Its man page says only that trustdFileHelper "provides services to trustd for modifying files". trustd runs as the limited system account _trustd; trustdFileHelper runs as root and is started by launchd through the com.apple.trustdFileHelper job when trustd needs a file changed that its own account cannot write.
Apple does not document which files those are, so this page does not guess. What can be checked is that the helper is tiny (a few megabytes of memory), signed by Apple, and only runs while trustd has work for it.
Is trustdFileHelper safe?
Yes. It lives in /usr/libexec on the read-only system volume and its launchd job is defined in /System/Library/LaunchDaemons/com.apple.trustdFileHelper.plist. Splitting file changes into a separate root helper keeps trustd itself running with fewer privileges.
Why does trustdFileHelper use so much CPU, disk and memory?
- Brief work for trustd. It wakes when trustd asks it to change a file and goes idle again. Activity is a short blip, not sustained use.
- Small file writes. Because its job is changing files, any disk activity it shows is small writes made for trustd.
- Resident while launched. Once launched it may stay in memory for a while. A few megabytes is typical and macOS reclaims it when needed.
How much CPU is normal for trustdFileHelper?
0% CPU nearly all the time, with occasional short blips, and a few megabytes of memory. It may or may not be running at any given moment; both are normal.
How do you stop trustdFileHelper from using so much CPU?
- Confirm it is Apple's. In Terminal, run
ps -axo user,pid,comm | grep trustdFileHelper. The path should be/usr/libexec/trustdFileHelperand the user root. - Look at trustd instead. If you see the helper often, check whether trustd is busy and follow the steps on that page; the helper only works when trustd asks it to.
- Restart if it never goes idle. Sustained activity from the helper is not expected. A restart starts trustd and its helper fresh.
When should you worry about trustdFileHelper?
A trustdFileHelper using noticeable CPU for minutes at a time would be unusual. Note what you were doing and check trustd's activity at the same moment.
A process with this name running from a path other than /usr/libexec would not be Apple's.
How do you check trustdFileHelper in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type trustdFileHelper in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every trustdFileHelper 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 'trustdFileHelper' | grep -v grep
sudo fs_usage -w -f filesys <PID> # PID from the ps line above
How can Thrum help with trustdFileHelper?
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 trustdFileHelper 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 trustdFileHelper
Why does trustdFileHelper run as root?
trustd runs under the limited _trustd account. File changes that need more access are handed to this separate root helper so that trustd itself does not need root rights.
Can I delete trustdFileHelper?
No. It is on the read-only system volume, which macOS protects, and trustd depends on it.
Sources
- trustdFileHelper(8) man page: run man trustdFileHelper in Terminal
- trustd(8) man page: run man trustd in Terminal