What is backupd, and why is it using CPU and disk?
- It’s Time Machine.
backupdmakes your backups and manages their history. It gets busy every time a backup runs, hourly by default, and most of all during the first one. - When it’s normal: a first backup, which Apple says may take longer than you expect, and any hour in which lots of files changed. Apple says later backups copy only what changed since the last one.
- Disk on the Mac: Time Machine also keeps local snapshots on your startup disk. macOS counts that space as available and deletes snapshots when it needs the room, but you can clear them sooner.
1. What backupd is
backupd lives at /System/Library/CoreServices/TimeMachine/backupd and runs as a system daemon, started by launchd from /System/Library/LaunchDaemons/com.apple.backupd.plist. Its manual page calls it the Time Machine backup daemon, responsible for creating backups and managing backup history. A second process, backupd-helper, decides when a backup is due and starts it.
It copies changed files to your backup disk, and it also takes local snapshots of the startup disk, so you can restore recent files when the backup disk isn’t connected. Apple says Time Machine saves one snapshot about every hour and keeps it for 24 hours, keeps another of the last successful backup until space is needed, and saves one before installing a macOS update.
2. Why it’s busy
A backup means working out what changed, reading those files and writing them to the backup disk. Apple names the things that make that slow:
- The first backup copies everything, so it’s far longer than the hourly ones that follow.
- Large files that change often, such as some app databases and virtual machine disks, are copied again every time they change.
- Apps that keep the backup disk busy, such as antivirus tools scanning it.
- A network backup disk, where speed depends on the network. Apple suggests connecting the disk directly if you can.
- An old backup disk format. Apple says an APFS-formatted backup disk performs better on macOS Big Sur and later.
You can keep using the Mac during a backup; Apple designed it to run in the background.
3. What to do about it
- Check progress in the Time Machine menu in the menu bar, which shows how much of the current backup is done. In Terminal,
tmutil statusprints the running backup’s state. - Exclude what you don’t need backed up, such as virtual machines, build folders or downloads you can fetch again, in System Settings › General › Time Machine › Options. In Terminal,
tmutil addexclusiondoes it for one item. Apple notes excluded items still appear in local snapshots. - Back up less often if hourly is too much: in the same Options, change Backup Frequency to daily or weekly.
- Skip one backup from the Time Machine menu, or with
tmutil stopbackup, if you need the Mac’s full speed right now.
For local snapshots, list them first, then ask Time Machine to thin them. In the second command the numbers are how many bytes to try to reclaim and an urgency level from 1 to 4, as the manual page describes:
tmutil listlocalsnapshots /
tmutil thinlocalsnapshots / 999999999999 4
To remove one snapshot, give its date from the list, such as sudo tmutil deletelocalsnapshots 2026-11-21-101500. Apple’s own way is to set Backup Frequency to Manually, wait a few minutes for the snapshots to be deleted, then turn automatic backups on again. Usually you can just leave them: Apple says they don’t use the space needed for downloading, copying or installing, and are deleted as space is needed. More in our guide to local snapshots.
4. Should you quit or disable it?
Don’t force-quit backupd in Activity Monitor during a backup; launchd simply starts it again. If you need a backup to stop, use Skip This Backup in the Time Machine menu, or tmutil stopbackup, which the manual page describes as cancelling a backup in progress.
You can turn automatic backups off, though you’d lose the protection they give. Set Backup Frequency to Manually in Time Machine’s Options, or run sudo tmutil disable, which the manual page says needs root and Full Disk Access; sudo tmutil enable turns them back on. The daemon itself is part of macOS’s sealed system volume and stays installed; there’s no reason to touch System Integrity Protection.
Don’t delete backups on the backup disk in Finder to speed things up. Apple says Time Machine deletes the oldest backups by itself when the backup disk is full.
Questions
Why does backupd run every hour?
Time Machine backs up hourly by default, keeping hourly backups for the past 24 hours, daily ones for the past month and weekly ones before that. You can change the frequency in Time Machine’s Options.
Why is my first Time Machine backup so slow?
It copies everything on the Mac. Apple says later backups are faster because only changed files are copied.
Do local snapshots fill my disk?
They take space, but macOS counts it as available and deletes snapshots as they age or when space is needed. Apple says Time Machine stores them only on disks with plenty of free space.
Does backupd run without a backup disk?
With Time Machine set up, it can still make local snapshots while the backup disk is away, so it isn’t completely idle.
How SiftMac handles it. SiftMac’s System Data view counts your local Time Machine snapshots (it asks tmutil listlocalsnapshots /) and shows them inside Space macOS frees by itself, explained but never removed, since macOS deletes them when it needs the room.
Download SiftMac · scanning is free, and so is your first 2 GB of cleaning · See how it works