Remove Old Unity Editor Versions on Mac Without Losing Projects

Use Unity Hub’s Installs panel to uninstall an unused Editor version after checking which projects need it. Removing the Hub application itself is not a reliable way to reclaim every Editor installation. Likewise, deleting a project from a recent-projects list does not prove its Editor is unused.

This cleanup makes sense after retiring a course, prototype, or client project. It is less useful when you will immediately reinstall the same version to fix or ship that project.

Make a short version inventory

Open Hub and compare its Projects and Installs panels. Write down the full version used by each important project. Include archived projects outside Hub’s current list and automated build scripts that may launch an Editor by its full path.

For each installed version, answer three questions: what needs it, when was that project last used, and could you restore the exact toolchain if necessary? A newer installed Editor is not evidence that an older project can be upgraded without work.

Uninstall through Hub where supported

1. Save and close projects running in the version you plan to remove.
2. In Hub, open Installs and identify the exact version.
3. Use its management menu and choose Uninstall for a Hub-installed Editor.
4. Read the confirmation, let removal finish, and recheck the installation location.

Unity’s Editor installation documentation explains an important distinction: a manually installed Editor may offer Remove, which removes the listing but leaves files on disk. Use Reveal in Finder to inspect that installation’s path rather than guessing which folder to delete.

Protect the project and the ability to reopen it

The Editor installation and your project directory are different things. Preserve your project source and backup regardless of whether you keep the toolchain installed. Our Unity project folder guide explains why source folders and generated data need separate treatment.

For a client handoff, record required modules alongside the version. A reinstall that opens the scene but lacks the platform support needed to build it is an incomplete restoration. Keep this record with the project archive rather than only in a note on the Mac you are cleaning.

If disk space does not change much

Confirm whether you selected Uninstall or Remove. Then inspect the known installation location and any other versions remaining in Installs. Do not assume two similar version names are duplicates; a patch difference may be intentional for compatibility.

Next check project folders independently. Deleting an Editor does not establish that imported project data or downloaded assets were removed. The broader Unity cache guide can help locate those categories, but treat each as a separate cleanup decision.

Use a retention rule that matches your work

A practical policy is to keep versions needed for current development and support commitments, and record reinstall information for retired work. Review this list when a project closes instead of deleting older installations purely because of their age.

Unity’s Editor management overview provides the supported route for maintaining multiple versions and modules. Before a deadline or an offline trip, postpone toolchain cleanup unless space is genuinely blocking the task. The cheapest space to recover is usually storage you can remove without creating an immediate rebuild or download obligation.