fileproviderd High CPU on Mac: Find the Busy Cloud App
When fileproviderd stays near the top of Activity Monitor, first find which cloud account is busy. Deleting a sync folder or resetting every cloud app makes that harder and can put local changes at risk. Start with one provider, one pause, and a comparison before and after.
What fileproviderd Is Doing
Apple's File Provider system connects cloud services to Finder and the file system, as its deployment documentation explains. The system daemon fileproviderd coordinates provider extensions and file information. Its name alone does not identify the account responsible.
Dropbox on File Provider, Google Drive streaming on macOS 12.1 and later, and Box Drive's File Provider architecture are documented by their vendors. Dropbox also retains a legacy mode, so check the installed app rather than assuming every installation works identically.
Microsoft also documents OneDrive's File Provider implementation on macOS 12.3. Include iCloud Drive in your account inventory too. For an iCloud-specific investigation involving other processes, use the separate bird and cloudd guide.
Separate Progress From a Repeating Problem
Dropbox's CPU troubleshooting guide identifies initial synchronization, large file counts, other apps repeatedly touching files, and permissions as reasons for work. These are useful hypotheses, not proof that Dropbox owns your particular CPU spike.
| Observation | What to check | Next step |
|---|---|---|
| A new account or large folder was added | Whether the app's pending work is decreasing | Let that batch progress before resetting anything |
| Many small files keep changing | Which folder and writing app are involved | Stop that writer temporarily, then compare |
| The same file keeps returning | The provider's error and conflict information | Preserve both versions before resolving it |
| CPU stays high without visible progress | Which account responds to a pause | Isolate that provider before escalation |
A large folder and a folder containing many small files are different workloads, so record both approximate size and file count when asking support. Do not infer a broken database from CPU usage alone.
Identify the Provider in Finder
Open each installed cloud app and note its account, current sync message and any named file. Then inspect the corresponding Finder sidebar entry, without moving files between locations.
Google documents its File Provider location under Finder's Locations, normally backed by ~/Library/CloudStorage. Its macOS guide also explains how to confirm File Provider in Drive's preferences. Use the app's displayed location when your setup differs, not a guessed folder name.
Do not delete ~/Library/CloudStorage or ~/Library/Application Support/FileProvider to test a theory. Google specifically warns that dragging a streamed file out of its location can move it and trash the cloud file. Copy wanted data to an independent location and open the complete copy before a reset. Synchronization is not an independent backup.
Pause One App and Compare
Use Apple's Activity Monitor CPU view to observe fileproviderd while keeping the same workload. Record the provider's sync message alongside CPU activity.
- In Dropbox, click its menu bar icon, then the sync-status text at the bottom to choose a pause, following its pause instructions.
- For Google Drive, use the app's pause control described in its desktop guide. While File Provider sync is paused, new file downloads are unavailable.
- For OneDrive, Control-click its menu bar cloud and choose a pause duration using Microsoft's instructions. Resume from the paused app afterward.
- Test only one app at a time, resume it, then test another if needed. For Box or iCloud, do not substitute an account sign-out for a pause that you cannot find.
If CPU falls during one pause and rises after resuming that app, that is evidence of an association, not proof of a corrupt file. If nothing changes, restore normal syncing and keep investigating rather than resetting that account.
Resolve the Named Work Before Resetting
For an error naming a file, check that file in the app and on the provider's website. Dropbox explains conflicted copies as separate versions created around overlapping edits. Compare and preserve the needed edits instead of deleting every duplicate name.
If a writing app is repeatedly updating the same folder, close that app for the comparison. Once the queue completes, check that a recent important file opens both locally and on the website, then observe CPU again under the same conditions.
There is no universal idle-CPU threshold or guaranteed completion time here. A falling queue and usable files are more useful evidence than waiting an arbitrary number of minutes.
When to Reset One Provider
Consider a provider-specific reset only after the same account remains stuck, pausing has implicated it, and recent local-only work has an independent verified copy. Keep the account name, sync location and error message for support.
Microsoft's OneDrive reset procedure uses the reset script inside the installed app, with different filenames for its editions. Follow that page for your edition, finish setup, and recheck folder selection. Do not apply its procedure to Dropbox, Drive, Box or iCloud.
If reinstalling is actually necessary, the separate Dropbox removal guide and Google Drive removal guide cover that larger operation. The tested-app records for Dropbox, Google Drive and OneDrive describe removal boundaries, not signed-in sync recovery guarantees.
Where Mole Fits
Mole Mac's Clean scanner has cloud-cache entries, but cache removal is not a File Provider reset. Use the provider's own controls for this diagnosis, rather than treating a cache row as a repair for the account's sync state.
FAQ
Does fileproviderd Mean iCloud Is Responsible?
No. Identify the active account and compare one provider at a time, rather than assigning the process to iCloud from its name.
Should I Delete the CloudStorage Folder?
No. Inspect the provider's location and preserve complete independent copies before account maintenance, without deleting the shared parent folder.
What If Pausing Does Not Lower CPU?
Resume syncing, keep the before-and-after observations, and investigate other providers. A pause without a change does not justify resetting that account.