Why Your Mac Slows to a Crawl During Time Machine Backups

You’re trying to work and notice everything is sluggish. Then you spot the Time Machine icon in the menu bar, slowly rotating. A backup is running. You glance at Activity Monitor — backupd is at 200% CPU, mds_stores is at 150%, your SSD is being hammered. Welcome to backup-time on a busy Mac.

Time Machine is one of macOS’s best features, but it’s also one of the most aggressive about resource usage during backups. The good news is most of the slowness is fixable — without disabling backups, which you absolutely shouldn’t do.

What Time Machine actually does during a backup

You think it’s just copying changed files. It’s actually:

1. Reading the file system to find changed inodes
2. Generating an APFS local snapshot
3. Comparing your data against the previous backup
4. Computing what’s new (deltas, not just whole files)
5. Encrypting the backup data (if encrypted)
6. Writing to the backup destination
7. Cleaning up old backups by thinning hourly → daily → weekly
8. Verifying integrity

Each of those steps competes with whatever else you’re trying to do. The first time you back up after a long delay is the worst — there’s a lot to compare and write.

There’s a faster waySweep diagnoses what’s eating your performance and clears it in seconds. Try Sweep free →

First test: is it actually Time Machine?

Open Activity Monitor → Disk tab. Sort by Bytes Written. If backupd is at the top with sustained high I/O, yes, Time Machine is your slowdown. If it’s something else (like bird, mds_stores, or photoanalysisd), the backup is just coincidental.

Fix 1: Adjust the backup interval

Time Machine defaults to hourly backups. For most people this is overkill — daily would do fine. Apple removed the GUI for changing the interval, but Terminal still works:

sudo defaults write /Library/Preferences/com.apple.TimeMachine.plist AutoBackup -int 0

That disables auto-backup. Don’t actually use that — instead, third-party tools like TimeMachineEditor (free, donationware) let you set custom schedules without losing automatic backups entirely. Common config:

• Backup at lunch and at night (when you’re not using the Mac)
• Skip business hours

The slowdown disappears because backups happen when you’re not there.

Fix 2: Move the backup destination to a faster drive

Time Machine destination speed is a major factor. Slow destinations make backups take longer, which means more total slowdown time even if peak slowness is the same.

Speed of destinations, fastest to slowest:

• USB-C SSD over USB 3.2 Gen 2 (10 Gbps) — very fast
• Thunderbolt SSD — also very fast
• USB-C SSD over USB 3.0 (5 Gbps) — fast
• USB 2.0 anything — slow
• Time Capsule / network share over Wi-Fi 5 — slow
• Time Capsule / network share over Wi-Fi 6 — moderate

If your Time Machine destination is a 10-year-old USB 2.0 hard drive, that’s why backups take an hour. Modern external SSDs are cheap; a 1 TB USB-C SSD costs less than a few hundred dollars and makes backups finish in minutes instead of hours.

Fix 3: Exclude folders that don’t need backing up

Time Machine backs up everything by default. There’s no reason to back up:

• Downloads (these are mostly things you can re-download)
• ~/Library/Caches (already excluded by Apple, but worth checking)
• VMs (huge files that change every time you boot the VM)
• Docker images
• Node_modules folders (huge, regeneratable)
• Steam/game install folders (regeneratable)
• Adobe cache files

To exclude:

1. System Settings → General → Time Machine → Options
2. Click + to add folders to the exclusion list
3. Add the heavy folders that you don’t actually need backed up

Each excluded folder reduces both backup time and ongoing snapshot churn.

Fix 4: Clear out old local snapshots

macOS keeps local snapshots on the internal SSD even when an external backup drive isn’t connected. Useful for “oh no I deleted that” recovery — but they take real disk space, sometimes hundreds of GB.

Check current local snapshot space:

tmutil listlocalsnapshots /

You’ll see a list of snapshots. To delete old ones:

tmutil deletelocalsnapshots <date>

Or to thin them automatically:

sudo tmutil thinlocalsnapshots / 1000000000 4

(That tries to free 1 GB of snapshot space.)

Local snapshots are managed by macOS but the management is conservative. Manual thinning before a backup can speed up the next one significantly.

