How to downgrade macOS, and what you lose

Check whether a downgrade solves the actual problem

If the trigger is one app, driver or extension, first check its supported versions and updates. If the Mac is busy just after an upgrade, the post-update guide explains temporary work and persistent symptoms. Erasing the Mac is a major response to an unidentified problem.

Reinstalling the current macOS without erasing can repair system installation problems while retaining data. Erase All Content and Settings removes your data and apps but keeps the installed OS; it isn't a downgrade.

This guide covers replacing the installed system deliberately. A factory reset for sale is a different objective, covered in the transfer-preparation guide.

Confirm the target macOS supports this exact Mac

Identify the chip and model, then check Apple's compatibility and installer information. A new Mac cannot be assumed to run a version released before its hardware was supported.

For example, a Mac introduced with a later compatible build isn't entitled to install an earlier major release just because both use Apple silicon. The compatibility guide covers the model check; Tahoe versus Sequoia compares those systems.

Apple says its installer-download route is limited to compatible releases no earlier than the version supplied with the Mac, or the closest one still available. Do not erase while relying on an installer you haven't confirmed is available for the target hardware.

Preserve two things before erasing

1. A current backup or separate copy of today's files. Include changes made since the upgrade, local-only documents, exports and the data required by your work apps.
2. A pre-upgrade backup where available. Preserve the earlier environment and app data rather than assuming a newer backup is interchangeable with the older system.

Verify that the files you need are present on the backup or independent storage. A local snapshot on the disk about to be erased is not the same protection as a separate backup.

Don't assume every library or database written by a newer app can be opened by its older version. Check the app developer's supported export and recovery method, particularly for projects you changed after upgrading.

Migration Assistant transfers files, apps, accounts and settings; Apple says it doesn't replace the destination OS. That doesn't guarantee every newer app or data format will work on an older system. Plan a selective recovery of compatible data rather than treating migration as an automatic downgrade tool.

Download the target installer from Apple

Use Apple's macOS download page and choose the compatible target. For a bootable installer, you need the full app in Applications, named Install macOS Tahoe or Install macOS Sequoia, for example.

If it launches after downloading, quit it while preparing. A small disk image or package may need the additional steps Apple documents to produce the full installer. Avoid third-party mirrors and guessed installer commands.

Keep the Mac connected to power. Check that your required apps and their licences have compatible versions available before erasing the currently working installation.

Prepare a bootable installer if needed

Apple says a 32 GB flash drive is more than enough for its installers. Its documented examples name the spare volume MyVolume. After downloading the corresponding full installer, the Tahoe example is:

sudo /Applications/Install\ macOS\ Tahoe.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume

For Sequoia, Apple's command is:

sudo /Applications/Install\ macOS\ Sequoia.app/Contents/Resources/createinstallmedia --volume /Volumes/MyVolume

Use only the command for the installer you actually have. Apple's bootable-installer instructions cover the administrator prompt, erase confirmation, completion and other versions. Enter a password only into your own Terminal when following those instructions.

The installer still needs internet access for firmware and model-specific information. Creating a USB installer doesn't bypass compatibility or make the installation fully offline.

Start the installer, then erase the intended volume

First confirm that the prepared installer appears as a startup choice. On Apple silicon, shut down, connect it directly and hold power until startup options appear. On Intel, hold Option at startup. Select the intended installer.

For Intel T2 Macs, Apple notes that external boot can be restricted by Startup Security Utility. Follow Apple's model-specific instructions if needed, and involve IT on a managed Mac. Don't assume that restriction or a hardware mismatch can be solved by weakening unrelated protections.

Erasure permanently deletes the selected startup data. Once your backups and target installer are ready, use Disk Utility from Recovery or the installer environment, following Apple's Apple silicon erase guide or Intel erase guide. Confirm the internal startup volume, not the USB installer or backup disk.

For modern APFS startup systems, follow the volume-group option when Apple's procedure presents it. Don't erase the whole physical device or unrelated volumes merely because they are visible in the sidebar. If the layout doesn't match the instructions, stop and identify it before deleting.

Install the target version and recover data

Quit Disk Utility and run the target installer on the erased startup volume. If you used Recovery only for erasure and it offers a different OS, return to startup options and use the prepared target installer. Recovery reinstall isn't a universal version picker.

Follow activation, network and setup prompts yourself. Keep power connected, don't close the lid during installation, and allow the documented restarts and blank-screen periods. Once it starts, install compatible updates for the chosen release.

Recover needed files from the protected copies or a compatible backup. Check apps and documents before discarding any backup. A clean installation doesn't recreate local-only data that was never backed up.

An additional volume is a different option

Apple documents installing a compatible macOS on an additional APFS volume or external disk. This can help with temporary testing while keeping another installation available.

Apple also warns that dual boot isn't a long-term guarantee for retaining a significantly earlier macOS: newer security changes can affect that ability. Each installation needs its own compatible updates, and shared files still need protection.

What a clean install loses from Tend

Tend keeps its history locally. Read-only code inspection confirms ~/Library/Application Support/Tend contains the energy history, Battery Coach log and daily battery-health record. Erasing the user data without restoring a suitable backup removes those records.

Reinstalling the app alone doesn't reconstruct that past history. A compatible user-data backup may preserve it, but no cross-version restore was tested here. A normal same-version reinstall without erasing is a different operation from this clean downgrade.

Questions

Related guides

Sources

Sources checked 23 October 2026. These are documented steps and specifications; no repair, installation or performance test was run for this guide.

• Apple, Download compatible macOS installers
• Apple, Bootable installer preparation and startup
• Apple, Erase an Apple silicon startup disk
• Apple, Erase an Intel startup disk
• Apple, Erase All Content and Settings keeps the OS
• Apple, Recovery reinstall and installation behaviour
• Apple, Migration Assistant does not replace macOS
• Apple, Additional macOS volumes and security limitations

Spotted something out of date? Tell us and we'll fix it.