HeartbeatHocusFocusFilesMacHyperTile
Guide

cloudd, the process that syncs your data with iCloud

cloudd is the daemon behind CloudKit, the layer that syncs iCloud Drive records, Messages, Safari tabs and more. What it is and what to do about it.

By Chethan Kumar S N · Updated

Two different searches bring people to this page.

One starts in Activity Monitor or a battery report. A process called cloudd is somewhere in the list, the CPU or network column is not at zero, and nothing you installed is called cloudd. The other starts as a complaint with no process name attached: this Mac is sending data while it sits on a desk doing nothing, or it is warm when it should be asleep, and none of the apps that are obviously running explains either.

Both come down to the same daemon, and the answer is duller than the search suggests. cloudd is the part of macOS that talks to CloudKit, which is the service that keeps your data in step across your devices, and it is neither a file you downloaded nor a leak.

Everything below comes from reading the process, its man page, the two property lists that launch it, its own log, and the files it keeps open, on an M1 Pro MacBook Pro running macOS 27.0.1, build 26A434, with 25 days of uptime. Nothing was quit, nothing was installed, no iCloud setting was changed, and the folder it keeps its databases in was described rather than opened.

What the process is, in one command

$ ps -Awwo pid,ppid,user,%cpu,rss,time,etime,comm | grep "[c]loudd"
70665     1 chethankumar       0.0  14064   2:25.03 02-09:39:15 /System/Library/PrivateFrameworks/CloudKitDaemon.framework/Support/cloudd
90109     1 root               0.0   4304   0:00.26       52:51 /System/Library/PrivateFrameworks/CloudKitDaemon.framework/Support/cloudd

Two lines, and the second one is the surprise. Parent process 1 on both, which is launchd, so neither was started by an app or by you. Both run the same binary. One belongs to your account and one runs as root, and the next section is about why.

The first line is the one that matters for a search: 14 MB resident, and 2 minutes 25 seconds of processor time across 2 days, 9 hours and 39 minutes of running. That works out at about 0.07 percent of one core averaged over the entire life of the process, and 0.0 percent at the moment of reading.

The binary itself is 480,672 bytes dated 24 September 2026, a universal one carrying three slices for x86_64, arm64e and arm64e.x1. It is signed by Apple under the identifier com.apple.cloudd, authority macOS Software Signing, Platform identifier 26, and it holds 55 entitlements. Among them are keychain access, permission to impersonate a URL session, and a set of names with no public documentation at all, including com.apple.cdp.statemachine, com.apple.private.octagon and com.apple.private.octagon.walrus. A daemon that only moved records would not need 55 entitlements. This one also handles the keychain and the encryption behind iCloud, which is the same daemon in a different hat.

Then there is the man page, and it is the shortest one I have found on this machine.

CLOUDD(8)                System Manager's Manual                CLOUDD(8)

NAME
     cloudd - CloudKit

DESCRIPTION
     cloudd is the system daemon backing the CloudKit feature.

     There are no configuration options to cloudd, and users should not run
     cloudd manually.

That is 305 bytes in total, dated 14/12/15, and it is the whole official description: there are no options, and running it by hand is not something you should do. Every other number on this page comes from the files rather than the manual.

What CloudKit is, in one sentence: it is the sync service Apple ships for records, and cloudd is the process on your Mac that is allowed to use it. Records rather than files is the important half of that. Notes, Messages, Safari tabs, Screen Time totals, Bluetooth pairings and Shortcuts flows are all records in CloudKit containers, and iCloud Drive has a record layer too, which is why so many features you would never group together show up in the log of one process.

Two copies run at once, and the labels do not tell them apart

$ ls /System/Library/LaunchAgents/ /System/Library/LaunchDaemons/ | grep -i cloudd
com.apple.cloudd.plist
com.apple.cloudd.plist

Two property lists, the same label inside each, and the difference is where they live. The one in LaunchAgents runs in your login session. The one in LaunchDaemons runs for the system, independently of any login, and its program arguments add a single flag:

