Thrum

What is coreservicesd, and why is it running on my Mac?

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

coreservicesd is a macOS system daemon that provides services for the CoreServices frameworks, the low-level layer that the Finder, Launch Services and file handling are built on. Apple documents little more than that, and says it must not be terminated. It is normally idle; sustained high CPU is unusual and usually tied to heavy app or file activity.

coreservicesd at a glance

coreservicesd
Made byApple (part of macOS, CoreServices)
TypeSystem daemon
Location/System/Library/CoreServices/coreservicesd
Runs asroot
Started bylaunchd job com.apple.coreservicesd
Can you quit it?No. Its man page says it must not be terminated.

What is coreservicesd?

The coreservicesd(8) man page says only that it provides various services for CoreServices frameworks, is not meant to be invoked directly and must not be terminated. Its launchd job, com.apple.coreservicesd, runs it as root and offers one service, com.apple.CoreServices.coreservicesd.

Apple does not publish a list of what those services are, so this page does not guess. It sits next to lsd and launchservicesd in the CoreServices group of daemons.

Is coreservicesd safe?

Yes. coreservicesd is part of macOS at /System/Library/CoreServices/coreservicesd on the read-only system volume, runs as root and is started by launchd.

Why does coreservicesd use so much CPU and memory?

How much CPU is normal for coreservicesd?

Typical: near 0% CPU and a few megabytes of memory.

Steady high CPU for long periods is not normal for coreservicesd.

What can you do if coreservicesd uses a lot of CPU?

  1. Check which app is busy at the same time. In Activity Monitor, sort by CPU and see which app or helper is active together with coreservicesd. Quit it and see whether coreservicesd settles.
  2. Sample it. Select coreservicesd in Activity Monitor (View > All Processes) and choose View > Sample Process. The sample shows what it is doing and is useful for an Apple support case or a Feedback Assistant report.
  3. Restart the Mac. Because it must not be terminated on its own, a restart is the safe way to reset it.

When should you worry about coreservicesd?

Worry if it stays busy after a restart while you are not using any apps. That is unusual enough to report to Apple with a sample attached.

A coreservicesd outside /System/Library/CoreServices would not be Apple's.

How do you check coreservicesd in Activity Monitor and Terminal?

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

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

How can Thrum help with coreservicesd?

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

Why can't I find documentation for coreservicesd?

Apple's man page describes it in one sentence: it provides services for CoreServices frameworks. It is an internal component, and apps reach it only through those frameworks.

Should I force quit coreservicesd?

No. Its man page says it must not be terminated. Restart the Mac instead.

Sources