fileproviderd on Mac: the cloud-folder sync engine, which app is driving it, and what to do

What fileproviderd does

Since macOS 12.1, cloud storage apps are not allowed to patch the Finder the way they used to. Instead they write a File Provider extension, and macOS runs the actual syncing for them inside one shared system process: fileproviderd, which lives at /System/Library/Frameworks/FileProvider.framework/Support/. iCloud Drive was the first client. Dropbox, OneDrive, Google Drive, Box and others moved onto it during 2022 and 2023, which is when people started noticing the name.

fileproviderd owns the clever parts. It keeps placeholder files on disk so a 50 GB Dropbox folder can show in Finder without taking 50 GB, downloads the real file when you open it, uploads your edits, draws the cloud and checkmark badges, and watches every one of those folders for changes. The cloud app itself just tells it what is in the account and moves bytes when asked.

One process doing the work for several apps is efficient, but it means Activity Monitor hides the culprit. When fileproviderd is at 80 percent, the question is never whether to quit it. The question is which client is feeding it.

What normal looks like

How busy fileproviderd gets depends on how much the cloud folders changed, and on which client it is:

Memory is normally a few hundred megabytes. The accounts of trouble are almost all about CPU and time, and in the Apple Community they cluster around specific client updates. In one thread the first poster traced it to a OneDrive update from the previous week; another in the same thread found the latest Google Drive update was the problem. That is the pattern: fileproviderd goes wrong when a client changes, not on its own.

Why fileproviderd is using CPU right now

1. A big sync is in progress. You just installed a cloud client, added a large shared folder, or dropped a project into iCloud Drive. Placeholders and uploads for thousands of files take time. This is the normal case and it ends.
2. A cloud client just updated. New versions of Dropbox, OneDrive and Google Drive have each caused fileproviderd loops at some point. The client re-scans everything, sometimes repeatedly.
3. A ghost extension. You uninstalled a cloud app but its File Provider extension is still registered. fileproviderd keeps trying to serve a provider that no longer answers. Reinstalling and properly signing out of that app clears it.
4. Two clients fighting over one folder. A folder inside Dropbox that is also inside iCloud Drive, or a Git repository inside a cloud folder, generates changes faster than they can be synced.
5. Low disk space. Downloads fail, the client retries, fileproviderd stays busy. Freeing space stops the loop.
6. Spotlight following behind. Every synced file is also a new file for mdworker, so the two often climb together. That is still the sync's fault, not Spotlight's.

How to tell which cloud app is driving it

Three quick ways, no terminal needed:

Look at the badges. Open Finder and click each cloud folder in the sidebar: iCloud Drive, Dropbox, OneDrive, Google Drive. The one whose files show spinning or syncing badges is the one feeding fileproviderd.

Look at the menu bar. Each cloud app has a menu bar icon with a sync status. One will say Syncing 2,431 files, or show a progress bar. That is your answer.

Pause one at a time. Every client has a Pause Syncing option in its menu bar icon. Pause Dropbox, wait a minute, look at Activity Monitor. If fileproviderd drops, you found it. If not, resume Dropbox and pause the next one. This isolates the client in under five minutes without quitting anything.

In Activity Monitor you can also select fileproviderd, click the i button, and open Open Files and Ports. The paths it is working on name the folder, and the folder names the app.

Is it safe to quit fileproviderd?

Yes. Nothing is lost: every client keeps its own record of what is synced, and uploads resume. But macOS relaunches fileproviderd immediately, every registered client reconnects, and the same work starts again. One user in the OneDrive thread followed the advice to restart the process and reported, with some disappointment, that the problem persisted.

The useful version of quitting is quitting the client, not the daemon. Quit Dropbox from its menu bar icon and fileproviderd stops doing Dropbox's work. That is both safe and effective, and it points you straight at the cause.

Check any other name from Activity Monitor above. For fileproviderd the verdict is: leave it, find the client.

What to do, in order

1. Identify the client

   Use the badges, the menu bar icons, or the pause-one-at-a-time test from the section above. Do this first; everything else depends on knowing which app it is.

2. Let a real sync finish

   If the client shows a falling count of files, it is working. Leave the Mac on power and let it finish. An hour is normal for a large account. Nothing else needed.

3. Pause the client if you need the Mac quiet

   Pause Syncing from the client's menu bar icon. fileproviderd drops within a minute. Resume when you are done. Nothing is lost.

4. Update the client, or wait for the fix

   If the loop started right after a client update, check for a newer version. Dropbox, OneDrive and Google Drive have all shipped fixes for fileproviderd loops within days of causing them.

5. Sign out and back in to that client

   Quit the client, open it again, sign out of the account in its preferences, then sign back in. It rebuilds its view of the account and re-registers its File Provider extension cleanly. Your files stay in the cloud; placeholders are recreated.

6. Remove ghost extensions

   Open System Settings, go to General, then Login Items & Extensions, and look under File Providers. Any cloud app listed there that you no longer use can be turned off. If one belongs to an app you deleted, reinstall it, sign out, then uninstall it properly.

7. Free space and restart

   Keep 10 to 20 GB free so downloads stop failing. Then restart the Mac once. If fileproviderd is still pinned after all of this with the client paused, report it to that client's support, because the fault is in their extension.

When to worry

fileproviderd is part of macOS and not a security concern. The worry is about work not finishing. Signs it is stuck rather than busy:

• High CPU for more than a day with no new or changed files.
• A cloud folder whose badges spin forever, or a menu bar status that shows the same count for hours.
• The problem started the day a cloud client updated.
• Pausing every client still leaves fileproviderd busy, which points to a ghost extension.

Your files are not at risk in any of these. The cloud copy is intact and the local copy is either a placeholder or a complete file. These are stalls in the sync, and the client-level fixes above resolve them. The trend over time is what tells busy from stuck, and Safe to Quit tracks that for every process so you can see whether fileproviderd is winding down or flat.