Thrum

What is fileproviderd, and why is it using so much CPU on my Mac?

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

fileproviderd is the macOS daemon that sits between Finder and cloud storage apps that use Apple's File Provider system, including iCloud Drive and current versions of OneDrive, Dropbox and Google Drive. It is busy when one of those apps lists, downloads or uploads many files. It is part of macOS and safe; find the cloud app that is syncing and let it finish or reduce what it syncs.

fileproviderd at a glance

fileproviderd
Made byApple (part of macOS, File Provider)
TypeLaunch agent (background process for your user)
Location/System/Library/PrivateFrameworks/FileProvider.framework/Support/fileproviderd
Runs asyour user
Started bylaunchd job com.apple.FileProvider
Can you quit it?Not usefully. launchd starts it again when Finder or a cloud storage app needs it.

What is fileproviderd?

File Provider is Apple's framework for apps that sync documents from remote storage. On macOS 11 and later, a provider uses a replicated extension: the system manages the local copies and the app's extension only syncs data with its servers. fileproviderd is the system side of that arrangement. Its man page says it controls the interaction between file provider extensions and filecoordinationd, and coordinates enumeration (listing a folder's contents) and property lookup.

Each cloud service runs its own extension process, such as com.apple.CloudDocs.iCloudDriveFileProvider for iCloud Drive or OneDrive File Provider. fileproviderd runs once for your user and serves all of them, so its activity reflects whichever service is busy.

Is fileproviderd safe?

Yes. fileproviderd is part of macOS, in the FileProvider framework on the read-only system volume, and runs as your user. It is not a third-party sync client, even though it gets busy when third-party clients sync.

Why does fileproviderd use so much CPU and disk?

How much CPU is normal for fileproviderd?

Activity while a cloud app is syncing, and while you browse large cloud folders in Finder, is normal. When no provider is syncing, fileproviderd typically sits near 0% CPU.

How do you stop fileproviderd from using so much CPU?

  1. Find the provider that is busy. In Activity Monitor's CPU tab, look for a file provider extension or cloud app (iCloud Drive's extension, OneDrive, Dropbox, Google Drive) that is active at the same time. That service is generating the work.
  2. Let the sync finish. Check the provider's status: the iCloud Drive status icon in the Finder sidebar, or the menu bar icon of a third-party service. Activity drops when it reports that it is up to date.
  3. Keep busy folders out of synced locations. Move code projects, virtual machines and caches out of iCloud Drive, OneDrive, Dropbox and Google Drive folders so their constant changes are not synced.
  4. Pause or sign out of a provider you do not need. Third-party services have a Pause option in their menu bar app. Removing the account from the app removes its location from Finder and fileproviderd stops serving it.

When should you worry about fileproviderd?

Look closer if fileproviderd stays high for hours while every provider reports that it is up to date. fileproviderctl dump in Terminal prints the daemon's state for each provider, which can show the one with work outstanding.

If a provider's folder shows errors in Finder, fileproviderctl check runs Apple's consistency check on the File Provider database and reports problems without changing anything.

How do you check fileproviderd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type fileproviderd in the search field. The CPU tab shows its % CPU. The Disk tab shows its Bytes Written and Bytes Read. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every fileproviderd 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 'fileproviderd' | grep -v grep
sudo fs_usage -w -f filesys fileproviderd

How can Thrum help with fileproviderd?

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 fileproviderd 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. Click fileproviderd in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.

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 fileproviderd

Is fileproviderd part of OneDrive or Dropbox?

No. It is Apple's. Cloud apps that use the File Provider framework hand file management to it, which is why it gets busy when they sync.

Can I disable fileproviderd?

No. Finder needs it for iCloud Drive and for any cloud service built on File Provider. Remove or pause the provider instead.

Sources