backupd high CPU on Mac? Time Machine, explained
backupd using high CPU on your Mac is Time Machine running a backup, usually normal and self-throttling. Here's when it's expected, when it isn't, and how to bring it back under control.
backupd is the Time Machine daemon. High CPU almost always means a backup is running, which is normal, and Time Machine is designed to throttle itself and stay out of your way. Here's when to leave it alone and when something's actually wrong.
What backupd does
It's the engine behind Time Machine: it runs backups (hourly by default), detects which files changed, copies them to your backup disk, and thins out older backups to make room. A helper, backupd-helper, mounts network destinations before a backup starts. If you don't use Time Machine, backupd shouldn't be doing anything.
Why it's using high CPU
- A backup is in progress: especially the first full backup, or a backup after large changes, uses real CPU, disk, and memory.
- A slow or large destination (a network drive or an older USB disk) drags the backup out.
- A deep-scan reconciliation when macOS's change-tracking (FSEvents) is invalidated and it has to compare everything.
- Local snapshots piling up on your internal disk while the backup destination is offline.
- An old "speed up Time Machine" tweak that disabled the built-in low-priority throttle.
Is backupd a virus?
No. It's a legitimate Apple daemon, and it only runs if Time Machine is configured.
What to do about it
- Usually, just wait. Time Machine deprioritizes itself and yields to your work by default; the first backup simply takes a while. Let it finish.
- If it's chronically pegged, check the throttle. An old tweak may have removed it; re-enable the default with
sudo sysctl debug.lowpri_throttle_enabled=1(1= throttling on). - Exclude large, volatile folders (VM images, big caches) from Time Machine so it isn't re-copying them constantly.
- Check the backup disk's health and connection; a failing or slow destination makes backups drag.
- A backup stuck on Preparing or Cleaning up can look like runaway CPU; a reboot often clears it.
What's normal vs not
High backupd CPU during a backup is expected and deprioritized by design. Chronic pegging is the signal something's off: usually a removed throttle, a failing/slow destination, or a forced deep scan.
See when a backup is the reason your Mac feels slow
A background Time Machine backup is a common, invisible reason a Mac feels sluggish for a few minutes. Plumby shows live CPU, disk, and network in your menu bar with the process named plainly, so you can see "it's just Time Machine, it'll finish" instead of guessing. Measured from your Mac's real state, never estimated. For the bigger picture of a slow Mac, see why is my Mac slow.
