How to Uninstall Unity and Unity Hub on Your Mac
AskClean Team · Updated 2026-09-29
To uninstall Unity on your Mac, verify your project backups and check the license return procedure first. Complete any step that needs an installed Editor before removing it. Uninstall Editors through Hub, finish any Hub license steps, then remove Hub and review leftover caches. Keep your project folders and dependencies.
Before uninstalling: decide what you want to keep
Unity is not one app bundle. A typical installation includes Unity Hub, one or more Editor versions and platform modules, project folders, downloaded packages, and shared build caches. Removing only Unity Hub can therefore leave the much larger Editor installations and caches behind.
Save your work. In Unity Hub's Projects list, note where each project is stored. Back up Assets, Packages, ProjectSettings, and any local dependencies outside those folders. If you use version control, confirm that untracked assets and large files are included in a usable backup; committing tracked files alone may not preserve everything.
Before uninstalling your last compatible Editor, test the backup in a separate working copy. Open it with the expected Editor version, check that needed packages are available, and run a representative scene or build. Confirm that .meta files and dependencies outside the project were preserved. Then close the test project and quit the Editor.
If you are retiring the Mac or freeing an activation, check the return procedure for your license type before uninstalling anything. Some procedures need an installed Editor; Unity Personal uses Hub sign-out. Plan the sequence so the required tools remain available until the license step is complete.
A complete app uninstall does not require deleting your Unity projects. Treat project folders as personal work unless you have deliberately archived and verified them elsewhere.
Check when to return your license
For Unity Personal, finish the Editor removal steps in Hub, then sign out before deleting Hub itself. For another license type, follow Unity's return procedure while the tools it requires are still installed. If you use the documented Editor command-line method, complete it before deleting that Editor.
For an organization-managed license, confirm any seat reassignment with your organization as well. Returning a machine activation and changing who has an assigned seat are different operations. Deleting a local license file is not a substitute for either one.
Uninstall every Unity Editor version through the Hub
Open Unity Hub, select Installs, and review every Editor version. Use the Manage menu for a version installed by the Hub, then select Uninstall. This removes that Editor and its installed modules together. Repeat for versions you no longer need.
There is an important exception: if you downloaded an Editor manually and later used Locate to add it to the Hub, the menu shows Remove instead. Remove only unlinks that Editor from the Hub; Unity’s documentation says its files remain on disk. Use Reveal in Finder first, remove the Hub entry, and then move that specific Editor folder to the Trash after verifying the path.
The default Hub-managed macOS location is under /Applications/Unity/Hub/Editor, but the Hub lets you change installation locations. Use the path displayed in Installs rather than assuming every Editor is in the default folder.
Remove Unity Hub after uninstalling the Editors
Check that your applicable license steps are complete; for Unity Personal, sign out of Hub now if you have not already done so. Quit Unity Hub completely, open Applications in Finder, and move Unity Hub to the Trash. Removing the Editors first lets you use Hub to locate and uninstall the versions it manages.
If Unity Hub launches at login, open System Settings > General > Login Items & Extensions and remove or disable its login entry. Leave items you moved with Finder in the Trash until you have checked your backups and selections. This recovery option applies to those Finder moves; do not assume Hub's Uninstall command puts files in the Trash.
Even after you remove the applications from their install locations, caches can remain in your user Library. You may want to keep them if you plan to reinstall Unity soon. If you are leaving Unity entirely, review them one category at a time.
Review leftover package and build caches
In Finder, choose Go > Go to Folder to inspect the paths below. Measure each folder and confirm which Unity installation uses it. Before removing a cache, quit Unity and any build jobs that use it, and check the cleanup instructions for your Editor version. Downloaded packages may need to be fetched again, which requires continued access to their source.
The Package Manager global cache is at ~/Library/Caches/Unity/upm. Asset Store .unitypackage downloads use a separate cache at ~/Library/Unity/Asset Store-5.x. The machine-level Bee build cache defaults to ~/Library/Unity/cache/bee. Unity can relocate the package caches, so users who changed their cache settings should verify the configured location instead of relying only on defaults.
Unity's build documentation warns that manually changing cache files can cause build problems and that paths may change between releases. Prefer Unity's documented cache controls or clean-build workflow where available. A path in this list is a place to inspect, not blanket permission to delete it. Leave a cache in place if you cannot establish a supported cleanup method and how required data would be restored.
Optional: reclaim cache space inside old projects
A Unity project’s Library folder can be much larger than its source because it holds imported assets, indexes, shaders, and build caches. Temp contains transient work. If you are keeping a project active, the lowest-risk choice is to leave these folders alone and use Unity’s own clean-build workflow when troubleshooting.
For an archived project, you can omit Library and Temp only after verifying that the backup contains Assets, Packages, ProjectSettings, and every required dependency. Unity will need to reimport assets and regenerate caches when you reopen it; later builds may also take longer. Test restoring the project with a compatible Editor first, including access to private packages. Missing source files or dependencies cannot be recovered by rebuilding Library.
Never delete Assets, Packages, or ProjectSettings as part of uninstall cleanup. Assets includes code, scenes, media, and .meta identity files; Packages records dependencies and can include embedded package source; ProjectSettings contains the project configuration needed to reproduce the project.
If a package is referenced from a local folder outside the project, make sure that folder is included in your backup. Recreating Library cannot restore a missing local dependency.
Verify the uninstall and reclaimed space
Check Unity Hub’s former install locations, Applications, and the cache paths you reviewed. Search by exact folder name only as a final check; a folder named Unity inside one of your projects can contain work, not an application leftover.
Confirm that the backup you tested before uninstalling is still accessible and that any license return or seat reassignment is complete. Review all items in the Trash before emptying it, including files unrelated to Unity. Emptying it permanently removes everything it contains.
Compare available disk space as well as the folder sizes you recorded before cleanup. Files moved to the Trash still occupy space until they are removed from it. The Storage summary in System Settings may take time to update, so do not repeat the cleanup just because its chart has not changed yet.
What to remove and what to keep
Use these locations to inspect your installation. Check the supported cleanup method and your backups before removing anything.
| Item | Default location or manager | What removal changes |
|---|---|---|
| Unity Editor and modules | Unity Hub > Installs | Reinstallable; projects remain, but they need a compatible Editor to open. |
| Package Manager cache | ~/Library/Caches/Unity/upm | Removed packages must be downloaded again; confirm continued access to public and private registries. |
| Asset Store package cache | ~/Library/Unity/Asset Store-5.x | Removed .unitypackage downloads may need to be fetched again; verify that needed assets remain available. |
| Machine-level Bee cache | ~/Library/Unity/cache/bee | Use a supported cleanup method for your Unity version. Rebuilding cached artifacts can slow later builds. |
| Project Library and Temp | Inside each project | Expect asset reimport and cache regeneration; verify a restorable project backup before omitting them. |
| Assets, Packages, ProjectSettings | Inside each project | Keep: these contain project work, dependencies, and configuration. |
The cache paths were checked against Unity's documentation on 2026-09-29. Custom locations and Editor versions can differ, so confirm the paths used by your installation. This review did not uninstall Unity or delete a real project's cache.
FAQ
Does uninstalling Unity Hub delete my projects?
No. Unity Hub tracks and opens projects, but project folders are separate. Removing Hub or an Editor should not delete them. Still, record every project path and verify a backup before uninstalling.
Why is Unity still using disk space after I deleted Unity Hub?
The Hub is only the manager. Installed Editor versions, platform modules, Package Manager downloads, Asset Store packages, Bee build caches, and per-project Library folders can all remain. Inspect those categories separately.
Is it safe to delete a Unity project's Library folder?
Unity generates Library from project assets and dependencies. Removing it means those assets must be reimported and caches regenerated. Keep it on an active project unless a documented troubleshooting step calls for removal. Before omitting it from an archive, test that the project can be restored from its source, configuration, and dependencies.
Can I delete the entire ~/Library/Unity folder?
Avoid deleting it wholesale. It can contain Asset Store downloads, build caches, and other Unity data. Inspect subfolders individually and follow the documented cleanup method for each one; do not assume every file can be downloaded or rebuilt.
What is the difference between Remove and Uninstall in Unity Hub?
Uninstall applies to Editors installed through the Hub and removes their files. Remove applies to an Editor you manually downloaded and located in the Hub; it removes the Hub entry but leaves the Editor files on disk.
Should I return my Unity license before uninstalling?
Check the procedure before you start. Unity Personal users can remove the Editors first, then sign out before deleting Hub. If another license's return method needs the Editor, complete it before uninstalling that Editor. Handle any organization seat reassignment separately; deleting license files does not release or reassign a seat.
Sources