# bird and cloudd High CPU on Mac: Check iCloud Sync First > Check one iCloud Drive file in Finder and on iCloud.com before treating bird or cloudd CPU use as a sync failure. Preserve local changes and a separate backup. Published: 2026-09-28 Activity Monitor can show `bird` or `cloudd` using a lot of CPU while Finder is moving files through iCloud Drive. The process name alone does not tell you whether the work is progressing. Check the files first, then decide whether there is a sync problem. For a broader way to inspect unfamiliar services, see [Mac processes explained](https://mole.fit/blog/mac-processes-explained). This iCloud Drive check has a limit: macOS describes `cloudd` as a CloudKit daemon, and [CloudKit also syncs app data](https://developer.apple.com/documentation/cloudkit). If Finder shows no stuck Drive files, investigate which app's iCloud activity coincides with the CPU use; do not assume Drive is the source. ## Check the file, not just the CPU number In Finder, open iCloud Drive, switch to List view, then choose **View › Show View Options** and enable **iCloud Status**. Apple's [status guide](https://support.apple.com/guide/mac-help/mchlc994344b/mac) distinguishes a transfer in progress from **Waiting to Upload**, **Out of Space**, **Ineligible**, and a file that is **In iCloud** but not downloaded to this Mac. Hover over iCloud Drive in the sidebar and open its status icon for the overall transfer. Watch the same affected file and the sidebar status again after some time; a busy process is not proof of a completed upload.
Conceptual check of one iCloud Drive file in Finder, its copy on iCloud.com, and a separate backup copy
Follow one file from Finder to iCloud.com, then keep a separate backup. Matching copies show sync progress, not backup protection.
Open [iCloud.com Drive](https://www.icloud.com/iclouddrive/) with the same Apple Account and check whether the affected file and its latest change are there. If Finder says **Waiting to Upload** and iCloud.com still has the old version, preserve the local file before changing settings. If the file is only **In iCloud**, use Finder's **Download Now** before relying on an offline copy; **Keep Downloaded** can retain a local copy when Optimize Mac Storage is on ([Apple's iCloud Drive guide](https://support.apple.com/guide/mac-help/mchl1a02d711/mac)). ## Match the status to the next check | What you see | What to check | | --- | --- | | Transfer indicator moves and files appear on iCloud.com | Leave the Mac online and check the same file again. CPU can accompany ordinary transfer work. | | Waiting to Upload | Check the connection and available iCloud storage. Apple says a file can remain on the Mac until storage becomes available ([storage guide](https://support.apple.com/guide/mac-help/mchle5a61431/mac)). | | Out of Space or Ineligible | Read the Finder status before changing a file. An ineligible item is not uploaded merely because `bird` is busy. | | A permissions warning above iCloud Drive | Use Finder's **Repair** button for that specific warning, as described in [Apple's permissions guide](https://support.apple.com/guide/mac-help/mchlp1203/mac). | | No visible progress, with the same file unchanged on iCloud.com | Confirm **System Settings › Apple Account › iCloud › Drive › Sync this Mac** and the same account on both devices ([Apple's setup guide](https://support.apple.com/118443)). Then check the network and macOS updates. | Check Activity Monitor's CPU and Network views over time if the file status stays still. A sustained CPU reading is a reason to investigate, not a diagnosis of a corrupt sync database. Sample a process if you need to see what its threads are doing; do not treat a sample or a quiet CPU graph as proof that a particular file reached iCloud. ## Keep a recoverable copy before repair iCloud Drive synchronizes changes, including deletions, across devices ([Apple's Desktop and Documents guide](https://support.apple.com/109344)). It is not an independent backup. For an important file, verify that it is fully downloaded, then copy it to storage outside iCloud Drive or confirm a usable backup before trying a repair. Do not delete `~/Library/Application Support/CloudDocs`, sign out, or repeatedly force-quit `bird` and `cloudd` as a first step: none identifies the file that failed, and a local change waiting to upload may be the only current copy. If the same file remains stalled after the status, account, storage, permissions, and network checks, record its Finder status and whether its latest version appears on iCloud.com for Apple Support. That gives a concrete failure to investigate without sacrificing local data. ## FAQ ### Is high CPU from `bird` or `cloudd` always a fault? No. A large first sync or a batch of changed files can keep them busy. Check that the transfer indicator and the affected file actually advance; CPU by itself cannot answer that. ### Can I delete the CloudDocs folder to restart syncing? Do not use that as a default fix. First identify the affected file and keep an independent copy of any local version that has not uploaded. --- Canonical HTML page: https://mole.fit/blog/bird-cloudd-high-cpu-mac Blog index for agents: https://mole.fit/blog/llms.txt Site index for agents: https://mole.fit/llms.txt