cloudd on Mac: what it is, why it is high, what to do

What cloudd does

iCloud is really two systems. One syncs files: that is iCloud Drive, handled by bird and fileproviderd. The other syncs records: a note, a reminder, a bookmark, a password, a game's save state, a third-party app's database rows. That second system is called CloudKit, and cloudd is the daemon that runs it on your Mac. OSXDaily's summary is the plain version: "The cloudd process is responsible for iCloud syncing and management" for the data apps keep in iCloud.

Apps do not talk to Apple's servers directly. They hand changes to cloudd, which batches them, encrypts them, uploads them, and pulls down whatever changed on your iPhone or iPad. When you type a note on your phone and it appears on the Mac a few seconds later, that was cloudd on both ends.

Because dozens of apps use it, it has no single owner, which is why it shows up in Activity Monitor as a process with no app attached. When it is busy, the question is always which app handed it the work, and whether that work is finishing.

Why cloudd is using CPU right now

1. You just signed in to iCloud. Every app with iCloud data pulls its full history: years of notes, thousands of bookmarks, Messages in iCloud. The first sync on a new Mac is the biggest job cloudd ever does, and it can take an hour of on-and-off CPU.
2. A macOS update. Schema changes mean records get re-synced or re-indexed. Expect a busy half hour after the update finishes.
3. An app changed a lot at once. Importing a thousand bookmarks, pasting a huge note, a third-party app migrating its database. One burst, then quiet.
4. A record it cannot sync. A note larger than the limit, a bookmark folder with a damaged entry, a third-party record the server rejects. cloudd retries, fails, retries. This is the case behind the long-running complaints. One Ask Different poster on Ventura found "cloudd is using over 100% CPU constantly" and the only relief was a reboot or signing out of iCloud.
5. Safari bookmark sync in a loop. A specific and common version of the above: SafariBookmarksSyncAgent and cloudd both high, often after a bookmarks import or a restore. Hacker News commenters have been grumbling about it for years: "SafaribookmarkSync, Cloudd, along with Content Cache has been problematic for years."
6. A second user account on the same Mac. Each account runs its own cloudd. An Apple Community thread traced a 100 to 200 percent spike to a family member's account syncing in the background after they logged in.

What it is not: malware. cloudd is part of macOS on the sealed system volume. Any page offering to delete it is selling a cleaner.

What normal looks like, and what is not

The shape of a healthy sync and the shape of a stuck one look very different over time:

The healthy pattern tails off: big, then smaller, then nothing. The stuck pattern is flat: the same percentage all day, no tail. The quickest check is Activity Monitor's Network tab: a healthy sync moves data (KB to MB per second in the early minutes); a stuck one burns CPU with almost no traffic.

A second check is in the apps themselves. Open Notes and look for a "Updating" line at the bottom of the sidebar; open Reminders for the same; in Safari, check that a bookmark you just added on your phone shows up. If everything is current but cloudd is still hot, it is looping on something you cannot see from the app.

Is it safe to quit cloudd?

Yes, in the sense that nothing is lost. CloudKit keeps a record of what has synced, cloudd restarts within seconds and carries on. The 2014 MacRumors thread on this found that quitting it alone changed nothing, which is the honest summary: it is harmless and it does not fix the record that is stuck.

What is not safe: deleting folders under ~/Library/Application Support/CloudDocs or anything named CloudKit in Library. Those are the local databases. Removing them can lose notes or reminders that had not uploaded. The decision tree covers the general rule:

So the lever is the app, not the daemon: find which app's sync is stuck and deal with that.

What to do, in order

1. Give it 15 minutes

   If you signed in, updated, or imported something today, that is a legitimate sync. Leave the Mac on power and awake. Check again later; most cases are over by then.

2. Look for the app that is also busy

   Activity Monitor, CPU tab, sort by % CPU. SafariBookmarksSyncAgent, Notes, Reminders, Messages, or a third-party app sitting near cloudd is the one feeding it. Quit that app and watch cloudd for a minute. If it drops, you found it.

3. Check the stuck app's data

   For Notes: look for a note that will not open or is enormous (hundreds of images). For Safari: look for a bookmarks folder that was imported or a very large reading list. Delete or split the problem item. Sync usually completes within minutes.

4. Restart

   Clears a daemon stuck mid-retry. Reliable for the version-specific loops, which is why the Ask Different poster ended up there.

5. Update macOS

   CloudKit loops have been fixed in point releases repeatedly. System Settings, General, Software Update.

6. Turn that one app's iCloud sync off and on

   System Settings, your name, iCloud, then toggle just the app that is looping (Safari, Notes, Reminders) off, wait a minute, and back on. Keep data on the Mac when asked. This re-syncs that app only, not everything.

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

   System Settings, your name, Sign Out, keep a copy of your data, restart, sign in. Everything re-syncs, which takes an hour or more and a lot of bandwidth. Last because it is the heaviest, not because it is risky.

When to worry

cloudd is not a security problem and does not delete your data. The things that deserve attention:

• Notes or reminders missing on another device after a day. That app's sync is the stuck one. Fix it before signing out of anything, or the unsynced item may be lost.
• Days at 100 percent after a restart. Then it is a specific record. Toggle that app's iCloud sync.
• Battery and heat. A laptop with cloudd at 100 percent all day gets hot, pulls in kernel_task throttling, and loses hours of battery. Reason enough to find the app rather than live with it.
• Another account on this Mac. If a family member's account is signed in in the background, their cloudd is syncing their data. Log them out fully when they are done.

Safe to Quit watches each process over hours and shows which app was busy in the minutes before cloudd climbed, which is the question Activity Monitor's snapshot cannot answer.