What is fileproviderd on a Mac, and why is it busy?

27 October 2026 · 6 min read

fileproviderd is the part of macOS that connects cloud storage to Finder. When you open iCloud Drive, Dropbox or Google Drive in the Finder sidebar and see your cloud files next to your local ones, fileproviderd is a big part of how that works. It gets busy when a lot of files are changing, and it is safe to leave alone: it settles down when the sync finishes.

The name is short for “file provider daemon”. A daemon is a background program with no window. This one has no menu and no settings of its own. You only notice it when a process list shows it using the processor for a while.

What fileproviderd actually does

Cloud storage on a Mac has a problem to solve. Your files live on a server, but you want to see them in Finder, open them from any app, and drag them around as if they were on your disk. macOS handles this with a feature called File Provider. A cloud service plugs into it, and fileproviderd is the macOS side that keeps the two worlds in step.

In practice that means it:

Shows the cloud folder in Finder, including files that are online only and have not been downloaded yet.
Starts a download when you open an online-only file, and shows the cloud or progress icon in Finder while it happens.
Notices when you add, rename, move or delete a file in a synced folder, and passes that change on to the service.
Keeps track of which files are downloaded, which are waiting to upload, and which have a conflict.

It does not decide what gets synced and it does not store your files itself. The service you chose, whether that is iCloud Drive, Dropbox, Google Drive or another, does the actual transfer. fileproviderd is the link between that service and Finder. For the iCloud side of the story, what bird is on a Mac covers the iCloud Drive process, and what cloudd is covers iCloud sync for app data.

Why it is busy

fileproviderd works in proportion to how many changes it has to deal with. The usual causes are easy to spot once you know them.

A first sync, or a big one. The first time you sign in, or when you add a folder with thousands of files, fileproviderd has to learn about every one of them. That can take a long time and a good share of the processor. This is the most common reason you will see it near the top of a list.

Many files. A folder full of thousands of files costs more than one large file of the same total size, because each file is its own change to record. Project folders, code, photo libraries and anything with a lot of generated files are typical.

An app writing to a synced folder. If an app saves or rewrites lots of files inside a synced folder, such as a build tool, a video editor’s cache or a backup job, every write turns into work for fileproviderd. Moving that working folder out of cloud storage often stops the load completely.

Just after a restart or an update. After you start the Mac, or after a macOS update, the sync services check that everything still matches. Why your Mac is slow right after an update explains why a lot of background work bunches up in those first hours.

Online-only files being opened in bulk. If you select a whole folder of online-only files, or an app scans them (a search, a photo tool, a backup), they all download at once.

How to tell what it is doing

You can see whether fileproviderd is the cause with a few of macOS’s own tools.

Open Finder and look at the cloud folder. Files with a cloud icon are online only, and items that are uploading or downloading show a progress indicator. If many files show progress, a sync is under way.
Open the menu bar item for your cloud service, if it has one. Dropbox and Google Drive both show a sync status there, and some say how many files are left.
Check that you are still signed in and that the account is not full. For iCloud Drive that is in System Settings under your name, then iCloud; for other services it is in their own app. A stuck sign-in or a full cloud account can make a sync retry again and again, which looks like a process that never stops.
If you like Terminal, pgrep -l fileproviderd confirms it is running. It nearly always is, so that alone tells you nothing. What matters is whether it stays busy for hours, not whether it exists.

The Force Quit window (Option-Command-Escape) lists apps only, so fileproviderd will not appear there. It is a background process, not an app.

Is it normal for fileproviderd to use a lot of CPU?

For a while, yes. A sync that has a lot to do will keep fileproviderd busy for minutes or hours, and the fan may spin up with it. That is a sign of work, not a fault. It becomes worth acting on when:

It stays busy for more than a day with no new files being added.
The same files keep uploading again and again.
Your cloud service shows an error, or a file that never finishes.

In those cases the fault is usually on the service side, not with macOS. Pausing and resuming sync from the service’s own menu is a sensible first step. Making sure the account has free space and that you are signed in comes next. Restarting the Mac is a good test too, because it starts the sync services again from scratch.

Can you stop it?

You should not try to end fileproviderd itself. Finder depends on it to show your cloud folders, and macOS starts it again as soon as something needs it. Ending it only interrupts the sync you were waiting on.

What works better is to reduce the load it is responding to:

Pause syncing from the cloud service while you do something heavy, such as exporting video or building a large project.
Keep working folders for tools that write thousands of files outside your cloud folders.
Let a first sync finish with the Mac plugged in and awake rather than interrupting it again and again.
If you do not use a cloud folder at all, turn that service off in its own settings instead of fighting its process.

Seeing it in Foreman

Foreman is a Task Manager for macOS, and it shows fileproviderd in plain English. In the Processes page the row reads “Cloud files”, with the real name fileproviderd beside it in grey, and the description says it connects cloud storage (iCloud Drive, Dropbox, Google Drive) to Finder. Sort the CPU, Disk or Network column and you can see whether the Cloud files row is the one doing the work, next to the cloud service’s own app.

That answer matters. If Cloud files is busy and nothing else is, you are looking at a sync, and the right move is to wait or pause it. If a build tool or editor sits above it using far more, the app is the cause, and how to see which app is using the most CPU on a Mac shows how to find it.

fileproviderd runs under your own account, not as a system process, so Foreman offers Efficiency Mode for it. If a big sync is getting in the way of a call or an export, turn it on for Cloud files: while you work, it runs at background priority and is held to about a quarter of the processor time it would take. The sync carries on, only more slowly, and how much the rest of the Mac gains depends on how busy it is. Turn it off from the toolbar or the right-click menu when you are done and the sync runs at full speed again at once.

Foreman will not clean up your cloud files or speed up a sync, and it is not meant to. It tells you what is busy so you can decide. Foreman is free for 24 hours, then $12 once for up to 3 Macs.

A short checklist

fileproviderd connects cloud storage to Finder. It is not malware and not a leftover.
High use during a first sync, a big folder or a bulk download is normal.
Wait, pause the service, or move a heavy working folder out of cloud storage.
Do not end it. macOS restarts it, and you only break the sync you are waiting for.
If it stays busy for a day with no new files, look at the service’s sign-in and storage first.