Sweepfor Mac

Apps & uninstalling

How to Completely Uninstall Unity Hub and the Unity Editor From Your Mac

Unity Hub installs editors, modules, and platform SDKs that can hit 50GB+. Here's how to remove every Unity file from your Mac cleanly.

8 min read

Unity Hub looks innocent — a 200MB launcher app. The thing it installs is anything but innocent. Each Unity Editor version is 4-8GB, and that’s before you add platform modules. iOS support is 2GB, Android support is 4GB (including the bundled Android SDK and NDK), WebGL is 1GB. A game developer keeping three Unity versions for backward compatibility on three platforms is staring at 40-60GB of Unity-related files.

Removing Unity properly means stripping the Hub, every editor version, every platform module, every project cache, and the bundled JDK/Android SDK/NDK. Here’s how.

What Unity installs

Unity Hub bundle ID: com.unity3d.unityhub. Unity Editor uses version-specific bundle IDs like com.unity3d.UnityEditor5.x. Files spread across:

  • Unity Hub at /Applications/Unity Hub.app/
  • Editor versions at /Applications/Unity/Hub/Editor/<version>/
  • Hub data at ~/Library/Application Support/UnityHub/
  • Editor caches at ~/Library/Application Support/Unity/
  • Asset cache at ~/Library/Unity/
  • Per-version caches at ~/Library/Caches/com.unity3d.UnityEditor5.x/
  • Preferences at ~/Library/Preferences/com.unity3d.UnityEditor5.x.plist and others
  • Android SDK/NDK at ~/Library/Android/ (if installed via Hub)
  • JDK at /Applications/Unity/Hub/Editor/<version>/PlaybackEngines/AndroidPlayer/

The Editor folders inside /Applications/Unity/Hub/Editor/ are the bulk. Each version is its own complete install.

Step 1: Quit Unity Hub and any open Editors

Open Activity Monitor and search “Unity”:

  1. Unity Hub
  2. Unity (the Editor)
  3. UnityShaderCompiler
  4. UnityYamlMerge (if running for source control merges)
  5. UnityHelper

Quit each. If you have an Editor with an open project mid-build, let the build finish or cancel it before quitting.

Step 2: Use Unity Hub to remove editor versions first

Before uninstalling Hub itself, use it to cleanly remove each Editor version:

  1. Open Unity Hub
  2. Go to Installs in the sidebar
  3. Click the gear icon next to each editor version
  4. Pick Uninstall

This removes each editor’s app bundle and platform modules. It’s faster than manual deletion because Hub knows exactly what each version installed.

If Hub itself is broken and won’t open, skip this step and handle the editors manually in step 4.

Free up tens of gigabytesAdobe and Microsoft apps leave 5–20GB scattered around. Sweep finds it all. Try Sweep free →

Step 3: Drag Unity Hub to the Trash

Move /Applications/Unity Hub.app/ to the Trash.

Step 4: Remove leftover editor folders

Even after Hub’s uninstaller runs, the editor parent folder may persist:

  • /Applications/Unity/

Inside you might find:

  1. Hub/Editor/<version>/ for any editor Hub didn’t fully clean up
  2. Hub/Editor/<version>/PlaybackEngines/ — platform modules
  3. Hub/Editor/<version>/Editor/Data/ — bundled mono runtime, shader compilers

Delete the entire /Applications/Unity/ folder if you’re nuking all Unity. If you have one editor you want to keep, leave its specific subfolder alone.

Step 5: Remove Unity user data

In Finder, hit Cmd+Shift+G and visit each:

  • ~/Library/Application Support/UnityHub/ — Hub configuration, signed-in account, license cache
  • ~/Library/Application Support/Unity/ — license file, asset store cache, package manager cache
  • ~/Library/Unity/ — global Unity caches and asset metadata
  • ~/Library/Caches/com.unity3d.unityhub/
  • ~/Library/Caches/com.unity3d.UnityEditor5.x/ — there’ll be one folder per editor version
  • ~/Library/Caches/Unity/
  • ~/Library/Preferences/com.unity3d.unityhub.plist
  • ~/Library/Preferences/com.unity3d.UnityEditor5.x.plist — one per version
  • ~/Library/Saved Application State/com.unity3d.unityhub.savedState/
  • ~/Library/Logs/Unity/

The ~/Library/Unity/ folder is interesting — it caches asset metadata across all your Unity projects. Lib cache, package cache, asset hash. On a heavy game dev’s machine this can hit 5-10GB.

Tip: Unity's Library/PackageCache and Library/ScriptAssemblies folders inside each project can hit 1-3GB per project. They're regenerated by Unity from project source. If you're freeing space without uninstalling Unity, deleting Library/ from inactive projects is safe and reclaims space fast — Unity rebuilds the folder when you reopen the project.

