What Is fileproviderd on a Mac? Fixing High CPU

Activity Monitor shows a process called fileproviderd using CPU while you are not touching anything, and the name gives nothing away. It often appears after you have signed in to iCloud, installed OneDrive, or copied a big folder into synced storage.

The short answer: fileproviderd is the daemon behind the File Provider feature in macOS, the layer that presents cloud storage such as iCloud Drive and OneDrive as ordinary folders on your Mac. It coordinates the per-service extensions that do the actual syncing, and it answers the system's questions about which files exist and what state they are in. It is safe. It gets busy when a provider has a lot of work, such as a large upload or download, a fresh sign-in, or a service with files that keep changing, and it settles when that work is done. Quitting it does nothing, because macOS starts a new copy the moment one is needed.

What fileproviderd does

Apple's manual page describes fileproviderd as "the daemon controlling the interaction between extensions and filecoordinationd", and says it is "responsible for coordinating enumeration and property lookup". In practice: macOS shows your cloud files through the File Provider framework, each cloud service supplies an extension that does the syncing, and fileproviderd is the coordinator that connects those extensions to the rest of the system. filecoordinationd is the older coordinator apps use to share access to files safely, and the two work together.

On our test Mac, running macOS 27.0.1, fileproviderd ran under the logged-in user's account from:

/System/Library/PrivateFrameworks/FileProvider.framework/Support/fileproviderd

It is started by the LaunchAgent com.apple.FileProvider in /System/Library/LaunchAgents/. Three details in that file explain how it behaves:

• It can exit when idle. The EnablePressuredExit and EnableTransactions keys let macOS stop it when nothing needs it and start it again on demand. If it disappears from Activity Monitor, that is normal.
• It has a daily maintenance pass. A background task named fpfs.telemetry repeats every 86,400 seconds at Maintenance priority, so fileproviderd can wake briefly once a day on its own.
• It watches your synced-storage folder. The agent registers a file-system event on ~/Library/CloudStorage, which is where File Provider volumes appear. On our Mac that folder holds OneDrive-Personal; iCloud Drive's own store lives elsewhere, in ~/Library/Mobile Documents, but it reaches the system through the same daemon and its own extension.

One of its services, com.apple.corespotlight.daemon.fileprovider, is how Spotlight queries cloud providers. Our corespotlightd guide covers the indexing side of Spotlight.

Is fileproviderd safe?

Yes. It is part of macOS, it runs under your own user account, and it starts from the system framework path shown above. To check the copy on your own Mac:

ps -axo user,pid,pcpu,comm | grep fileproviderd

It should appear under your user name, running from inside /System/Library/PrivateFrameworks. A process with the same name running from anywhere else would be worth investigating.

The extensions it serves

fileproviderd itself holds almost none of your files. The work happens inside extensions: Apple's File Provider documentation says macOS creates one extension instance for each File Provider domain, and each domain appears as a location in the Finder's sidebar. Listing the registered providers on our test Mac:

$ pluginkit -m | grep -i fileprovider
com.apple.Photos.PhotosFileProvider(12.0)
com.apple.FileProviderDaemon.diagnostic(1.0)
com.apple.CloudDocs.iCloudDriveFileProviderManaged(1.0)
com.microsoft.OneDrive-mac.FileProvider(26.168.0830)
com.apple.CloudDocs.iCloudDriveFileProvider(1.0)

iCloud Drive's own provider, Microsoft OneDrive's, and the one Photos uses to browse your library are all in the list. Google Drive for desktop uses File Provider on macOS 12.1 and later, and Dropbox documents File Provider support for its Mac app.

Why fileproviderd uses CPU

The daemon coordinates work rather than doing the heavy lifting itself, so its CPU rises when a provider has a lot to do:

• A new Mac or a fresh sign-in, when your iCloud Drive or OneDrive contents download for the first time.
• A large folder added to synced storage, which has to upload in full.
• A provider catching up after days offline, or after a service outage.
• Files that change constantly in a synced folder, such as build output or a database, which keep the extension and its coordinator working all day.
• The daily telemetry pass described above, which is brief and Maintenance priority.

