# The bird process, iCloud Drive's engine on your Mac

> bird is the iCloud Drive daemon hiding behind a codename. What it does, where com.apple.bird lives, and whether you can quit it.

Source: https://www.ribbonmac.com/guides/bird-process-mac · Updated 2026-11-15

A process called bird is not something most people set out to find. It turns up the way most Activity Monitor questions do. The laptop is warm, the list is sorted by CPU, and there it is near the top with a name that sounds like a placeholder.

It is neither a placeholder nor anything malicious. bird is the iCloud Drive daemon, the piece of macOS that keeps your synced files up to date in both directions, and it has carried that name for a long time. Everything that uploads, downloads, and decides whether a file is on your disk or only in iCloud runs behind it.

What follows comes from Apple's iCloud documentation, from the files macOS ships that describe the process, and from read-only checks on the Mac this was written on. Nothing was uninstalled, no cache was cleared, and no iCloud setting was touched. The machine is a 14-inch MacBook Pro with an M1 Pro running macOS 27.0.1.

## What the bird process actually is

One command gives you the whole identity of the thing:

```text
$ ps -Awwo pid,ppid,user,%cpu,rss,etime,args | grep "[/]bird"
77511     1 chethankumar  0.0   7264 04-20:54:35 /System/Library/PrivateFrameworks/iCloudDriveCore.framework/Versions/A/Support/bird
```

Four details in that line are worth reading properly. The path sits inside a PrivateFramework, which is Apple's own code rather than something an app dropped on you. The parent process is 1, which is launchd, the part of the system that starts and supervises other processes. The user is the person logged in, so bird is not running as root. And the elapsed time is over four days, meaning this copy started at the last login and has been there since.

macOS also ships a file that describes the job in plain terms. Read it with plutil and the parts that matter are three lines long:

```text
$ plutil -p /System/Library/LaunchAgents/com.apple.bird.plist
  "Label" => "com.apple.bird"
  "MachServices" => { "com.apple.bird" => true, "com.apple.bird.cache-delete" => true,
                      "com.apple.bird.push" => true, "com.apple.bird.token" => true }
  "ProgramArguments" => [ 0 => "/System/Library/PrivateFrameworks/iCloudDriveCore.framework/Versions/A/Support/bird" ]
```

A LaunchAgent with a label of com.apple.bird is launchd's own bookkeeping for this process, and it settles the question people ask most often about it, which comes up further down this page.

The clearest statement of what bird does is in the command line tool that talks to it. Run `man brctl` and the first line of the description reads: Manage the CloudDocs daemon. CloudDocs is the older internal name for iCloud Drive, and the framework with that name still ships next to the one bird lives in.

## The name is a codename, and that is the whole story

Nothing in Apple's user documentation explains why it is called bird, and that is a count rather than a suspicion. The index of the macOS 27 Mac User Guide, read while writing this page, has no entry for a process called bird, and the iCloud pages there describe the feature without ever naming the machinery behind it.

Apple uses short internal names across the whole system, and they surface in Activity Monitor because that is where processes are listed. This one predates the name iCloud Drive entirely.

So when a search for a strange process lands here, the honest answer is that the name carries no information about what it does, and that finding it running is normal rather than notable.

## There are two parts to iCloud Drive, and bird is one of them

On a Mac running macOS 27 the sync engine is split in two. bird holds the connection to iCloud, tracks changes in both directions, and moves the bytes, though the transfers that outlive a closed window are handed to the system's background download service, [which the nsurlsessiond page traces](https://www.ribbonmac.com/guides/nsurlsessiond-mac). Next to it runs a File Provider extension:

```text
$ ps -Awwo pid,user,%cpu,etime,args | grep "[C]loudDocs.iCloudDriveFileProvider"
1673 chethankumar 0.0 24-23:08:25 /System/Library/PrivateFrameworks/CloudDocs.framework/PlugIns/com.apple.CloudDocs.iCloudDriveFileProvider.appex/Contents/MacOS/com.apple.CloudDocs.iCloudDriveFileProvider
```

