What is backupd on a Mac? Time Machine behind the scenes

27 October 2026 · 6 min read

backupd is the macOS process that runs Time Machine backups. When your Mac is backing up, backupd is the one reading your files and writing them to the backup disk, so it uses disk and some processor for as long as the backup runs. The first backup is the longest, often hours, and later ones are much shorter. It is normal, it is yours to keep, and it stops by itself when the backup finishes.

You will usually meet it as a name in a process list while the Mac feels slow and the disk light on your external drive is flashing. That is Time Machine doing its job.

What backupd does

Time Machine is the backup feature built into macOS. It copies your files to a disk you choose and keeps older versions so you can go back in time. backupd is the program that does the work: it works out what has changed since the last backup, copies those files, and keeps the backup tidy.

A second process, backupd-helper, decides when a backup should start. You will see both names in a process list. backupd-helper is the scheduler and backupd is the worker.

By default Time Machine backs up automatically every hour while the disk is connected, and you can see its state in System Settings under General, then Time Machine. It shows your backup disk, the latest backup and, while one is running, its progress. You can also start a backup by hand from the Time Machine menu bar item if you have turned it on.

Why the first backup takes so long

The first backup has to copy everything: every file in your user folder, your apps and your settings. That is the whole of what is on the Mac, not a few changes. A Mac with several hundred gigabytes of files can take many hours the first time, and a slow disk or a Wi-Fi network drive can stretch it to a day or more.

During that time backupd will read heavily from your internal drive and write heavily to the backup disk. It will also keep the processor busy checking and preparing files. That is expected. You can keep using the Mac, though it may feel a bit slower, particularly if your backup disk is a slow one.

After the first backup, each one only has to copy what changed since the last. Those are usually a few minutes at most, unless you have changed a lot, like importing a large video library.

Why a later backup is slow

If a normal backup suddenly takes a long time, the cause is nearly always one of these.

A lot changed. A big photo import, a video export or a folder of downloaded files makes the next backup large.
A big file that changes constantly. A virtual machine disk or a large database is one file, so a small change inside it means the whole file is copied again. Files like these are a common reason a backup is bigger than it should be.
A slow or nearly full backup disk. When the disk fills, Time Machine has to delete older backups to make room, which takes time.
The Mac was asleep or away. After a long gap, the next backup has a lot of catching up to do.
A network backup. Backing up over Wi-Fi to a network disk is much slower than a directly connected one.

If a backup never seems to finish, check System Settings, General, Time Machine for a message. An error about the disk, such as it being full or disconnected, is the first thing to rule out.

How to see what backupd is doing

You can check on a backup without special tools.

Open System Settings, then General, then Time Machine. While a backup runs, the status shows its progress, and it says if the disk is not available.
If you use the Time Machine menu bar item, click it. It shows the latest backup, and whether one is in progress.
Watch the disk. The backup disk’s light, or its sound if it is a spinning drive, will tell you it is working.
For Terminal users, tmutil status prints the current state of Time Machine, including whether a backup is running. It only reads, so it is safe to run.

Is it safe to stop a backup?

Yes, in the normal way. You can stop a running backup from the Time Machine menu bar item, and Time Machine tries again at the next backup. Do not pull the backup disk out in the middle of a backup. Stop the backup and eject the disk first, or wait until it finishes. Unplugging a disk while it is being written to is how backups get damaged.

What you should not do is end the backupd process itself from a process list. It runs as root, so ending it takes an administrator password, and it cuts the backup off instead of stopping it cleanly. You gain nothing either: Time Machine simply tries again at the next scheduled backup. If the Mac is struggling during a backup, stopping the backup from Time Machine is the cleaner way.

Making backups lighter on the Mac

If backups bother you while you work, these changes help.

Exclude big, replaceable folders. In the Time Machine settings, the Options button lets you add folders to leave out, such as downloads you can fetch again, large caches or virtual machine disks.
Use a fast disk and a direct connection. A solid-state disk on a good cable makes the difference between a backup you do not notice and one you do.
Leave room. A backup disk at least twice the size of what you back up means Time Machine does not have to stop and delete old backups as often.
Let it run while you are away. Plug in and leave the Mac awake at lunch or overnight, and the long ones finish without you noticing.

Time Machine is designed to run quietly in the background, and on most Macs you will not notice a routine hourly backup at all.

Seeing it in Foreman

Foreman is a Task Manager for macOS, and it labels backupd as “Time Machine backup” and backupd-helper as “Time Machine scheduler”, with the real names in grey, under System processes. While a backup is running, sort the CPU column on the Processes page to see how much processor the backup row takes next to the apps you are working in. Because backupd runs as root, macOS does not let an ordinary app read that process’s disk figures, so for the disk side pick Disk on the Performance page: its graph shows read and write for the whole Mac, which is a clear picture of what a backup does to your drive.

If the Mac feels slow and you are not sure why, a busy “Time Machine backup” row and a busy disk graph answer it in seconds: it is a backup, and it will end. If something else is on top, how to find out what’s running in the background on your Mac helps you find the cause. Foreman does not manage your backups, and it keeps no history of a process after it ends. Foreman is free for 24 hours, then $12 once.

For the related indexing work that often runs at the same time, see what mds_stores is on a Mac.

The short version

backupd runs Time Machine backups, and backupd-helper decides when.
It uses disk and processor while a backup runs, and that is normal.
The first backup is the longest, often hours. Later ones copy only changes.
Check progress in System Settings, General, Time Machine.
Do not end the process or unplug the disk mid-backup. Stop the backup from Time Machine instead.