Thrum

What is xpcproxy, and why does it appear in Activity Monitor?

Last reviewed: 19 November 2026. Path and man page checked on macOS 26.3.1.

xpcproxy is a small macOS helper that launchd uses to set up the execution environment of an XPC service or launchd job, after which it is replaced by the service itself. Each copy lives only a fraction of a second, so you see it only when services are being started. Many xpcproxy entries in a row mean something is starting services repeatedly, usually a job that keeps crashing.

xpcproxy at a glance

xpcproxy
Made byApple (part of macOS)
TypeLaunch helper (short-lived)
Location/usr/libexec/xpcproxy
Runs asthe account of the service it is starting (root, a system account or your user)
Can you quit it?There is nothing to quit. Each copy exists for a moment and then turns into the service it was starting.

What is xpcproxy?

The xpcproxy(8) man page describes it as an exec trampoline that configures the environment for an XPC service's execution. In practice, when launchd needs to start a job, it starts xpcproxy, which prepares the process (its environment, user and other settings from the job's definition) and then replaces itself with the real program using exec. The process ID stays the same, but the name changes from xpcproxy to the service's name.

Because of this, xpcproxy has no lasting job of its own and no launchd job label. A listing taken at the exact moment a service starts can show it, and tools that record process launches will list it as the first step of nearly every background service.

Is xpcproxy safe?

Yes. The real xpcproxy is at /usr/libexec/xpcproxy on the read-only system volume, and its parent is launchd (PID 1). Its man page says it is not intended to be invoked directly.

Why does xpcproxy use so much CPU?

How much CPU is normal for xpcproxy?

Typical: you rarely see xpcproxy at all, because each instance becomes another process almost immediately. Seeing it now and then, at 0% CPU, is normal.

If xpcproxy appears again and again with new PIDs every few seconds, a service is being relaunched in a loop.

How do you find out what xpcproxy keeps starting?

  1. Watch which process it becomes. In Activity Monitor, sort by PID. A process that keeps appearing with a new, higher PID right after xpcproxy entries is the service being started.
  2. Read the crash reports. Open Console and click Crash Reports. Many reports for one process name, with times a few seconds apart, identify the service that keeps failing.
  3. Check the launchd job. When you know the label, launchctl print gui/$(id -u)/<label> (or system/<label>) shows the job's program, its run count and its last exit status.
  4. Update or remove the app behind it. If the service belongs to a third-party app, update it or remove it, including its items in System Settings > General > Login Items & Extensions.

When should you worry about xpcproxy?

Look closer if xpcproxy shows up continuously while you are not opening apps, or if one copy stays as xpcproxy for a long time instead of turning into a service. The first means a crash loop; the second means a service is failing to start.

A program named xpcproxy outside /usr/libexec would not be Apple's.

How do you check xpcproxy in Activity Monitor and Terminal?

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

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

How can Thrum help with xpcproxy?

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

Why does xpcproxy disappear when I click on it?

By the time you select it, it has usually already replaced itself with the service it was starting. The same PID now shows the service's name.

Is xpcproxy related to proxy servers or VPNs?

No. Proxy here means a stand-in process that prepares an XPC service's environment before the service runs. It has nothing to do with network proxies.

Sources