That second process is what the Finder, the open and save dialogs, and any app using the file system actually talk to. When you double-click a file that exists only in iCloud, the extension asks bird for it, bird fetches it, and the file appears. The daemon hosting that extension is a separate process with its own launch job, database and work queue, [which the fileproviderd page counts across two providers and two domains](https://www.ribbonmac.com/guides/fileproviderd-mac). That is why the two are almost always in the list together, and why a document can sit there for a second before opening on a Mac with storage optimisation switched on.

Both started at login on this Mac and both are doing nothing at all right now. That is the resting state, and it is the state you should expect to see most of the time.

Files are only half of what happens under the iCloud Drive banner, and the other half belongs to a different process. The record layer, which is how macOS tracks what exists where and what changed since last time, is CloudKit's work rather than bird's, [which the cloudd page counts across eighty containers on one Mac](https://www.ribbonmac.com/guides/cloudd-mac).

And the push wake is only one of the two directions something can arrive from. When the other device is on the same network as your Mac rather than at the other end of Apple's servers, the finding and the pairing are handled by rapportd, [which its own page reads out of the daemon's launch jobs, its firewall-provoking listening socket and its pairing protocol](https://www.ribbonmac.com/guides/rapportd-mac).

## Reading bird's numbers

Activity Monitor gives you a percentage and a memory figure, and the useful thing to know about the memory number is that it moves while you watch it. Four reads of the same process, a few minutes apart on an otherwise idle machine:

```text
$ ps -o rss -p 77511        # kilobytes
  7264
 10128
 10592
 10656
```

That is the daemon working through small jobs and caching metadata, not a leak. The figure climbs as it works, then settles once the queue is empty.

Memory is the wrong number to fixate on here. Apple publishes no target, no ceiling and no guidance for how much memory bird should use, so any thread quoting a specific limit is describing one person's Mac rather than Apple's advice. The trend over days is meaningful. The number over minutes is not.

CPU is the more readable signal, and it only looks alarming while there is real work. This copy sits at 0.0 per cent at rest and stays there. During an upload the percentage rises with the size of the queue and falls back as it drains. For what the columns themselves mean, [the running slow page takes the three numbers in order](https://www.ribbonmac.com/guides/why-is-my-mac-running-slow).

## Why bird gets busy

Uploading is the expensive direction. A file going up is read from the disk, hashed, encrypted and sent in pieces, and every one of those steps counts against the CPU column. One large video is a solid block of work. A folder of a few thousand small files is worse, because the per-file overhead and the metadata updates dominate.

Two situations produce most of the complaints. The first is the day Desktop and Documents Folders gets switched on, because Apple's description of that setting is that your Desktop and Documents folders are moved into iCloud Drive. It is not a link and not a copy: everything in both folders becomes something bird has to upload, which on a full desktop is hours of work on a home connection.

The second is a Mac that has just been set up, restored, or reconnected after a long time offline, syncing an account with a lot of files in it. There is no shortcut for either case. bird moving data is the feature working.

Then there are the wakes nobody triggers. The same plist that starts the daemon books recurring maintenance work with launchd, and reading it shows three of them: an analytics report once a day, and app telemetry plus a configuration update every two days. Each one carries the conditions RequiresExternalPower and RequiresUserInactivity, which is the plist declaring that they only run on mains power and while the Mac is not being used. That is why a plugged-in Mac left overnight can show a brief burst of activity from a process that was quiet all evening, and why it is not a symptom of anything.

One more source of activity is easy to overlook. The plist registers a service called com.apple.bird.push, which means the iCloud servers can wake bird when something changes. Editing a document on your iPhone can start work on the Mac a moment later, with nothing at all happening on the Mac itself.

## Where its data lives on your disk

Three locations come up whenever bird is the subject, and they behave differently.

iCloud Drive itself lives at `~/Library/Mobile Documents/com~apple~CloudDocs`, and the trick worth knowing is that the files there can take up no space at all. On this Mac the folder holds 69 files across five folders, and asking how much room they use returns zero:

```text
$ du -sh ~/Library/Mobile\ Documents/com~apple~CloudDocs/
  0B
$ stat -f "blocks=%b bytes=%z" ~/Library/Mobile\ Documents/com~apple~CloudDocs/Wallpaper\ /PNG\ image.png
blocks=0 bytes=2921820
```

Zero blocks allocated for a file whose full size is nearly three megabytes. The file is not missing and it is not corrupt. It is a placeholder: the name, the size and the dates are on your Mac, the contents are in iCloud, and bird fetches them the moment something opens it. Apple's description of the setting behind that behaviour is short, and it explains the whole arrangement. If space is not needed, the full contents of iCloud Drive remain on your Mac. When space is needed, older documents get stored in iCloud instead.

This is why two people with identical iCloud Drive folders can see wildly different storage figures, and why a Mac can look empty in Disk Utility while the Finder shows a folder full of files. It is the same arithmetic that makes [a storage bar disagree with the Finder](https://www.ribbonmac.com/guides/mac-storage-full-but-nothing-on-it).

The cache lives at `~/Library/Caches/com.apple.bird`. On this Mac it holds a Cache.db of about 49 KB with its two side files, a folder called fsCachedData with one entry, and a session folder. All of it came to 144 KB. The plist above is where the cache is emptied from, through that com.apple.bird.cache-delete service, which is what a search for com.apple.bird cache delete is really after.

The working folder is `~/Library/Application Support/CloudDocs`, and it is the one that will not open. On this Mac, `ls` on it returns Operation not permitted. That is macOS protecting it rather than a fault: it holds the sync database and per app state, and the Terminal app needs Full Disk Access before it can read inside. The same protection is what hides parts of your Library folder from the Finder, and [the storage page goes through that in detail](https://www.ribbonmac.com/guides/mac-storage-full-but-nothing-on-it).

## Can you quit it, delete it, or stop it?

You can quit it. You cannot stop it, and you should not try.

Because bird is a LaunchAgent, launchd starts it at login and starts it again the instant it exits. Force quitting it in Activity Monitor does end the process, and syncing stops with it, but a new copy appears within seconds with a new process ID. Nothing is freed, no disk space is reclaimed, and any upload that was in flight simply resumes when the new copy picks up the queue. If you have quit bird before and watched it come back, that was the launchd job doing exactly what it says on the file.

Removing it is not available either. The binary sits inside a system framework protected by System Integrity Protection, so there is no app to drag to the Trash, no login item to untick, and no supported switch that disables bird while leaving iCloud Drive working. Turning iCloud Drive off is the only way to stop it, and that is a decision about syncing rather than a tweak to a process.

One behaviour is worth knowing because it looks like a malfunction. The same plist declares EnablePressuredExit, which tells the system that this process may be ended under memory pressure and started again the next time something needs it. So bird disappearing from the list on a busy Mac for a minute, then returning, is the arrangement working as designed rather than something crashing.

## When iCloud Drive looks stuck

Start with space, because Apple's own account of that case is the useful one: if you cannot move or save a document to iCloud Drive, your iCloud storage space may be full. The document stays on your Mac, and is uploaded to iCloud Drive when space becomes available. A stalled upload is therefore often an account problem rather than a process problem, and the place to look is System Settings, your name, iCloud, then Manage, where the bar at the top breaks the total down by category.

For the live picture, Apple's tip is the quickest route: hold the pointer over iCloud Drive in the Finder sidebar, then click the status or information icon. That tells you whether it is syncing, waiting or finished, without opening anything else.

If the Mac was only just given Desktop and Documents Folders, expect a long first run rather than a fault. And if a second cloud service is pointed at the same folders, Apple has a sentence for that too: syncing by other third party apps or cloud services can interfere with or stop the updating performed by iCloud Drive. Two sync engines watching one folder is a race, and the loser is whichever one you were waiting for.

Past that, the standard re-seat is the Drive section of iCloud settings, where Sync this Mac can be turned off and on again. Read the dialog before agreeing to anything, because macOS asks what should happen to the local copies when that switch goes off. Signing out of iCloud and back in is the heavier version of the same idea, and it asks the same question about your data first.

What no step fixes is a large first upload on a slow connection. That is not stuck, it is slow, and it will finish.

## brctl: watching it instead of guessing

The manual page for brctl opens with Manage the CloudDocs daemon, and it is the closest thing to a window into the sync engine that ships with macOS. It is a diagnostic tool, and everything useful in it for this situation only reads:

```text
$ brctl status | head -4
60 containers matching '*'
<5{8}3.n{1}t.w{6}p.W{6}p[25] background {client:needs-sync|blocked-app-uninstalled server:idle sync:idle last-sync:never ...}>
>>> SYNC DISABLED (app not installed)
<5{8}G.c{1}m.a{3}e.dt.X{3}e[59] background {client:idle server:full-sync|sync:has-synced-down last-sync:2026-11-09 15:14:05.086, caught-up ...}>
```

Read it as a list of containers, one per app or service that has a slice of your iCloud, each with a short status string. The container names are deliberately obfuscated, with runs of letters shortened to a count in braces, which is why the output is good for spotting something that has not synced since a date and useless for telling what it is.

The words inside the braces are the readable part:

| What you see | What it means |
| --- | --- |
| client:idle | Nothing on this Mac is waiting to go up |
| client:needs-sync | There is something it has not pushed yet |
| sync:idle | Not in the middle of a transfer |
| sync:has-synced-down | It has pulled changes at least once |
| last-sync: a timestamp | When it last completed a round trip |
| SYNC DISABLED (app not installed) | Left over from an app you removed, and harmless |

Two other commands answer questions that come up in the same search. `brctl quota` prints the remaining storage in bytes followed by the words in personal account, which is the account figure rather than the free space on your disk and not the size of your iCloud Drive folder, since iCloud storage is shared with backups, photos and mail. On this Mac it printed 25912658096 bytes, a little over 24 GB, while the Finder folder reported zero. And `brctl monitor` shows activity as it happens, with `-t` available to bound how many seconds it runs and `-g` for the global view.

One honest note about all of this. `brctl accounts` is meant to list the accounts it knows about, and on the Mac used for this page it printed nothing at all, even with its wait flag. These are internal tools with no promise of polish, and a blank answer is part of using them. `brctl diagnose` also writes a bundle of logs to disk when it runs, so it belongs in the same category as any diagnostic tool: useful, but not free of consequences.

## What this page cannot tell you

Apple publishes no CPU figure, memory figure or duration that counts as normal for bird, so there is no threshold to measure against. That is a gap in the documentation rather than something being hidden.

No Apple source explains the name. It is a codename, and it will keep looking strange until you know what it stands for.

And bird is not a cleanup target. Emptying its cache reclaims kilobytes and costs a rebuild, so a Mac cleaner promising to deal with bird is selling the removal of something that comes straight back.

## Where window managers fit

None of this is a window problem, and no amount of syncing makes a desktop easier to work on. What usually sends people into Activity Monitor in the first place is a Mac that feels slow to use, and a large part of that feeling is windows: things shrunk into the Dock, a desktop with nineteen overlapping windows on it, and Control-Up used as a search expedition.

Ribbon takes the other approach. Windows stay at full size on a single scrolling strip instead of stacking, so the window you want is one swipe away and nothing disappears behind anything else. It is $15, once, for up to 3 Macs, with a full refund within 10 days, and it runs on macOS 14 Sonoma and later on Apple silicon and Intel Macs. You can [drive the strip in your browser](https://www.ribbonmac.com/#drive) before installing anything.

## The short version

bird is iCloud Drive. It is Apple's own daemon, it lives inside a system framework, launchd starts it at login, and the command line tool that talks to it calls itself the manager of the CloudDocs daemon.

It shows up as a real process with real numbers, and both move while it works. Its memory drifted between 7 and 11 MB across a few idle minutes on this Mac, and Apple publishes no figure that says what is normal, so watch the trend rather than the reading.

Its own settings file explains most of the strange timing: daily and two-day maintenance jobs that only run on power and while the Mac is idle, and a push service that lets the servers wake it when something changes on another device.

You can quit it and it comes straight back, which is the design. You cannot remove it, and its cache is worth nothing to delete. What actually helps when syncing stalls is space in your iCloud account, the status icon in the Finder sidebar, and patience for a first upload of a full desktop. And for a look under the bonnet, `brctl status` will tell you which containers are idle and which have never synced, in a syntax that only Apple could love.

## FAQ

### What is the bird process on my Mac?

It is iCloud Drive. bird is the daemon that keeps your synced files up to date, and on this Mac its full path is /System/Library/PrivateFrameworks/iCloudDriveCore.framework/Versions/A/Support/bird. The Apple command line tool that talks to it says so in its own description, which reads Manage the CloudDocs daemon. CloudDocs was the internal name for iCloud Drive before it had that name, which is why a process called bird exists at all. Nothing installed it, nothing is wrong, and it runs as you rather than as root.

### Why is bird using so much CPU or memory?

Because it is uploading or downloading, and both cost work. A file going up is read, hashed, encrypted and sent in pieces, so a folder of thousands of small files keeps it busier for longer than one large video. Apple publishes no target figure for its memory use, so any specific number you read online belongs to someone else's Mac. What is worth watching is the trend: this copy of the daemon drifted between 7 MB and 11 MB over a few idle minutes, and that is metadata being cached rather than a leak.

### Is it safe to quit bird, or delete the com.apple.bird cache?

Quitting it does nothing useful and it will not stay quit. bird is a LaunchAgent, listed in /System/Library/LaunchAgents/com.apple.bird.plist, so launchd starts it at login and starts it again the moment it exits. Force quitting it stops syncing for a few seconds, frees nothing, and lets whatever was uploading carry on afterwards. Deleting ~/Library/Caches/com.apple.bird is harmless but pointless: the daemon rebuilds it, and the whole folder was 144 KB on this Mac. The binary itself sits inside a system framework protected by System Integrity Protection, so removing it is not on the table either.

### Why is iCloud Drive stuck uploading, or how do I check if it is syncing?

The first thing to rule out is space, because Apple's own wording for that case is that the document stays on your Mac and is uploaded to iCloud Drive when space becomes available. So a stalled upload can be a full iCloud account rather than a stuck process, and the place to check is System Settings, your name, iCloud, then Manage. For the live status, hover over iCloud Drive in the Finder sidebar and click the status or information icon, which is the tip Apple gives for exactly this question. And if a Mac has just been given Desktop and Documents Folders for the first time, that first upload is the whole contents of both folders, which takes as long as it takes.

### Does the bird process mean my Mac has a virus?

No. It is Apple's own code, signed and sealed inside a system framework, and it is present on every Mac signed in to iCloud Drive. The name is an internal codename rather than a description, which is part of why it looks suspicious: Apple's macOS 27 user guide index contains no entry for a process called bird at all, so there is no documentation to find when you search for it. If you want the reassurance properly rather than by reputation, check the path in Activity Monitor: anything running out of /System/Library/PrivateFrameworks is part of the system.
