Thrum

What is filecoordinationd, and why is it using CPU?

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

filecoordinationd coordinates access to files between processes, so that when one app reads, writes, moves or deletes a file, other apps that have it open are told first. It uses CPU when apps coordinate many file operations, such as during cloud syncing. It is part of macOS and safe.

filecoordinationd at a glance

filecoordinationd
Made byApple (part of macOS, Foundation)
TypeSystem daemon
Location/usr/sbin/filecoordinationd
Runs asroot
Started bylaunchd job com.apple.FileCoordination
Can you quit it?Not usefully. Apps that coordinate file access would stall until launchd started it again.

What is filecoordinationd?

Its man page says it is used by Foundation's NSFileCoordinator class to coordinate access to files by multiple processes and to message registered NSFilePresenter objects. Apple's documentation describes the idea: before an app changes a file, the coordinator lets other interested objects prepare, for example by learning the file's new location if it is being moved.

Because this works across apps, the coordination runs through one system daemon. Its launchd job also publishes a progress reporting service, which apps use to show the progress of file operations.

Is filecoordinationd safe?

Yes. It is at /usr/sbin/filecoordinationd, runs as root, and is signed by Apple (com.apple.filecoordinationd). The man page says it has no configuration options.

Why does filecoordinationd use so much CPU and memory?

How much CPU is normal for filecoordinationd?

Typically near 0% CPU, with short bursts when apps save or sync files. Higher use during a big sync is expected and stops when the sync finishes.

How do you stop filecoordinationd from using so much CPU?

  1. Find the app doing file work. In Activity Monitor, check the Disk tab for an app writing a lot and the CPU tab for sync clients. The busy app is the real source.
  2. Let a sync finish or pause it. If a cloud service is uploading or downloading many files, let it finish or pause it in that service's settings.
  3. Close documents you are not using. Fewer open documents means fewer presenters to notify about each change.
  4. Restart the app that started it. If filecoordinationd stays busy after a sync finished, quitting and reopening the sync app or document app often ends it.

When should you worry about filecoordinationd?

Look into it if filecoordinationd stays at high CPU with no sync or file activity, or if apps hang while opening or saving files. A restart resets all coordination.

A process with this name outside /usr/sbin would not be Apple's.

How do you check filecoordinationd in Activity Monitor and Terminal?

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

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

How can Thrum help with filecoordinationd?

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

Can I disable file coordination?

No. It is part of how macOS prevents apps from overwriting each other's changes to the same file.

Why does it run as root?

It coordinates access between processes of every user, so it runs as a system daemon.

Sources