$ plutil -p /System/Library/LaunchDaemons/com.apple.cloudd.plist
  "Label" => "com.apple.cloudd"
  "POSIXSpawnType" => "Adaptive"
  "EnablePressuredExit" => true
  "ProgramArguments" => [
    0 => "/System/Library/PrivateFrameworks/CloudKitDaemon.framework/Support/cloudd"
    1 => "--system"
  ]

The rest of the split is in the doors each copy opens, which macOS calls Mach services:

User copy (LaunchAgents)System copy (LaunchDaemons)
com.apple.clouddcom.apple.cloudd.system
com.apple.cloudasset.clouddcom.apple.cloudasset.cloudd.system
com.apple.cloudd.cache-deletecom.apple.cloudd.system.cache-delete

The user copy serves your data. The system copy serves the parts of iCloud that have to exist before anyone logs in. Apple does not document the split in either file, and both describe themselves with the same words, but the naming rule holds without exception here: the system copy is the same three jobs with .system appended. If you are searching for this process because of something you did in an app, it is the user copy you want, which on this Mac is the paged 14 MB one rather than the 4 MB root one.

launchctl gives the behaviour, and three lines of it carry the whole explanation:

$ launchctl print gui/501/com.apple.cloudd
        state = running
        runs = 2
        pid = 70665
        immediate reason = ipc (mach)
        minimum runtime = 10
        exit timeout = 5
        last exit reason = JETSAM_REASON_MEMORY_IDLE_EXIT
        jetsam memory limit (active, soft) = 100 MB
        jetsam thread limit = 32

immediate reason = ipc (mach) means what woke it was another process knocking on one of those Mach services, not a clock. jetsam memory limit (active, soft) = 100 MB is the budget macOS gives it, and a 14 MB process is not close to it. And last exit reason = JETSAM_REASON_MEMORY_IDLE_EXIT is the answer to the most common confusion about cloudd, which is a process that keeps vanishing from Activity Monitor and coming back.

That exit reason means macOS deliberately reclaimed it, not that it crashed. Both property lists set EnablePressuredExit to true, which is the door being held open for exactly that outcome: a daemon that only has work when something asks it to do something should not sit in memory when nothing is asking. Two smaller settings in its environment point the same way, OSLogRateLimit at 64 and MallocSpaceEfficient at 1, both of which read as instructions to a service that is expected to run a little and then go away.

So the honest framing is the opposite of the one the search implies. cloudd appearing in Activity Monitor and disappearing again is not a symptom. cloudd staying there and working for hours is what a sync looks like.

The five wake-up events inside its job

A daemon with no KeepAlive needs something to start it. Its job carries five event triggers, and they are a good picture of what this thing actually does, because only two of the five are scheduled work.

TriggerWhat wakes itConditions from the property list
com.apple.cloudkit.operationInfoCacheEvictiona background task due every 24 hoursminimum gap 69120 s (19.2 h), maintenance priority, needs protection class C
com.apple.cloudkit.tokenregistrationa background task due every 691200 s (8 days)minimum gap 552960 s (6.4 days), needs network, maintenance priority, class C
com.apple.cloudkit.tcc-event-subscribera permissions changesubscribes to the kTCCServiceLiverpool stream, monitored by com.apple.tccd
com.apple.cdp.manatee-availabilityan availability changea distnoted notification, monitored by the user event agent
com.apple.cdp.manatee-availability-changedthe same, after it landsa distnoted notification

Two things jump out. The first is that both scheduled tasks are labelled maintenance priority, which in macOS means they yield to whatever you are doing and are normally run when the machine is otherwise quiet. The eviction job does what its name says, trimming the operation cache; the token registration job runs roughly once a week and is the one that needs the network. A daemon whose own timetable is “once a week, when nothing else is happening” is not the process behind a mystery slowdown.

The second is those two identically named triggers containing the word manatee. Both fire on a notification, not a schedule, and the entitlement list contains matching private names, com.apple.cdp.manatee-availability and com.apple.private.octagon.walrus. Apple does not document what they mean anywhere I could find, so the honest description is limited to the shape: they are availability notifications for the encrypted keychain side of iCloud, which on this Mac is also what most of the rest of the entitlement list is for. If you are the kind of person who turned on Advanced Data Protection, these two are part of what changed.

