bird process on Mac: what it is, why it is high, what to do

What bird does

The name is an Apple in-joke (the original internal codename for iCloud Drive's engine), which is why nobody can guess what it is from Activity Monitor. bird runs under your user account and does three things: watches your iCloud Drive folders for changes and uploads them, listens for changes made on your other devices and downloads them, and keeps the bookkeeping that lets Finder show those little cloud and progress icons next to each file.

It works with two other processes. cloudd handles CloudKit, the database side of iCloud that apps like Notes and Reminders use. fileproviderd is the newer layer (since Monterey) that presents cloud files to Finder and lets third-party services like Dropbox plug in. On recent macOS versions you often see bird and fileproviderd busy together; that is one sync job.

It is not iCloud Photos (that is cloudphotod) and not iCloud Backup, which Macs do not have. If Photos is uploading, bird is not the one doing it.

Why bird is using CPU right now

1. A lot just changed. You dropped a project folder into iCloud Drive, turned on Desktop & Documents, or imported a big batch of files on your iPhone that now need to land on the Mac. Thousands of small files take longer than one big one, because each is a separate upload with its own metadata.
2. A new Mac or a fresh sign-in. bird has to compare everything in the cloud with everything on disk. For a large Drive that is hours of work, mostly while you are not looking.
3. A macOS update. Updates often reset parts of the sync state and bird re-scans.
4. One file it cannot finish. This is the case behind most "bird at 100 percent for days" threads. A file that is too large for iCloud, a file an app holds open and keeps rewriting (a database, a virtual machine image, an Outlook or Lightroom catalog), a name with characters the server rejects, or an item whose permissions are wrong. bird retries it forever and the rest of the queue waits behind it. A MacRumors user described the symptom exactly: "some 'bird' process just sits there at 100% CPU usage all the time without actually accomplishing anything."
5. An app writing constantly into a synced folder. Every save is an upload. Put an active Git repository, a Docker volume or a Photos library inside iCloud Drive and bird never rests.
6. A memory leak in a specific version. Reported on Ventura in particular. If bird's memory grows into many GB, a restart clears it and an update fixes it.

What normal looks like, and what is not

Sync time depends on how much changed and how many files it is split into. These are typical shapes on a home broadband connection:

How to tell the difference without guessing: open Finder, click iCloud Drive in the sidebar, and choose View, Show Status Bar (and View, as List, then View, Show View Options, tick iCloud Status). You get a per-file status column: Downloaded, Waiting to Upload, Uploading with a percentage. A healthy sync has the percentages moving. A stuck one has the same item at the same percentage an hour later. Hacker News users keep passing along the same first step: "In Finder, enable the Status bar."

Also normal: bird pausing when the Mac is on battery with Low Power Mode on, when the network is metered, or when the lid is closed. A big sync that only runs while you are at your desk can take days of calendar time and still be healthy.

Is it safe to quit bird?

Yes in the narrow sense: nothing is lost. iCloud Drive keeps its own record of what has and has not synced, bird restarts within seconds and carries on. It is the most common advice in forums because it feels like doing something, and sometimes it does unstick a transfer for a while. It does not fix the file that caused the jam, so it comes back. The May 2024 Apple thread on this settled on the same conclusion: "Turning off and back on iCloud from Sys Preferences sometimes succeeds, oftentimes doesn't."

What is not safe: deleting ~/Library/Application Support/CloudDocs or anything under it. That is iCloud Drive's local database. Removing it can turn a stuck sync into missing files. The decision tree covers the general rule:

So the plan is: identify the stuck file, move it out, let the queue drain. Quitting bird is at best step zero.

What to do, in order

1. Check what is actually syncing

   Finder, iCloud Drive, View, Show Status Bar. The bar at the bottom shows items waiting or uploading. Switch to List view and add the iCloud Status column via View Options to see per-file progress. If numbers move, it is working. Give it time, plugged in, lid open.

2. Find the item that is not moving

   Sort by the iCloud Status column. The one stuck at "Waiting to Upload" or a fixed percentage for an hour is the jam. Common culprits: very large files, files an app keeps open (databases, VM images, catalogs), packages with thousands of files inside, and names with unusual characters.

3. Move it out of iCloud Drive

   Drag the stuck item to a local folder (Documents on this Mac, or anywhere outside iCloud Drive). bird gives up on it and the rest of the queue proceeds within minutes. Keep it local, or zip it and put the zip back in.

4. Keep live data out of iCloud Drive

   Move active Git repositories, Docker and VM files, email and photo catalogs, and Photos libraries out of synced folders for good. They are the files that never finish because they never stop changing.

5. Restart

   Clears a leaked bird process and resets the sync engine. The most reliable version of "force quit bird."

6. Update macOS

   Sync engine bugs, including the Ventura memory leak, were fixed in later point releases. System Settings, General, Software Update.

7. Sign out of iCloud Drive and back in, last resort

   System Settings, your name, iCloud, iCloud Drive, turn it off (keep a copy when asked), restart, turn it on. This rebuilds the local sync state and re-downloads everything, which takes hours and uses a lot of bandwidth. That is why it is last, not first, however often forums suggest it.

When to worry

bird is not a security concern and it does not delete files on its own. The cases that deserve attention:

• A file is on this Mac but not on iCloud.com after a day. That file is the jam. Copy it somewhere safe before doing anything else.
• Memory in the GB. A leak. Restart, update. One Ventura user on MacRumors kept hitting it: "I have to force-quit bird to fix the memory issue, but the bird memory issue keeps happening."
• Finder beachballs in iCloud Drive folders. fileproviderd is waiting on bird. Same fix: find the stuck item.
• Battery and heat. A day at 100 percent on a laptop brings kernel_task throttling and an empty battery by lunch. Reason enough to find the file rather than wait.

Safe to Quit tracks each process's CPU and network over hours, so bird busy all night with nothing transferring shows up as exactly that, rather than a mystery you discover when the fan is already on.