Time Machine Backup Slow? Check the Stage Before Changing It
A slow Time Machine backup needs a different response depending on whether it is preparing, copying files, or finishing. Before changing exclusions or replacing a disk, record the stage and the last successful backup, then change one thing and compare the next run.
Check the Stage Before Changing Anything
Apple's Time Machine guide explains how to check progress and the last completed backup from the Time Machine menu in the menu bar. Use that display rather than an estimate of how long a backup ought to take.
Record the destination, whether this is its first backup, the displayed stage, and any error. Check again later against the same destination; a changing count or stage is more useful evidence than an estimated finish time.
| What you see | What to check | First response |
|---|---|---|
| First backup | No completed backup on this destination | Allow an uninterrupted run before comparing with later backups |
| Preparing | Recent update, interruption, or days without a backup | Let the preparation finish and watch for a stage change |
| Copying slowly | Network destination or frequently changed large files | Test one connection or workload change |
| Cleaning up | Whether the run eventually completes | Wait for completion, not just the end of copying |
| Destination unavailable | Power, cable, network visibility, or sleeping host | Restore access before judging speed |
The first backup can take longer, and later ones copy changed files. Apple also says Time Machine removes older backups as the destination fills, so copying bytes is not the only work involved. Do not erase history because a progress estimate looks unhelpful.
Give Preparation Time to Finish
Apple's preparation explanation describes comparing current files and folders with the previous backup. Interruptions, an improper shutdown, an unejected disk, an update, or several days without backups can lengthen that stage.
If you recently changed a folder containing many small files, note that folder and the stage where time is spent. File count alone does not establish a fault or predict a duration; compare a later run without that workload before blaming the disk.
Avoid repeatedly stopping a run just because copying has not started. If an actual error appears, record its wording and the destination instead of treating every long preparation as the same problem.
Test the Connection and the Mac's Workload
Apple's slow-backup guidance says backups slow when a Mac is busy, hot, or low on battery. Try a run on power with demanding work paused, then compare completion with your earlier observation.
For a network destination, test a stable wired connection if available, keeping the destination and exclusions unchanged. Apple specifically documents Ethernet for an initial Time Capsule backup; do not assume a NAS has the same ports, settings, or performance.
Check destination availability before tuning anything. A directly attached disk needs power and a firm connection; a disk shared by another computer needs that host awake. For a controlled test, leave the backing-up Mac awake too, without making a permanent sleep-setting change.
If the backup works while awake but repeatedly misses the period you expected, record power and sleep conditions for support. Do not conclude that every Mac model backs up in sleep, or that none do.
Exclude Only Data You Can Replace
On macOS Tahoe 26, Apple's exclusion instructions use System Settings › General › Time Machine › Options. Add an exact file or folder to exclude it; remove that entry to include it again, then finish with Done.
- Read the current list before adding anything. A folder called cache is not proof that it is currently being backed up.
- Choose one verified rebuildable cache or disposable virtual machine, rather than its parent folder.
- Keep source files, configuration, and a separate backup of any wanted VM before excluding it.
- Run another backup and compare its stage and completion; undo the exclusion if it does not justify the lost coverage.
Treat a frequently changed VM as a candidate to investigate, not a universal exclusion. A VM containing your only copy of documents is not disposable, and a cache can be rebuilt only while its original sources remain available.
Removing an exclusion restores eligibility for future backups; it cannot supply the versions missed while excluded. Apple also notes that excluded items can still appear in local snapshots. Exclusion is neither deletion nor proof of an independent backup.
Keep the Destination Usable
Apple recommends using the backup disk for Time Machine, rather than mixing ordinary files into its backup volume. Check that the destination stays connected and that a subsequent backup really completes before declaring the issue resolved.
If you see disk errors or repeated disconnections, preserve your existing backup and investigate the device. The Disk Utility First Aid guide covers that separate decision; erasing a disk is not a speed test.
For cache decisions, see which Mac caches are safe to delete. Do not clear caches just to make a backup smaller while also changing its exclusions, because you would lose the comparison.
Where Mole Fits
Mole Mac's Clean can offer Purgeable Space for releasing local Time Machine snapshots when eligible, with checks that withhold the action during an active or indeterminate backup. Optimize has no Time Machine backup-speed control; local snapshot release is not destination repair or a network-backup accelerator.
The separate local snapshot guide covers that space decision. Leave snapshots alone while diagnosing a slow backup and use Time Machine's own progress as the completion check.
FAQ
How Long Should the First Backup Take?
There is no single useful deadline for every Mac and destination. Apple says the first backup can take longer; compare later runs only after it has completed, with the same destination available.
Should I Exclude Every Cache and Virtual Machine?
No. Check existing exclusions and recoverability first, then test one exact item. Keep a separate backup for wanted VM data and retain anything you cannot recreate.
Should I Delete Snapshots to Make Backups Faster?
Do not use local snapshot deletion as a speed fix. Establish whether the delay is preparation, copying, finishing, or destination access, then verify a completed backup after one controlled change.