How long a macOS upgrade takes, and when to book it

The question behind "how long does a Mac upgrade take" is almost never curiosity. It is a scheduling question. Something has to happen today, the Mac has been nagging for a week, and the person asking wants to know whether the gap between now and the next commitment is big enough. The honest answer has two parts: Apple does not publish a duration, and the duration is not the number that matters anyway. What matters is which parts of the process leave the machine unusable and which parts can be run in the background while work continues.

Why nobody publishes a number

Apple's own documentation on downloading and installing macOS describes the methods available and never states how long any of them take. That is not evasion. The elapsed time is dominated by variables that belong to the machine and the network rather than to the software.

The installer is measured in gigabytes, so the download alone scales with connection speed. Apple does note one thing about size, which is useful:

Software Update is the fastest and easiest way to get macOS updates and upgrades, and it can use less storage space to download and install them.

That distinction between an update and a full upgrade is the single biggest fork. Moving from one version of macOS 26 to the next is a different operation from moving from macOS 15 to macOS 26, and the two get discussed as though they were the same thing.

The second reason no number exists is that the process is not one continuous operation. It is four, and only two of them require the Mac to be left alone.

The four phases

Treating the upgrade as a single block is what causes people to lose an afternoon or, worse, to start it forty minutes before a call.

Phase	What happens	Is the Mac usable
Download	The installer is fetched in the background	Yes, normally
Prepare	The installer is unpacked and verified	Yes, with some slowdown
Restart and install	The system is replaced, with progress bars and reboots	No
First login	Setup prompts, indexing, app permissions	Partly, and slowly

The download can be started at any point, including during a working morning, and it will continue while other work happens. The prepare phase is similar. The restart and install phase is the one that owns the machine completely, and it is the only phase where a screen must not be needed for anything else.

That is why the plan to upgrade after lunch tends to go wrong. The download was never started, so the whole sequence begins from zero at the moment the gap opens. Starting the download the previous evening removes the largest and most variable component from the window that has to be booked.

What actually determines the length

Five factors account for nearly all the variation between one Mac and another.

Connection speed against installer size. This is arithmetic, and it can be estimated before starting. A multi gigabyte download on a slow or shared connection is the difference between minutes and hours, and it is the part most affected by doing it overnight.

Whether it is an update or an upgrade. Point releases within the same major version replace less. A jump across major versions replaces the operating system. Apple's guidance that Software Update can use less storage than other routes matters most in the second case.

Free disk space. An installer needs room for itself and for the work of installing. A drive that is nearly full slows the process and can stop it, which turns a booked window into a longer unbooked one.

Drive and machine generation. Modern Apple silicon Macs with fast internal storage move through the install phase considerably quicker than older machines with slower drives. Nothing about the software changes this.

Encryption and account setup. A machine with full disk encryption and multiple accounts has more to do after the restart than a single account machine.

None of these produce a number that can be published, but together they mean the estimate for any specific Mac is knowable in advance. The one thing that should not be assumed is that a previous upgrade's timing predicts the next one, because installer sizes change with each release.

The routes Apple documents

There is more than one way to get there, and the choice changes both the time and the risk.

Software Update in System Settings is the route Apple describes as fastest and easiest, and it only offers software compatible with the machine. For the current release this is effectively the main path: Apple's own download page lists macOS Tahoe 26 as available through Software Update or Terminal, without an App Store link of the kind older versions have.

The Terminal route uses softwareupdate --fetch-full-installer with a version number, and softwareupdate --list-full-installers shows which versions the machine can take. This produces a full installer in the Applications folder, which is useful when the same version is going onto several machines.

macOS Recovery is for reinstalling rather than upgrading, and it is the route when Software Update has already failed or the Mac will not start up properly. It takes longer because it downloads what it needs from Apple during the process.

A bootable installer is the option for installing onto multiple computers without downloading each time. It costs setup effort once and saves the download on every machine after that.

For a single Mac being upgraded once, Software Update is the route with the fewest steps and the fewest ways to go wrong. The others exist for cases that are genuinely different.

The part that runs after the progress bar

The install finishing is not the end of the window, and this is where most of the unbudgeted time goes.

The first login after a major upgrade brings a sequence of setup prompts. Background indexing runs, which makes search unreliable and the machine warm for a while. Applications that need system permissions have to be granted them again, and the ones that matter most are the ones used in meetings. Screen recording permission, microphone access, and camera access all sit behind prompts that only appear the first time an app asks after the upgrade.

The practical consequence is specific. A video call joined immediately after an upgrade is a call where screen sharing fails, and the fix involves a settings pane and often a restart of the conferencing app. That is five to ten minutes of everyone else waiting, and it happens at exactly the moment when it is most visible.

Anything that syncs also has work to do. Mail re downloads, cloud storage revalidates, and a calendar that reads several accounts needs to reconnect each of them. None of that is difficult, but it is not instant, and it happens while the machine is already busy indexing.

The rule that follows is to book a buffer after the install of at least the same length as the install itself, and to make sure nothing in that buffer requires screen sharing.

The two steps that belong before the window

Both of these take time, and neither belongs inside the booked block.

The first is checking compatibility. Apple publishes which Macs each macOS version supports, and Software Update only offers versions the machine can run, which makes it a compatibility check in itself. If Software Update reports that the Mac is up to date, no newer version is available for it. That single sentence resolves a large share of the cases where someone plans an upgrade that was never going to happen.

The second is the backup, and it is the one most often skipped because it feels like it belongs to a different task. A full backup on an external drive takes as long as the amount of data and the speed of the drive dictate, which for a first backup can be considerably longer than the upgrade. Running it inside the upgrade window is how a one hour plan becomes a four hour one. Running it the night before, alongside the installer download, costs nothing in working time.

There is a third preparation step worth listing even though it is quick: making sure the Mac will stay powered and connected. A laptop upgrading on battery in a place with intermittent wifi is the scenario where an interrupted install turns into a recovery job. Plugged in, on a stable connection, unattended is the intended condition.

Once those three are handled, what remains to be booked is genuinely just the install phase and its buffer, which is a window that can be estimated and defended rather than a vague afternoon.

Booking it so it does not collide

Treating the upgrade as a calendar event rather than an intention is what makes the difference, and it takes three decisions.

Pick the end of a working block, not the middle. The install phase wants a window with nothing after it that depends on the Mac. Last thing before lunch works if lunch is real. Last thing before a commute works better, because the machine can finish alone.

Enter it as busy, with the buffer included. An hour marked as busy stops scheduling tools from filling it, which is the entire reason to enter it. A window that exists only as a plan gets a meeting dropped into it by someone else within the day. Entering it as a sentence rather than through a form takes seconds, which matters because the events most likely to be skipped are the ones that feel like admin. The Entering events page covers that.

Check what is either side of it. Specifically, check for anything requiring travel immediately after, because a machine that needs another ten minutes cannot be closed and carried. Attaching travel time to the next event makes that visible on the grid rather than discovered at the door, and the Travel time page shows how that is entered.

One more habit is worth adopting. Start the download the night before, so the booked window contains only the phases that cannot be moved. The download is the largest and least predictable part, and it is also the only part that can happen while nobody is watching.

What to change first

Split the upgrade into two calendar entries instead of one. Put the download on the evening before, where its length does not matter, and book the install as a real busy block at the end of a working stretch, with a buffer after it that contains no calls. Back up before either. If the reason this keeps getting postponed is that no block on the calendar is ever long enough to be safe, that is a scheduling problem rather than an upgrade problem, and Caltimate is built for putting the blocks in quickly enough that they actually get entered.