Thrum

What is trustd, and why is it using CPU on my Mac?

Last reviewed: 19 November 2026. Path, accounts, launchd jobs and man page checked on macOS 26.3.1.

trustd is the macOS daemon that evaluates whether a certificate can be trusted, for example the certificate a website presents when an app opens a secure connection. It is busy when many apps make new secure connections at once, such as after waking from sleep or when a browser loads many sites. It is part of macOS, safe, and usually settles within seconds.

trustd at a glance

trustd
Made byApple (part of macOS, Security framework)
TypeSystem daemon and per-user agent
Location/usr/libexec/trustd
Runs as_trustd (a system account), plus one copy for each logged-in user and some system accounts
Started bylaunchd job com.apple.trustd
Can you quit it?Not usefully. launchd starts it again the next time an app needs a certificate checked.

What is trustd?

trustd provides certificate trust evaluation for every process on the Mac. Its man page describes it as the daemon and launch agent "that performs trust evaluations". When an app receives a certificate, from a web server, a mail server, a VPN or a signed document, it asks trustd whether the certificate chains up to a trusted root and is valid under the right policy, instead of doing that work itself.

There are two launchd jobs. com.apple.trustd runs as the system account _trustd, and com.apple.trustd.agent runs a separate copy for each user session. On a typical Mac you therefore see several trustd processes, one owned by _trustd, one owned by you, and sometimes others owned by system accounts such as _locationd. A helper, trustdFileHelper, changes files on its behalf.

Is trustd safe?

Yes. trustd lives in /usr/libexec on the read-only system volume and is started by launchd from a property list in /System/Library/LaunchDaemons. Several copies running at once is normal and does not mean anything is wrong. A process called trustd anywhere else on disk would not be Apple's.

Why does trustd use so much CPU and memory?

How much CPU is normal for trustd?

Short spikes of a few percent CPU when apps connect to servers are normal, and so is a burst right after the Mac wakes. Each copy usually sits at or near 0% CPU between those moments.

Seeing four or more trustd processes in Activity Monitor is normal: one for the system account, one for your session, and one for some system accounts that run their own services.

How do you stop trustd from using so much CPU?

  1. Check which copy is busy. In Activity Monitor, choose View > All Processes, search for trustd and look at the User column. A busy copy owned by your account points to an app in your session; a busy _trustd copy points to system services.
  2. Find the app making connections. Open the Network tab in Activity Monitor and sort by Sent Bytes or Rcvd Bytes. An app that is constantly connecting is the most likely reason trustd stays busy.
  3. Quit and reopen that app. Quitting an app that keeps reconnecting usually brings trustd back to near 0% within seconds.
  4. Review proxy and traffic inspection tools. If you use a VPN, proxy, content filter or security product that inspects encrypted traffic, check whether trustd calms down when it is paused. Contact the vendor if it does.
  5. Restart the Mac. If trustd stays high with no obvious cause, a restart clears its caches and starts it fresh.

When should you worry about trustd?

Look closer if trustd stays above roughly 20% CPU for many minutes while you are not opening apps or websites. That usually means one app is retrying a connection in a loop, which the Network tab can reveal.

Certificate warnings in apps that used to work without them are not caused by trustd itself; they come from the certificate the server presents or from a tool on the Mac that intercepts connections.

How do you check trustd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), choose View > All Processes, and type trustd in the search field. The CPU tab shows its % CPU. 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 trustd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'trustd' | grep -v grep

How can Thrum help with trustd?

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

Why are there several trustd processes?

macOS runs one trustd as the system account _trustd and a separate copy for each user session, and some system accounts get their own copy. Each copy answers requests from processes in its own context.

Can I quit trustd?

You can, but launchd starts it again as soon as any app needs a certificate checked, and secure connections wait until it is back. There is no benefit to quitting it.

Why is trustd running as _locationd or other odd accounts?

The agent copy of trustd runs once for each account that has its own set of running services. Some macOS system accounts, such as _locationd, run services of their own, so they get a copy too.

Sources