Time Machine is supposed to be the quiet, dependable assistant that saves your Mac while you do more important things, such as answering email or pretending your desktop is organized. Then one day it sits on Preparing backup… for what feels like an entire geological era.
Before assuming the backup is broken, remember that “preparing” is real work. Time Machine compares the current contents of your Mac with the most recent backup, identifies changed files, creates or manages local snapshots, and checks the destination. That process can take much longer after a macOS update, an interrupted backup, an improper shutdown, several days without access to the backup disk, or a major change to your files.
If the status never advances, however, use the steps below in order. Start with the safe, simple fixes and save disk erasure for the very end. Your backup drive is not the place for experimental enthusiasm.
How Long Should “Preparing Backup” Take?
There is no universal time limit. A small incremental backup to a directly connected SSD may prepare in minutes. A first backup containing hundreds of gigabytes, a backup over Wi-Fi, or a deep comparison after an interruption may take hours.
Look for signs of activity before canceling anything:
- The “Found” file count continues to increase.
- The backup drive light flashes or the drive appears active in Disk Utility.
- Time Machine eventually changes from “Preparing” to a progress measurement.
- Your Mac recently installed an update or reconnected to a drive after several days.
If the count is changing, let the process run while the Mac is connected to power and the backup disk remains available. If nothing changes for several hours, the Mac becomes unusually sluggish, or Time Machine repeatedly returns to the same status after restarts, begin troubleshooting.
1. Stop the Backup Gracefully and Restart the Mac
Open the Time Machine menu in the menu bar and choose the option to stop or skip the current backup. Give macOS a moment to finish closing the operation. Do not pull the cable while Time Machine is writing merely because patience has left the building.
After the backup stops, restart the Mac. Reconnect the external drive if necessary, confirm it appears in Finder, and choose Back Up Now. A restart clears temporary processes, remounts the backup volume, and often resolves a preparation loop caused by a stalled background service.
If Time Machine Will Not Stop
Wait a few minutes before forcing a shutdown. If the Mac is completely unresponsive, hold the power button only as a last resort. Once the Mac starts again, check the backup drive with Disk Utility before beginning another backup.
2. Check the Backup Drive, Cable, Hub, and Power
A backup cannot move quickly through a connection that is barely holding a conversation. If the disk is connected through a USB hub, dock, adapter, or monitor, connect it directly to the Mac. Try another compatible cable or port. For desktop hard drives with separate power adapters, verify that the power connection is secure.
Open Finder and make sure the drive appears in the sidebar. If it disconnects randomly, makes repeated clicking sounds, or disappears from Disk Utility, stop using it until the hardware problem is addressed. A failing drive is not a backup strategy; it is a suspense novel.
3. Confirm That the Destination Has Enough Space
Time Machine normally removes older backups as space is needed, but a nearly full or undersized disk can still cause errors. Apple recommends a backup disk with at least twice the storage capacity of the Mac. In practical terms, a Mac with 1TB of internal storage is best paired with a 2TB or larger Time Machine disk.
Select the backup disk in Finder and choose File > Get Info to review available capacity. Also check the Mac’s internal storage under System Settings > General > Storage. If the internal disk is almost full, Time Machine may be unable to create the snapshot required for a backup. Remove or relocate unnecessary files, empty the Trash, restart, and try again.
4. Run First Aid in Disk Utility
File-system errors can leave Time Machine preparing forever, especially after a forced shutdown or an external drive was unplugged without being ejected.
- Stop the Time Machine backup.
- Open Applications > Utilities > Disk Utility.
- Choose View > Show All Devices.
- Select the lowest volume beneath the backup device and click First Aid.
- Continue upward through the related volumes and containers, ending with the physical device.
If First Aid reports that the disk was repaired, restart the Mac and retry the backup. If Disk Utility cannot repair the drive, preserve any accessible data before considering erasure or replacement. Do not erase a backup disk until you understand that doing so permanently deletes its backup history.
5. Check for Antivirus, Security, and Cleanup Software
Security software can repeatedly scan the Time Machine destination, keeping the disk busy while Time Machine is also trying to catalog and write data. Update the security app and exclude the Time Machine backup disk from virus scanning. If the problem began immediately after installing or updating a security utility, temporarily disable that utility for one controlled backup test.
Third-party firewall tools can also interrupt backups to a network-attached storage device. Test with the firewall disabled only long enough to identify the cause, then configure an appropriate exception rather than leaving protection off permanently.
Be equally suspicious of cleaner, disk-monitoring, synchronization, and drive-health apps that continuously inspect mounted volumes. Useful utilities can become less useful when they all try to supervise the same disk at once.
6. Investigate Large or Frequently Changing Files
Virtual machines, development environments, database files, video-editing libraries, mail databases, and disk images may be enormous and may change even when only a small part of their contents changes. Time Machine can then treat the container as a newly changed file and spend considerable time processing it.
Open System Settings > General > Time Machine, click Options, and temporarily exclude a suspected folder. Run another backup. If preparation suddenly completes, you have identified a likely bottleneck.
Exclusion is not the same as protection. If the folder contains important data, back it up with a method recommended by the application developer. For example, a virtual machine may be safer when shut down before backup, while a database may require its own export or snapshot procedure.
7. Treat Network Backups as a Network Problem Too
When Time Machine backs up to a NAS or another Mac, the preparation stage depends on Wi-Fi quality, server availability, permissions, free space, and the health of the network backup image.
- Confirm that both the Mac and server are connected to the same working network.
- Use Ethernet for a test when possible.
- Restart the router and backup server if other network symptoms are present.
- Open Finder and verify that the destination remains mounted.
- Reselect the backup disk in Time Machine settings if its password or network address changed.
For supported network backups, hold the Option key while opening the Time Machine menu and choose Verify Backups. Verification may detect damage that prevents a new backup from completing. If verification fails repeatedly, you may need to create a new backup set after preserving any recoverable history.
8. Start the Mac in Safe Mode
Safe mode helps determine whether login items, extensions, or third-party background software are interfering with Time Machine.
Apple Silicon Mac
- Shut down the Mac.
- Press and hold the power button until startup options appear.
- Select the startup volume.
- Hold Shift and click Continue in Safe Mode.
Intel-Based Mac
- Restart the Mac.
- Immediately hold Shift until the login window appears.
- Log in; a second login may be required.
Connect the backup disk and try Back Up Now. If Time Machine works in safe mode, restart normally and review login items and recently installed utilities. Remove or update the software most likely to be accessing the disk.
9. Check the Backup Disk Format
APFS and APFS Encrypted are the preferred formats for new Time Machine backup disks. Older Mac OS Extended backup sets can still be supported, but an APFS-formatted disk may provide better performance on modern macOS versions.
In Finder, select the backup disk, choose File > Get Info, and read the Format field. Reformatting is not a casual repair step: it erases every backup and every other file on that volume. Consider it only after other fixes fail and after confirming that you no longer need the existing backup history.
10. Update macOS, Then Reselect the Backup Disk
Install compatible macOS updates from System Settings > General > Software Update, restart, and try again. Updates can correct bugs in storage, networking, and backup services, but the first backup after an update may itself spend longer preparing because Time Machine has more changes to evaluate.
You can also remove and re-add the destination in Time Machine settings. This does not automatically mean erasing the disk. Open System Settings > General > Time Machine, remove the destination from the configuration, and then add the same disk again. If macOS asks whether to claim existing backups, read the prompt carefully and choose the option that preserves the history you intend to use.
Should You Delete an “.inProgress” File?
Older troubleshooting guides often recommend deleting a file whose name ends in .inProgress from a legacy Time Machine backup. That advice may apply to some older Mac OS Extended backup structures, but modern APFS and network Time Machine backups are organized differently.
Do not rummage through the backup package deleting files simply because an old article says so. Manual deletion can damage the backup set or make restoration harder. Use Apple’s supported controls to stop the backup, Disk Utility to check locally attached storage, and Time Machine’s verification command for supported network backups. Consider manual intervention only when you fully understand the backup format and have another current copy of your important data.
When to Create a New Time Machine Backup
A fresh backup set becomes reasonable when Disk Utility cannot repair the destination, network verification reports persistent corruption, the disk repeatedly disconnects, or every backup fails after the simpler fixes. Before erasing anything, make a separate copy of irreplaceable files from the Mac to another device or a reputable cloud backup service.
If replacing the disk, choose a reliable device with enough capacity, connect it directly for the first backup, and allow the initial run to finish uninterrupted. Use the Time Machine volume primarily for backups. Storing the only copy of unrelated files beside the backup defeats the point: one disk failure could take both the original and the backup to electronic Valhalla.
Real-World Troubleshooting Experiences and Lessons
The following composite scenarios reflect common patterns reported by Mac users and support technicians. They are useful because “stuck preparing” is a symptom, not a single diagnosis.
Experience 1: The Backup Was Slow, Not Frozen
A MacBook owner reconnects a backup drive after three weeks of travel. Time Machine displays “Preparing backup” for two hours, and the owner assumes it has failed. The “Found” count is still rising, however, and the drive remains active. After the Mac is left connected to power overnight, preparation completes and the backup finishes normally.
The lesson is simple: recent updates, long gaps between backups, and large numbers of changed files can produce a legitimate deep comparison. Canceling repeatedly may force Time Machine to restart part of that work. Activity matters more than the clock.
Experience 2: The Innocent-Looking Hub Was the Culprit
An external drive appears in Finder but disconnects for a second whenever several devices share a bus-powered USB hub. Browsing ordinary files works, so the connection seems fine. Time Machine, which needs a long uninterrupted session, exposes the weakness. Connecting the disk directly to the Mac solves the problem.
This is why cable, port, hub, and power checks belong near the top of the list. They are fast, reversible, and embarrassingly effective. Troubleshooting does not award bonus points for beginning with Terminal.
Experience 3: Antivirus Software Created a Traffic Jam
A user updates macOS and also updates a security suite. The next Time Machine run stays in preparation while the antivirus scans every file the backup process touches. Excluding the dedicated Time Machine volume from real-time scanning allows the backup to complete.
The broader lesson is that two programs can both be working correctly and still obstruct each other. After any system update, review third-party security, firewall, disk-management, and cleanup tools before blaming Time Machine itself.
Experience 4: A Virtual Machine Changed Constantly
A developer’s virtual machine occupies 150GB. Opening it changes a large disk-image file, even after a minor work session. Time Machine repeatedly treats that giant container as changed, causing preparation and backup times to balloon. Temporarily excluding the virtual-machine folder confirms the cause.
The permanent solution is not to forget the folder forever. The developer adopts the virtualization app’s recommended backup process and keeps separate exports of critical projects. Time Machine remains responsible for ordinary Mac files instead of wrestling a digital refrigerator through the doorway every hour.
Experience 5: The Backup Disk Was Beginning to Fail
A drive repeatedly stalls, remounts, and makes unusual noises. First Aid reports errors it cannot repair. Starting over on the same hardware would create a clean-looking backup on an unreliable device, which is like repainting a canoe with a hole in it. The sensible move is to copy any accessible data, replace the drive, and build a new backup.
The most valuable habit from all these cases is redundancy. Time Machine is excellent for versioned local recovery, but one backup disk is still one physical object. Important files deserve another independent copy, ideally stored separately. Backups are comforting; tested restores are proof.
Conclusion
When Time Machine is stuck preparing a backup, begin by checking whether it is actually making progress. Then stop the backup properly, restart the Mac, inspect the connection, confirm free space, run First Aid, and test for interference from security or disk utilities. For network destinations, troubleshoot the network and verify the backup. Safe mode can expose third-party conflicts, while a new APFS backup disk is the final option when the existing set or hardware is no longer trustworthy.
Most preparation problems do not require deleting backup files or launching a dramatic Terminal command. Methodical checks are safer, faster, and considerably less likely to turn a slow backup into an ex-backup.
Note: Menu names can vary slightly by macOS version. Erasing, reformatting, or manually modifying a Time Machine disk can permanently remove backup history, so preserve important files elsewhere before taking destructive action.
