Thrum

What is CloudKeychainProxy, and why is it running on my Mac?

Last reviewed: 19 November 2026. Path, launchd job and man page checked on macOS 26.3.1.

CloudKeychainProxy is part of iCloud Keychain syncing in macOS: it relays keychain sync data between the Mac's security services and iCloud key-value storage. It runs briefly when keychain items or the set of trusted devices change, and launchd stops it when it is idle. It is part of macOS and safe.

CloudKeychainProxy at a glance

CloudKeychainProxy
Made byApple (part of macOS, iCloud Keychain)
TypeLaunch agent (background process for your user)
Location/System/Library/Frameworks/Security.framework/Versions/A/Resources/CloudKeychainProxy.bundle/Contents/MacOS/CloudKeychainProxy
Runs asyour user
Started bylaunchd job com.apple.security.cloudkeychainproxy3
Can you quit it?Yes, but launchd starts it again when keychain sync has work to do.

What is CloudKeychainProxy?

Its man page says only that it is part of iCloud keychain syncing. Its launchd job shows how: it is woken by a notification named for a change in its iCloud key-value store, by keychain lock and unlock events, and by requests to force an update. Apple's Platform Security guide says the signed syncing circle is stored in iCloud key-value storage, the service this proxy watches.

It lives inside the Security framework itself, next to the code that manages the keychain, and runs as your user only when there is something to relay.

Is CloudKeychainProxy safe?

Yes. It is inside Apple's Security framework on the read-only system volume. Apple's guide says synced keychain items are encrypted so that only devices in your circle can decrypt them, not Apple.

Why does CloudKeychainProxy use so much CPU and network?

How much CPU is normal for CloudKeychainProxy?

Short runs after unlocking and when passwords change are normal. Between them it typically is not running at all.

What can you do if CloudKeychainProxy keeps using CPU?

  1. Answer any iCloud Keychain prompt. A pending request to approve this Mac can leave syncing unfinished. Approve it from another device if it is yours.
  2. Check Passwords sync. In System Settings, click your name, click iCloud, then click Passwords, and check that Sync this Mac is on (or turn it off if you do not use iCloud Keychain).
  3. Restart the Mac. A restart ends any stuck sync and lets launchd start the proxy only when needed.

When should you worry about CloudKeychainProxy?

Continuous CPU use for a long period is not its normal pattern. If it returns after a restart, turning Passwords sync off and on again under System Settings > your name > iCloud > Passwords is a reset you can try; the Mac may then need approval from another device again.

How do you check CloudKeychainProxy in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type CloudKeychainProxy in the search field. The CPU tab shows its % CPU. The Network tab shows its Sent Bytes and Rcvd Bytes. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every CloudKeychainProxy 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 'CloudKeychainProxy' | grep -v grep
nettop -p <PID>    # PID from the ps line above

How can Thrum help with CloudKeychainProxy?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when CloudKeychainProxy is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click CloudKeychainProxy 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 CloudKeychainProxy

Is CloudKeychainProxy the same as the keychain?

No. The keychain is managed by the security daemons. CloudKeychainProxy only relays sync data between them and iCloud.

Why is the launchd job called cloudkeychainproxy3?

The number is part of Apple's label for the current version of the job. It is the only CloudKeychainProxy job on macOS 26.

Sources