There are also four event channels and three endpoints declared for the user copy, which is the plumbing: one endpoint per Mach service, and channels for the background task stream, the TCC stream, and two notification streams. None of it is configurable, which is what the man page said.

Where it keeps its books

This is the part you cannot get from a description, and the command that shows it is the one that lists open files.

$ lsof -p 70665 | grep CloudKit
cloudd  70665  ...  3u  REG  1,16   835584  .../Library/Caches/CloudKit/CloudKitMetadata
cloudd  70665  ...  4u  REG  1,16  2125952  .../Library/Caches/CloudKit/CloudKitMetadata-wal
cloudd  70665  ...  6u  REG  1,16     4096  .../Library/Caches/CloudKit/CloudKitOperationInfo
cloudd  70665  ...  7u  REG  1,16  1153632  .../Library/Caches/CloudKit/CloudKitOperationInfo-wal

Two databases, each with a working copy and a write-ahead log, in ~/Library/Caches/CloudKit. Two details are worth having.

The first is how you get the sizes at all. ls on that folder returns Operation not permitted, because macOS protects it, and the same is true of several of the caches that belong to Apple’s own processes. stat against a file path you already know works fine, which is how the table below was measured:

FileSizeLast written
CloudKitMetadata835,584 bytes14 November 2026, 20:20
CloudKitMetadata-wal2,125,952 bytes14 November 2026, 21:19
CloudKitOperationInfo4,096 bytes19 September 2026, 20:46
CloudKitOperationInfo-wal1,153,632 bytes12 November 2026, 12:28

The second is that in both pairs the log is bigger than the database it belongs to, which looks alarming if you read it as a leak and is ordinary SQLite behaviour. A write-ahead log collects changes as they arrive and only folds back into the main file at a checkpoint, so a database of 835 KB carrying a 2 MB log means writes are arriving and being batched rather than that something is quietly growing without limit. The -wal timestamps are the useful number: 21:19 tonight for the metadata, three days earlier for the operation cache. That is a process that has been asked to write twice in a week and once in the last hour, which matches everything else measured here.

These four files are only cloudd’s own bookkeeping about requests. The data itself stays with the container that owns it, which is why clearing this folder does not remove anything from iCloud and only costs you the care taken over requests in flight.

What it does all day, counted

A process that is quiet by design is hard to describe with a single CPU figure, so the log is the better instrument. In the 24 hours before this was written, one process wrote 53,624 lines of log.

$ log show --predicate 'process == "cloudd"' --start "2026-11-13 22:00:00" | wc -l
   53624

And the shape of those lines over the day is the point, because it is nothing like a steady load:

Hour (14 Nov)LinesHour (14 Nov)Lines
0078123,632
024013471
0440144,765
0636151,810
0737173,762
08341193,925
092,4832013,808
117,799212,337

Overnight it is between 36 and 78 lines an hour, which for a process talking to a network service is close to silence. Then it spikes to thousands of lines in the hours this Mac was actually in use. A daemon doing scheduled scanning would look the other way round.

Inside those lines, the vocabulary is specific. Twenty different log subsystems feed it, and the biggest three in a three hour sample were com.apple.cloudkit at 4,537 lines, com.apple.xpc at 3,231 and com.apple.mmcs at 986. MMCS is the part that stores and fetches the actual file chunks behind a record, and its lines are as literal as they look:

[com.apple.mmcs:default] mmcs_engine verifySentChunks: true
[com.apple.mmcs:default] mmcs job queue halted
[com.apple.chunkinglibrary:default] ChunkRegistry ver=10/10 isNew=N
[com.apple.cloudkit:Request] ... Requires zone id gates, grabbing them from gatekeeper, expectDelay false accessMode shared

The last line is the mechanism in one sentence. CloudKit is organised into zones, writes need permission from a zone’s gates, and those gates are fetched from a component the log calls the gatekeeper. When you read that a daemon is “syncing”, this is the queue it stands in.

