Downgrade a Mac operating system: what to weigh before you start

A downgrade is not an update running backwards. It is three separate operations stacked on top of each other: obtaining an installer for the older version, getting it onto the disk, and putting the data back afterwards. Each one has its own floor, its own prerequisites and its own way of failing, and the order in which they are attempted decides whether the afternoon ends with a working Mac.

Most guides open with the steps. The steps are the easy part. What actually decides the outcome is whether the target version is reachable on this particular Mac at all, and whether there is a backup that predates the upgrade. Both of those can be checked before anything is erased, and one of them cannot be fixed after the fact.

The five routes, and what each one costs

Route	What it needs	What it erases	How far back it reaches
Software Update	Nothing extra	Nothing	Forward only
Reinstall from macOS Recovery	Internet, an account password	Nothing by default	The current version of the most recently installed macOS
Full installer via Terminal	macOS Catalina 10.15 or later	Nothing until it is run	No earlier than the version that came with the Mac
Bootable installer on USB	A 32GB volume, a downloaded installer	The USB volume	Whichever installer was downloaded
Restore in DFU mode	A second Mac on macOS 14 or later, a USB-C data cable	Everything on the Mac	Factory state

Software Update is in the table because it is what most people try first, and it will never offer an older version. Recovery is the second guess and is equally unlikely to help on its own, for a reason set out in the next section. The two middle rows are the ones that actually perform a downgrade. The last row is the recovery path when an attempt leaves the Mac unable to start up, and it is worth reading before starting rather than afterwards.

The floor: what this Mac can reach

Two documented limits govern how far back any Mac can go, and neither can be argued around.

The first is the installer floor. Downloading an older installer through Terminal is possible, but only down to a point fixed by the hardware.

You can use Terminal to download the installer for compatible macOS versions no earlier than the version that came with your Mac, or the closest version still available. Source: support.apple.com, read September 27, 2026

A Mac that shipped with macOS Tahoe 26 cannot be taken back to macOS Sequoia 15, whatever the method. This is the single most common reason a downgrade plan collapses, and it is answerable in one command before anything else happens: softwareupdate --list-full-installers prints the versions currently available for that specific model. If the wanted version is not in the list, the plan needs to change.

The second limit is what Recovery hands over, which is not what most people expect.

On a Mac with Apple silicon: Recovery installs the current version of the most recently installed macOS. If you installed a macOS upgrade and then used Disk Utility to erase the disk, you might get the macOS that you were using before upgrading. Source: support.apple.com, read September 27, 2026

So reinstalling from Recovery normally reinstalls the version being escaped from. The second sentence describes the one case where it does not, and that case involves erasing the disk first, which brings the data question forward rather than deferring it.

On an Intel-based Mac the behaviour splits three ways by keystroke. Command-R gives the current version of the most recently installed macOS. Option-Command-R starts up from Internet Recovery and might give the latest macOS compatible with the machine. Shift-Option-Command-R might give the macOS that came with it, or the closest version still available. Those are different outcomes from the same recovery screen, and picking the wrong one wastes a full download cycle.

Getting and using an older installer

With a target version confirmed as available, the download is one command. Apple's own example is softwareupdate --fetch-full-installer --full-installer-version 26.6.2, and the result lands in the Applications folder as an app named after the version, such as Install macOS Tahoe or Install macOS 27 Golden Gate. If Terminal reports that the update was not found, that version is not available for this Mac and the floor has been reached.

For a downgrade the installer usually has to run from outside the system being replaced, which means a bootable volume. The createinstallmedia tool inside the installer app writes one, and three details in Apple's instructions cause most of the failures. The volume is erased in the process and is reformatted as Mac OS Extended (Journaled). A 32GB flash drive has more than enough room for any current installer. And the volume has to be named MyVolume, because that is the name the published commands expect.

Starting from it differs by architecture. On a Mac with Apple silicon, shut down, connect the drive, then press and hold the power button until startup options load and the bootable installer appears among the volumes. On any other Mac, turn it on and immediately hold the Option key until the volume list appears. On a Mac with the T2 chip that refuses to start from it, Startup Security Utility has to be set to allow booting from external or removable media.

