What is coredatad, and why is it using network on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.
coredatad is the macOS agent that schedules CloudKit operations, meaning iCloud sync, for apps that store their data with Core Data and sync it through NSPersistentCloudKitContainer. It uses network when such an app has changes to upload or download. The app whose data is syncing is the real source of the work.
coredatad at a glance
| coredatad | |
|---|---|
| Made by | Apple (part of macOS, Core Data) |
| Type | Per-user agent |
| Location | /usr/libexec/coredatad |
| Runs as | your user |
| Started by | launchd job com.apple.coredatad |
| Can you quit it? | Not usefully. launchd starts it again when an app needs to sync. |
What is coredatad?
Core Data is Apple's framework for storing app data, and NSPersistentCloudKitContainer is the part that mirrors that data to the user's iCloud account through CloudKit. The coredatad man page says it handles CloudKit syncing for clients of Core Data with CloudKit and schedules CloudKit operations on their behalf.
It runs as your user through the com.apple.coredatad job, started on demand, and launchd may end it when memory is short. Both Apple apps and third-party apps can use this sync method.
Is coredatad safe?
Yes. It is in /usr/libexec on the system volume and signed by Apple. It only syncs data of apps that use Core Data with CloudKit, to the iCloud account signed in on the Mac.
Why does coredatad use so much network and CPU?
- First sync of an app. When you install or first sign in to an app that uses Core Data with CloudKit, its whole data set may be downloaded or uploaded.
- Large changes in an app. Importing many records or attachments into such an app creates a lot of data to sync.
- Sync retries. If iCloud is unreachable or the account needs attention, scheduled operations are retried later, which brings coredatad back repeatedly.
How much network is normal for coredatad?
Usually not running or idle. Short network bursts after you change data in a syncing app are typical.
Long uploads are expected after importing large amounts of data.
What do you do if coredatad keeps syncing?
- Find the app that is syncing. Think about which app you recently used heavily or installed. Apps with iCloud sync show their sync status in their own settings.
- Check your iCloud account. Open System Settings and click your name. Fix any sign-in or storage-full message, since sync cannot finish without them.
- Let large syncs finish. Keep the Mac online and awake until a large import has synced.
- Turn off iCloud sync in one app. If a single app's sync never finishes, turn off its iCloud option in its settings, or turn off that app under iCloud in System Settings, then contact its developer.
When should you worry about coredatad?
Worry only if coredatad sends large amounts of data for days without any change in your apps. That points to a sync loop in one app.
A copy outside /usr/libexec would not be Apple's.
How do you check coredatad in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type coredatad in the search field. The Network tab shows its Sent Bytes and Rcvd Bytes. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every coredatad process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). nettop shows its live network traffic.
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'coredatad' | grep -v grep
nettop -p coredatad
How can Thrum help with coredatad?
Thrum's Network tab shows upload and download speed for each process, including coredatad, and an optional second menu bar item shows the Mac's total upload and download speed. Click coredatad in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about coredatad
Is coredatad the same as cloudd?
No. cloudd is the general CloudKit daemon used by many apps. coredatad schedules CloudKit work for apps that use Core Data's CloudKit sync.
Can I disable coredatad?
No. It starts on demand and does nothing if no app needs Core Data sync.
Sources
- coredatad(8) man page: run man coredatad in Terminal
- launchd job /System/Library/LaunchAgents/com.apple.coredatad.plist on macOS 26.3.1