The last number to have is who it serves. Counting the container identifiers that appear in 24 hours of log gives 82 distinct containers on one Mac, and the top of that list is a fair map of what iCloud does:

ContainerMentions in 24 hBelongs to
com.apple.clouddocs653iCloud Drive records
com.apple.security.keychain39iCloud Keychain
com.apple.bluetooth.services27Bluetooth pairings
com.apple.ScreenTimeSettings25Screen Time
com.apple.iCloud.CommCenter22Messages over iCloud
com.apple.callhistory.cloud-storage222Call history
com.apple.shortcuts21Shortcuts
com.apple.SafetyMonitor.SafetyCache21Check In

Which is why the search results for this process are so contradictory. One person’s cloudd is syncing Safari tabs, another’s is moving Screen Time totals, a third is watching keys land in the keychain, and a fourth is checking whether a Note changed. All four are the same process doing the same job for different owners, and none of the four is doing it on a schedule.

Worth adding because it is the kind of number that surprises people: in a six hour window this daemon asked the permissions system for access 961 times, once per container per request. Cloudd does not have a blanket right to your data. Every container has to ask through TCC, and the log says so 961 times.

The lines that look alarming and are not

Two things in this log read worse than they are, and both are worth recognising so you do not chase them.

The first comes from the root copy rather than yours:

cloudd[90109] [com.apple.accounts:core] "Remote account store returned fatal error: ... com.apple.accountsd.accountmanager was invalidated: ... No such process."
cloudd[90109] [com.apple.authkit:core] Could not fetch accounts of type (null) due to Error Domain=com.apple.accounts Code=10002
cloudd[90109] [com.apple.cdp:core] No primary account found

The words fatal error are doing a lot of work there. This is the system copy, which by definition is not signed into a personal iCloud account, asking the account store for an account and being told there is none, on a loop, in bursts of a few dozen lines at each start. It is a system daemon discovering it has no user, which is the correct state of affairs. The account store it keeps knocking on belongs to accountsd, and the accountsd page covers the daemon that owns it, its plugin registry and the keychain prompt it is famous for.

The second is the push connection flapping:

[com.apple.apsd:connection] Delivering connectionStatusChange from apsd: NO
[com.apple.apsd:connection] Delivering connectionStatusChange from apsd: YES

That is the Apple push channel for iCloud dropping and reconnecting, which it does in bursts, 710 times in a six hour window on this Mac. Push is how your Mac learns that something changed elsewhere, so a reconnect is a healthy thing to see. The one genuinely interesting error line in the same window was a single cache_purge: MMCS setup failed, one occurrence against 986 MMCS lines, which is the asset store being torn down while a request was in flight, and it is the retry logic doing its job rather than a fault you can act on.

One caveat that applies to everything quoted from this log: paths and identifiers arrive as private markers or hashed tokens, so the log is excellent at counting and useless at naming. Every number above is a count of something, and none of them would let me tell you what you changed on your iPhone at 20:00 last night.

What Apple’s own documentation says

The man page is quoted above and it is two sentences long, which is itself the finding: for a process that appears in every Activity Monitor tutorial, Apple publishes almost nothing about it.

Apple documents the service underneath at more length, from the developer side, and its own words about what CloudKit is are worth having exactly: apps store their data in iCloud and keep everything up to date across devices and on the web, with efficient syncing, monitoring and management built in. That is the feature this daemon implements. Apple’s page describes CloudKit as a way to store private data securely in users’ iCloud accounts and sync it, and it names the encryption and the container model, but it never names cloudd. I checked both documents I fetched for the word and got zero mentions in each.

The user-facing half is covered by Apple’s iCloud data security overview, which is where the useful quotation lives. Apple writes that standard data protection is the default setting for your account, that your iCloud data is encrypted in transit and stored in an encrypted format at rest, that the encryption keys from your trusted devices are secured in Apple data centres so Apple can help you with data recovery, and that Advanced Data Protection is an optional setting where your trusted devices retain sole access to the keys. It also states that all new Apple Accounts require two factor authentication, and that end-to-end encryption is one of the features that requires it.