An important honest note: we measured the ordinary case, and it is cheap. Our iCloud Drive library holds 23,238 files; walking 2,000 of them with stat, and a separate pass of mdls property lookups over 200 files, added 0.01 seconds at most to fileproviderd's CPU time. Browsing an up-to-date library is nearly free. Sustained, visible CPU means real sync work is happening, or an extension is stuck, and in both cases the cause is a specific provider.

Over the four days our test Mac had been up, fileproviderd had used five and a half minutes of CPU in total, about 0.09% of one core on average, while sitting at 26 MB of memory. If yours shows minutes of CPU per hour instead, a provider is genuinely working.

How to find which provider is busy

• Ask the daemon what it has open. fileproviderd runs under your own account, so Activity Monitor can inspect it: double-click it and open the Open Files and Ports tab. Paths that keep appearing name the service that is busy.
• Watch the extensions instead. Each provider's extensions run as their own processes with recognisable names, such as iCloud Drive's com.apple.CloudDocs.iCloudDriveFileProvider or OneDrive's File Provider extension. The one using CPU is the one doing the syncing.
• See which services are mounted. Run:

ls ~/Library/CloudStorage

Every volume listed there is a File Provider service on your Mac.

• Check iCloud Drive's own status. The brctl command reports whether iCloud Drive has caught up with the server, and our bird guide explains how to read it.

What helps, and what does not

• Let the sync finish. For a new sign-in or a large folder, leave the Mac on, online and plugged in. This is the single most common cause, and it ends on its own.
• Pause the service that is busy. OneDrive has a pause control in its menu bar app. We know of no pause control for iCloud Drive; turning Drive off in System Settings works, but that is a heavier action than waiting. For other providers, check the app you use.
• Keep churn folders out of synced storage. Folders that an app rewrites constantly keep both the extension and fileproviderd busy forever. Move them outside ~/Library/CloudStorage and iCloud Drive.
• Restart the Mac if a provider seems stuck. A restart relaunches every provider and the daemon cleanly.
• Do not bother quitting fileproviderd. In our test on macOS 27, we sent it a normal quit signal and macOS started a new copy in under a second. It is also part of macOS, so it cannot be removed; that is by design, since every cloud folder on the Mac depends on it.

See it in your menu bar

fileproviderd runs under your own account, so MacStats can see it, along with the provider extensions that are doing the work. When one is busy it appears in MacStats' Top CPU list, and with MacStats Pro clicking it gives you a plain-English explanation of what it is doing and whether you need to act. The transfers themselves usually ride on nsurlsessiond, which our nsurlsessiond guide covers, and MacStats' menu bar shows your live upload and download speed, so a big sync is obvious the moment it starts.

See which process is busy before the fans tell you.

Download MacStats for Free

Frequently asked questions

What is fileproviderd on a Mac?

It is the macOS daemon behind the File Provider feature, the layer that presents cloud storage such as iCloud Drive and OneDrive as folders. Apple's manual page describes it as controlling the interaction between extensions and filecoordinationd, and coordinating enumeration and property lookup.

Why is fileproviderd using so much CPU?

Because a cloud provider has a lot of work: a fresh sign-in downloading your files, a large folder uploading, a service catching up after being offline, or files that change constantly. It settles when the syncing is done.

Is fileproviderd safe?

Yes. It is part of macOS and runs from the system FileProvider framework under your own account. A process with that name running from anywhere outside /System/Library/PrivateFrameworks would be worth investigating.

Can I quit fileproviderd?

You can, but it does not help. In our test on macOS 27, macOS started a new copy in under a second after we quit it. It is part of macOS and cannot be removed.

What is the difference between fileproviderd and bird?

bird is the process that syncs iCloud Drive itself. fileproviderd is the File Provider coordinator that serves iCloud Drive, OneDrive and other provider services to the rest of macOS. On macOS 27 both run at the same time, and our bird guide explains the syncing side.

How do I stop fileproviderd using high CPU?

Find which provider is busy using Open Files and Ports in Activity Monitor or the provider's own extension process, then let the sync finish or pause that service in its app, and keep folders that change constantly out of synced storage.