One warning in Apple's instructions deserves to be read twice.

Your Mac must be connected to the internet so that the installer can get firmware and other information specific to this Mac model. If the macOS you're installing is incompatible with your Mac, installation might not complete or your Mac might start up to a circle with a line through it. Source: support.apple.com, read September 27, 2026

That is the state the DFU row in the table exists for. Reviving is the first attempt, because it is faster and does not erase the Mac; restoring erases it and returns it to factory settings. Both run from a DFU window in the Finder on a second Mac running macOS 14 or later, over a USB-C cable that supports data as well as charging, and not a Thunderbolt 3 cable.

The data is the part that cannot be fixed afterwards

This is where downgrades go wrong permanently rather than inconveniently.

Time Machine and Migration Assistant restore content, not an operating system. Apple's description is precise: Migration Assistant can use a Time Machine backup "to restore all of your personal files, including your apps and everything in your user account." Nothing in that sentence installs a version of macOS. The macOS is whatever was installed before the restore begins, which is why the install has to be done first and the restore second.

The consequence is that the backup which matters is one made while the older macOS was still running. A backup taken after the upgrade holds files and apps that were working under the newer system, and restoring it onto an older system puts those apps back without guaranteeing that they still run. Anything that required the newer macOS will not become compatible by being copied backwards.

Recovery does include Restore from Time Machine in its list of utilities alongside Reinstall macOS and Disk Utility, so the two halves can be done in one session. What Recovery cannot do is invent a backup that was never made. Checking that a usable backup exists, and that it is from before the upgrade, is the single check worth doing before anything else on this page.

Three cheaper options than erasing the disk

A full downgrade is a long operation with a real chance of a broken startup disk in the middle. Three lighter options cover a surprising share of the actual reasons people reach for it.

The first is scope. Rolling back a point release within the same major version is a smaller job than crossing a major version, and the two get conflated. Checking which one is actually needed sometimes shrinks the task to nothing.

The second is a second volume. On a Mac with Apple silicon, installing a second operating system on the same machine is supported, with the caveat that ownership has to be handed over deliberately: Apple's platform security documentation notes that when installing a second operating system, "explicit consent is required from the users on the first operating system to hand off Ownership to the users on the second operating system." An older macOS on a separate volume or an external disk gives access to whatever needed the older version without erasing anything.

The third is to fix the thing that caused the complaint. A good share of downgrade attempts trace back to a small number of visible changes rather than to anything structural. The clearest current example is app browsing: Launchpad was replaced in macOS Tahoe 26, which is visible even in Apple's keyboard shortcut list, where Fn-Shift-A is documented as showing "Apps (macOS Tahoe 26 or later) or Launchpad (earlier versions of macOS)." The grid still exists inside Spotlight, with a search field, category filters and a list view. Learning the replacement takes minutes. Erasing the disk to get the old one back takes an evening and a backup.

The same reasoning applies to the top of the screen. A menu bar that suddenly looks crowded or unfamiliar after an upgrade is a layout problem with a layout solution, and a tool that collapses the strip while keeping every icon clickable changes it in seconds. How it compares lays out what those tools do and do not do, and the FAQ covers which macOS versions are supported.

What to weigh, in order

Five checks, in this sequence, decide whether to proceed. Whether a backup exists from before the upgrade. Whether softwareupdate --list-full-installers lists the target version for this model. Whether the apps that matter have builds for the older macOS. Whether a second Mac and a USB-C data cable are available if the install fails. And whether the original complaint is actually about the operating system, or about one changed interface that can be adjusted in place.

Installation itself asks for patience rather than skill. Apple's guidance is to let it finish without sleeping the Mac or closing the lid, and to expect several restarts and an empty screen for minutes at a time. Interrupting it is how a routine downgrade turns into a DFU session.

What to change first

Run the list of available full installers before anything else, because if the target version is not on it, no method on this page will reach it. Then confirm a backup from before the upgrade exists, because that is the only step that cannot be recovered later. If the reason for the downgrade is a menu bar that got busier, Koffret settles that without touching the disk.