That article is the place to go if the question behind your search is whether cloudd is sending your data to Apple. The answer is that it syncs with Apple’s servers by design, which is what iCloud is, and Apple’s own page tells you exactly how much of it Apple can read in each of the two modes.

Is it malware, and can you turn it off

No, and mostly no.

On malware, everything measurable says otherwise. The binary is Apple’s, signed, on a read-only system volume with Platform identifier 26, which an app you downloaded cannot obtain. Its databases live in a folder macOS will not let an ordinary user list. And the job it does is the one that stops your Notes and your keychain from diverging between devices, which is not a description of anything a malicious process would want to announce.

On turning it off, the design works against you. There is no KeepAlive, so there is no switch that keeps it stopped. Both property lists opt in to being reclaimed under memory pressure, which means the operating system treats it as disposable on purpose and will start it again the moment something needs it. Force quitting it from Activity Monitor looks successful for a few seconds and then the next sync request starts a new process, which is why the same advice appears in every forum thread and never fixes anything.

What does work is turning off the thing that is asking it to sync, and that is a per-service choice in System Settings, under Apple Account, then iCloud:

ToggleWhat stops
iCloud Drivefile and record sync for Drive, Desktop and Documents
Passwords and KeychainiCloud Keychain, which is one of the busiest containers in the list above
Safaritab, bookmark and reading list sync
Photoshanded to cloudphotod rather than cloudd, a separate process with its own page
Screen Timethe Screen Time container, which also carries device settings

Turning all of them off, or signing out of iCloud, is the only thing that makes cloudd go quiet, and both of those are bigger decisions than the process deserves. The one thing not to do is the thing search results suggest first: a cleanup utility that offers to purge the CloudKit cache or reset the sync state. macOS will not let most such tools touch that folder anyway, and a reset that does work costs you a re-download of everything the cache was holding rather than saving you anything.

What to do about it

Nothing, in the ordinary case. The numbers above are the argument: 0.07 percent of one core averaged across the entire life of the process, 14 MB of a 100 MB allowance, an hourly log volume in the tens while the machine is idle, and its own scheduler placing anything it does at maintenance priority so it yields to you.

There are two cases where a minute of attention is warranted, and neither is about the process itself.

If the Mac is warm and busy while unattended, look at what changed rather than at cloudd. Its two scheduled tasks are a daily cache eviction and a weekly token registration; everything else it does is a response to another process asking. A sustained load therefore means something is asking it constantly, and the place that shows up is the container counts in the log, not the CPU column.

If data use is the worry, the same measurement applies from the other direction. A sync that is behind will move data until it catches up, and the container list tells you which feature is behind. Check the iCloud section of System Settings for a progress line before hunting for a leak, and remember that a first download on a new Mac is the one time this process is genuinely meant to be busy for hours.

What this page cannot tell you

The databases could not be read, only measured. The folder they sit in returns Operation not permitted to an ordinary user, and there is no attempt here to work around that, which is why the four file names above come from the list of open files rather than from a directory listing, and why nothing on this page says what is inside rows.

The documentation line is thinner here than on any page in this series. Apple ships 305 bytes of man page, and neither the CloudKit developer page nor the iCloud security article mentions cloudd by name, so the man page, two property lists, one log and a handful of entitlement names are carrying most of the weight. Where Apple is silent, this page says so rather than filling the gap, which is the case for the two triggers with manatee in their names and the letters in the protection class requirement.

And the log has its own limit from the other direction. Identifiers arrive hashed and paths arrive as private markers, so counts are trustworthy and identities are not.

All of it comes from one Mac and one build in one 24 hour window: macOS 27.0.1, build 26A434, M1 Pro, 25 days of uptime. A page about a moving target is only as good as the build it was written on.

Where window managers fit

Nothing here changes how your windows behave, and no amount of iCloud hygiene makes a desktop easier to work in. The two do meet at the same feeling, though, which is a Mac that appears to be doing a great deal you never asked for: syncing records, checking apps, indexing a disk, resolving names. That is the invisible half of using a Mac, and windows are the visible half, which usually means a screen full of them and Control Up pressed like an expedition.

