How to Uninstall Unity on Mac Completely
AskClean Team · Updated 2026-07-29
To uninstall Unity completely on a Mac, remove each Editor version from Unity Hub first, quit and delete the Hub app, then review Unity’s package, Asset Store, and build caches. Keep your project source folders, and return any license before retiring the Mac. This guide separates safe leftovers from files you should preserve.
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.
Close every Unity project and quit both the Editor and Unity Hub. In the Hub Projects list, record the location of every project you want to keep. Back up or commit your work before cleanup, especially the Assets, Packages, and ProjectSettings folders. Those are project source and configuration, not disposable uninstall leftovers.
If you are decommissioning the Mac or moving a paid seat to another machine, return the license before deleting the Editor. Unity Personal uses Hub sign-out to return the license; for other license types, check Hub licensing or your Unity organization before removal.
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.
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 the Editors are gone
Quit Unity Hub completely, open Applications in Finder, and move Unity Hub to the Trash. Removing the Editors first matters: the Hub is the supported interface for identifying install locations and uninstalling versions it manages.
If Unity Hub launches at login, open System Settings > General > Login Items & Extensions and remove or disable its login entry. Do not empty the Trash yet. Keeping the removed app and Editor folders there until verification gives you a short recovery window if you selected the wrong item.
At this point the applications are gone, but caches can remain in your user Library. Whether to delete them depends on whether you are leaving Unity permanently, troubleshooting a damaged install, or just reclaiming space.
Clean Unity package and build caches safely
In Finder, choose Go > Go to Folder and inspect each path below. Measure first, then move only the cache you intend to remove to the Trash. Quit Unity before changing any of them. The cost is usually time and network bandwidth: Unity must download packages or rebuild artifacts when you use them again.
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 current build documentation warns that manually modifying cache files can cause later build problems and that cache locations may change between releases. Delete whole, clearly identified cache categories while Unity is closed; do not pick through unknown files inside them.
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 from a verified archive when Assets, Packages, ProjectSettings, and every required local dependency are safely backed up. Reopening the project then requires a full import and rebuild, which can take a long time. Do not use this as a casual cleanup step on the only copy of a project.
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.
Return the license instead of deleting license files
License cleanup is an account operation, not a filesystem cleanup. For Unity Personal, sign out of Unity Hub before removing it. For serial or organization-managed licenses, use the current Hub license controls or your Unity organization to return or reassign the seat. Unity also documents a command-line return method for supported licenses when Hub is unavailable.
Do not hunt for and delete license files as a substitute for returning a seat. Removing a local file does not reliably tell Unity’s licensing service that the machine no longer uses the activation.
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.
Open a project backup and confirm that Assets, Packages, and ProjectSettings are present. Confirm your license or seat status in the Unity account if you returned one. Only then empty the Trash to make the space available.
If macOS Storage does not update immediately, wait for it to recalculate or restart the Mac. Compare the measured folder sizes from before and after instead of relying on an instant change in the System Data bar.
Unity uninstall safety map
The safest cleanup separates reinstallable applications and caches from the files that define your projects.
| 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 | Registry packages and metadata must be downloaded again when needed. |
| Asset Store package cache | ~/Library/Unity/Asset Store-5.x | Downloaded .unitypackage files must be downloaded again. |
| Machine-level Bee cache | ~/Library/Unity/cache/bee | Shared build artifacts are rebuilt; the next build can take longer. |
| Project Library and Temp | Inside each project | Reimport and rebuild required; archive only after verifying project source. |
| Assets, Packages, ProjectSettings | Inside each project | Keep: these contain project work, dependencies, and configuration. |
Paths shown are current Unity defaults on macOS as of 2026-07-29. Unity supports custom Editor and cache locations, so verify the actual path on your Mac before deleting anything.
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?
Library is generated from project assets and contains imported data and build caches, but deleting it forces a full reimport and can expose missing dependencies or unsaved assumptions. Only omit it from a verified archive when Assets, Packages, ProjectSettings, and required local packages are backed up. Do not modify individual files inside Library while Unity is using the project.
Can I delete the entire ~/Library/Unity folder?
Not as a blind cleanup. It can contain Asset Store downloads, build caches, and other Unity data with different rebuild costs. Inspect named subfolders, measure them, and remove only categories you understand.
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?
Yes if you are decommissioning the Mac or need to free an assigned seat. Unity Personal users return the local license by signing out of Hub; other licenses may use Hub, organization controls, or Unity's documented command-line return method.
Sources