Step 6: Android SDK, NDK, and JDK

If you installed Android Build Support, Unity also dropped:

  • ~/Library/Android/sdk/ — Android SDK (3-5GB)
  • ~/Library/Android/ndk/ — NDK (1-3GB)

These are independent of Unity Hub’s uninstaller. Hub may not remove them. Delete manually.

The bundled JDK lives inside each editor version at /Applications/Unity/Hub/Editor/<version>/PlaybackEngines/AndroidPlayer/OpenJDK/. It goes when you delete the editor folder.

If you have other apps that use the Android SDK (Android Studio, React Native, Flutter), don’t delete ~/Library/Android/ — they share it.

Step 7: iOS / Apple build tools

Unity’s iOS build support is bundled inside each editor version at /Applications/Unity/Hub/Editor/<version>/PlaybackEngines/iOSSupport/. It goes with the editor.

If you used Unity to build for iOS, you also have Xcode installed separately — that’s not part of Unity. Xcode lives at /Applications/Xcode.app/ and removes independently.

Step 8: WebGL build cache

Unity caches Emscripten/WebGL build artifacts at:

  • ~/Library/Application Support/Unity/AssetStoreCache/
  • Inside individual project Library/ folders

These are part of step 5’s cleanup.

Skip the manual huntSweep finds every leftover preference, cache, and support file in seconds. Download Sweep free →

Step 9: License files

Unity’s license is stored at:

  • /Library/Application Support/Unity/Unity_lic.ulf — the license file
  • ~/Library/Application Support/Unity/Unity_lic.ulf — user-level fallback

Removing these deactivates Unity. If you’re moving to another machine, sign out through Unity Hub first to release the seat. Manual deletion of the license file without signing out can leave the seat marked as in-use server-side, requiring a manual return through Unity ID.

Step 10: Empty Trash and reboot

A reboot is good practice — Unity’s services may have file handles open until log out. After login, verify Activity Monitor shows nothing Unity-related.

Realistic space recovery

A full Unity uninstall reclaims:

  1. 200MB from Unity Hub
  2. 4-8GB per editor version (you may have 3-4 of these)
  3. 2-4GB Android SDK + NDK
  4. 2GB iOS build support per editor version
  5. 1GB WebGL build support per editor version
  6. 1-5GB from Hub data and caches
  7. 5-10GB from ~/Library/Unity/ global cache

Total: 20-60GB on most game devs’ machines. Those keeping multiple LTS versions plus the latest can hit 80GB+.

This doesn’t include Unity project folders, which live wherever you put them and aren’t touched by uninstalling Unity. Project Library/ folders alone can be many GB each.

Common questions

Will my Unity projects still work? Project files are independent of Unity. They sit on disk. Without Unity installed, you can’t open them. Reinstalling Unity later — same version or different — will reopen the projects (with possible upgrade prompts for newer versions).

Does this remove my Asset Store purchases? No. Asset Store purchases are tied to your Unity ID account. They persist server-side. Local downloaded copies live in ~/Library/Application Support/Unity/AssetStoreCache/ — that’s removed with the cleanup but you can re-download from Asset Store anytime.

What about the Unity Cloud Build agent? Cloud Build runs server-side at Unity’s infrastructure. Nothing to uninstall locally.

Can I keep one editor and remove the others? Yes. Use Hub’s uninstaller (step 2) to remove specific versions. Leave the one you want. Hub keeps the editor it knows about; the rest get removed.

Manual versus automated

Unity is one of the more complex apps to uninstall manually. The version-specific folders, the platform modules, the bundled SDKs, the cache locations across multiple ~/Library/ folders — it’s a lot to track.

Unity Hub’s built-in uninstaller for editor versions is decent. Manual cleanup of ~/Library/ is required after. Sweep handles both — it scans for every Unity-related bundle ID (Hub plus every editor variant), the global Unity cache, and the bundled Android SDK if it’s not used by anything else. For one-off uninstalls, the manual route works in 15-20 minutes. For routine cleanup or when you’ve accumulated multiple editor versions, automation is significantly faster.

Resetting Unity Hub without uninstalling

If Hub is broken (won’t sign in, can’t see installs, license errors):

  1. Quit Hub completely
  2. Delete ~/Library/Application Support/UnityHub/
  3. Relaunch Hub — sign in fresh

This resets Hub without touching installed editors. Editors remain in /Applications/Unity/Hub/Editor/ and Hub re-detects them on launch.

For Editor preferences specifically (not Hub):

  1. Quit the Editor
  2. Delete ~/Library/Preferences/com.unity3d.UnityEditor5.x.plist
  3. Relaunch — Editor rebuilds preferences

This is much faster than full uninstall + reinstall for fixing preference corruption.

← Back to all guides