Fix 5: Check what changed since last backup

If a backup is taking dramatically longer than usual, something probably changed. Common causes:

• A virtual machine was used (10+ GB of disk written)
• A huge download finished
• A folder of photos was imported
• Xcode rebuilt a project (lots of derived data)
• A development tool ran tests with massive logs

You can see what’s being backed up by tailing the Time Machine log:

log stream --predicate 'subsystem == "com.apple.TimeMachine"'

This shows you exactly what files are being backed up in real time. Useful for spotting the actual culprit.

Skip the manual huntSweep finds every cache, log, and forgotten file slowing your Mac in seconds. Download Sweep free →

Fix 6: Verify the backup destination is healthy

A failing backup drive can make Time Machine retry, write inefficiently, or get stuck. Symptoms:

• Backups that “fail” but the next one works
• Backups that take 10x longer than usual
• Time Machine showing “Preparing backup” for very long periods

Check the drive:

1. Disk Utility → select the backup drive
2. Run First Aid

If errors come up, replace the drive before it dies completely. Time Machine drives die — they’re hammered with writes constantly.

Fix 7: Don’t run Time Machine over Wi-Fi if you can avoid it

Wi-Fi Time Machine (to a Time Capsule, an AirPort base station, or a NAS) is much slower than wired. The whole Mac slows down because the network connection is saturated, not because of disk I/O.

If you’re using a NAS or Time Capsule:

• Switch to Ethernet for the backup
• Or move to a directly-connected USB-C drive

Direct-attached storage is faster, simpler, and less prone to slow down everything else.

Fix 8: Disable Spotlight indexing on the backup drive

Time Machine drives don’t need to be searchable. Spotlight indexing them adds work for no benefit:

1. System Settings → Spotlight → Search Privacy
2. Add the backup drive

Indexing on the backup drive stops. The actual restore from backup still works fine — Time Machine doesn’t use Spotlight for restore.

Fix 9: Run a cleanup before the next backup

The smaller your data set, the faster Time Machine backs it up. If your ~/Library/Caches/ is 30 GB, every backup is dragging that 30 GB through the comparison process. If your Downloads folder has 100 GB of stuff you don’t need, same.

A pre-backup cleanup pays off in two ways: faster current backup, and faster every subsequent backup.

Sweep handles this in one scan. It surfaces caches, logs, language packs you don’t speak, leftover preferences from uninstalled apps, and big forgotten files. You see exactly what’s about to be removed before anything happens. Notarized by Apple, free to download.

Don’t restart — cleanSweep clears the buildup that’s actually slowing your Mac. No reboot needed. Free for macOS →

Fix 10: Use multiple backup destinations

Time Machine supports rotating destinations. Use one drive on weekdays, another on weekends. This:

• Halves the wear on each drive
• Reduces “this backup takes forever” because each drive has half the data churn
• Provides redundancy

Add a second destination in System Settings → General → Time Machine → click + next to your existing destination.

When you should temporarily skip a backup

Sometimes you legitimately need to skip a backup — you’re in a meeting, on battery, in the middle of an important render. Right-click the Time Machine menu bar icon and choose “Skip This Backup.” It picks up at the next scheduled time.

Don’t disable Time Machine permanently. Skipping individual backups is a great safety valve.

A weekly Time Machine maintenance routine

Once a week, two minutes:

1. Plug in your backup drive (if not always connected)
2. Right-click TM icon → Back Up Now
3. Wait until it finishes
4. Eject the drive properly

Once a month:

1. Run Disk Utility First Aid on the backup drive
2. Check ~/Library/Caches/ and clean if big
3. Check that exclusion list still makes sense

Once a year:

1. Replace the backup drive (or check warranty)
2. Test a restore (yes, actually try it)

That’s enough to keep Time Machine fast and reliable for years.

When backups still slow your Mac after all that

The honest answer: backups are inherently disruptive. Even an optimal Time Machine setup will impact your Mac for the duration of a backup. The fix is making backups infrequent enough that they don’t matter — daily instead of hourly, scheduled at night, on a fast drive.

Apple’s default of hourly backups is conservative for safety. For most users, twice-daily backups offer 95% of the protection with 25% of the disruption.