Ribbon takes the other approach. Windows stay at full size on a single scrolling strip instead of stacking on top of each other, so the window you want is one swipe away and nothing ends up buried 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 before installing anything.

The short version

cloudd is the CloudKit daemon, which means it is how your Mac syncs records with iCloud: iCloud Drive’s metadata, the keychain, Safari tabs, Screen Time, Shortcuts, call history and around eighty other containers on this machine alone. Apple’s own man page is 305 bytes long and says there are no options and that you should not run it manually.

Two copies run at once, one for your session and one for the system, both labelled com.apple.cloudd with .system appended to the system copy’s doors. It has no KeepAlive, it opts in to being reclaimed under memory pressure, and its last exit on this Mac was a deliberate jetsam reclaim, which is why it disappears and comes back. Its two scheduled jobs run at maintenance priority, once a day and once a week. Its books are four SQLite files in a folder macOS will not let you list, and its last measured cost was 14 MB of memory and about two and a half minutes of processor time across two and a half days.

The one thing worth remembering is the number 82. That is how many separate features were asking this one process to sync something in a single day, and it explains every contradictory answer you will find about whether cloudd is fine. It is fine. It is just very busy on behalf of a great many things at once.

Questions

What is cloudd on Mac?

It is the daemon that runs CloudKit, the service that keeps records in step across your devices. Its path is /System/Library/PrivateFrameworks/CloudKitDaemon.framework/Support/cloudd, it is signed by Apple, and Apple's own man page for it says, in full, that it is the system daemon backing the CloudKit feature, that there are no configuration options to it, and that users should not run it manually. On this Mac it used 14 MB of memory and about 2 minutes 25 seconds of processor time across 2 days 9 hours of running. It exists on your machine because iCloud does, and what it does all day is answer requests from other processes that want something synced.

Is cloudd a virus or malware?

No. It is Apple's own code, signed under the identifier com.apple.cloudd with the authority macOS Software Signing and Platform identifier 26, and it lives inside a framework in the System folder rather than anywhere an installer can write. It carries 55 entitlements that only system daemons have, including keychain access and the ability to impersonate a URL session, and the folder it keeps its databases in is protected by macOS so that an ordinary user cannot even list it. The name looks suspicious only because it is short, lower case and ends in d, which is the same Unix convention that gives you httpd and sshd.

Why is cloudd using CPU or network?

Because something on the Mac asked it to sync. It is a request-driven process, not a scheduled scanner: launchctl reports the reason it is awake as ipc, meaning another process knocked, and its hourly log volume on this Mac ran between 36 and 78 lines an hour overnight, then jumped to 7,799 lines in one hour and 13,808 in another when things were actually happening. The work itself is record sync, chunk upload and download, and the retry logic around both, which is why a spike lines up with a change you made on another device rather than with anything you did on this one.

Can I stop or disable cloudd?

There is nothing running to stop most of the time. Its launch job has no KeepAlive, both of its property lists set EnablePressuredExit to true, and launchd reports its last exit reason on this Mac as JETSAM_REASON_MEMORY_IDLE_EXIT, which means macOS reclaimed it on purpose because it was idle. Force quitting it just means it opens again the next time a process asks. The only switch that really stops the sync side is in System Settings, Apple Account, iCloud, either by turning off individual services such as iCloud Drive, Passwords and Keychain, or by signing out of iCloud altogether. Everything else is theatre.

What is the difference between cloudd, bird and cloudphotod?

cloudd is the CloudKit daemon, the general layer that talks to iCloud on behalf of many features: iCloud Drive records, Passwords and Keychain, Safari tabs and settings, Screen Time, Shortcuts, call history and more. bird is the iCloud Drive daemon specifically, and the Finder talks to a File Provider extension that asks bird for files. cloudphotod is the photo library sync engine. Put them in a sentence and it reads: cloudphotod decides what Photos needs the server to know, bird moves iCloud Drive files and their placeholders, cloudd syncs the records everything else keeps in iCloud, and nsurlsessiond carries the bytes that outlive the process that asked for them.

Ready? Buy Ribbon for $15, or read all the guides.