What is com.apple.CloudDocs.iCloudDriveFileProvider on my Mac?
Last reviewed: 19 November 2026. Path, bundle ID and extension point checked on macOS 26.3.1.
com.apple.CloudDocs.iCloudDriveFileProvider is the File Provider extension that connects iCloud Drive to Finder: it is iCloud Drive's equivalent of the extensions that OneDrive or Dropbox install. It works alongside bird and fileproviderd and is busy when iCloud Drive files are listed, downloaded or uploaded. It is part of macOS and safe.
com.apple.CloudDocs.iCloudDriveFileProvider at a glance
| com.apple.CloudDocs.iCloudDriveFileProvider | |
|---|---|
| Made by | Apple (part of macOS, iCloud Drive) |
| Type | File Provider extension |
| Location | /System/Library/PrivateFrameworks/CloudDocs.framework/PlugIns/com.apple.CloudDocs.iCloudDriveFileProvider.appex/Contents/MacOS/com.apple.CloudDocs.iCloudDriveFileProvider |
| Runs as | your user |
| Bundle ID | com.apple.CloudDocs.iCloudDriveFileProvider |
| Can you quit it? | Yes, but macOS starts it again the next time Finder or an app uses iCloud Drive. |
What is com.apple.CloudDocs.iCloudDriveFileProvider?
This process is an app extension inside Apple's CloudDocs framework. Its Info.plist names the extension point com.apple.fileprovider-nonui, the one used by File Provider extensions, and its display name is iCloudDrive. It is not started by a launchd job of its own; the system launches it when Finder or an app needs iCloud Drive.
In Apple's File Provider design, the system (fileproviderd) manages the local copies of files and the provider's extension handles syncing with its storage. For iCloud Drive, that sync work is shared with bird, the iCloud Drive daemon.
Is com.apple.CloudDocs.iCloudDriveFileProvider safe?
Yes. The extension is inside /System/Library/PrivateFrameworks/CloudDocs.framework on the read-only system volume and runs as your user. Activity Monitor shows the name of its executable file, which is the same as its bundle identifier; that is why the name is so long.
Why does com.apple.CloudDocs.iCloudDriveFileProvider use so much CPU and network?
- Browsing large iCloud Drive folders. Opening a folder with many items in Finder asks the provider to list its contents, which takes more work the more items there are.
- Opening files stored only in iCloud. Opening a file whose local copy was removed makes the system download it again through iCloud Drive.
- Large copies into iCloud Drive. Copying many files into iCloud Drive or Desktop and Documents (when those sync) creates work for each new item.
How much CPU is normal for com.apple.CloudDocs.iCloudDriveFileProvider?
It runs whenever iCloud Drive is in use and may appear and disappear in Activity Monitor. Brief activity while you browse or sync is normal; typically it is idle the rest of the time.
How do you stop com.apple.CloudDocs.iCloudDriveFileProvider from using so much CPU?
- Check iCloud Drive's status. In Finder, hold the pointer over iCloud Drive in the sidebar and click the status icon. If an upload or download is in progress, the extension is doing expected work.
- Wait for big transfers to finish. Keep the Mac online and awake until the status shows everything is up to date.
- Keep fast-changing folders out of iCloud Drive. Folders such as code projects and caches create constant changes. Store them outside iCloud Drive.
- Turn off Desktop & Documents if you do not need it. In System Settings, click your name, click iCloud, click Drive, and turn off Desktop & Documents Folders. Apple's guide explains what happens to the files when you do.
When should you worry about com.apple.CloudDocs.iCloudDriveFileProvider?
If it uses CPU for hours while iCloud Drive reports that it is up to date, look at bird's log with brctl log -w in Terminal, which shows what iCloud Drive is working on.
How do you check com.apple.CloudDocs.iCloudDriveFileProvider in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type com.apple.CloudDocs.iCloudDriveFileProvider in the search field. The CPU tab shows its % CPU. The Network tab shows its Sent Bytes and Rcvd Bytes. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every com.apple.CloudDocs.iCloudDriveFileProvider process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). nettop shows its live network traffic.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'com.apple.CloudDocs.iCloudDriveFileProvider' | grep -v grep
nettop -p <PID> # PID from the ps line above
How can Thrum help with com.apple.CloudDocs.iCloudDriveFileProvider?
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 com.apple.CloudDocs.iCloudDriveFileProvider 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 com.apple.CloudDocs.iCloudDriveFileProvider 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 com.apple.CloudDocs.iCloudDriveFileProvider
Why does it have such a long name?
Activity Monitor shows the extension's executable name, which matches its bundle identifier, com.apple.CloudDocs.iCloudDriveFileProvider. CloudDocs is Apple's internal name for the iCloud Drive framework.
Is it the same as bird?
No. bird is the iCloud Drive daemon; this is the File Provider extension that connects iCloud Drive to Finder through fileproviderd. They work together.