Where apps hide your files

Finding Unity's editors and caches

Updated 2026-10-28 · 6 min read

Unity Hub puts each editor version in a folder inside /Applications, and the package caches and logs sit in the hidden Library folder. You can open any of them, see what takes the space, and change where new editors go.

Where the editors are

For editors installed through Unity Hub, the default on macOS is:

/Applications/Unity/Hub/Editor/<version>/Unity.app

Each version gets its own folder named after the version, so a Mac with two editors has two folders there. Unity documents this default in its Hub settings reference, and says changing the setting does not move editors you already installed.

The quickest way in is from the Hub itself. Open Installs, find the version, open its Manage menu and choose Reveal in Finder. From Terminal:

open /Applications/Unity/Hub/Editor

If that folder does not exist, the Hub was pointed somewhere else, or you installed the editor by hand and added it with Locate. In either case Reveal in Finder still takes you to the right place.

Check or change the install location

In the Hub, select Settings in the left navigation, open the Installs section and change Installs location. Do it before installing a new editor, for example to put editors on an external drive. The same section has a Downloads location, which Unity says defaults to the temp directory; installer downloads land there, not in the editor folder.

The Hub also has a command line mode. Unity's Hub CLI page gives this form for a Mac, where -g prints the current install path and -s sets a new one:

/Applications/Unity\ Hub.app/Contents/MacOS/Unity\ Hub -- --headless install-path -g

Unity marks the CLI as experimental, so the Settings window is the safer route. If an install fails with a permissions error, check who owns the folder with ls -ld /Applications/Unity; an account without admin rights, or a folder created by another account, can block it.

What lives where

Unity spreads its data across several places. This table covers the ones people usually go looking for.

What	Path
Editors installed by the Hub	/Applications/Unity/Hub/Editor/<version>/
Hub's own log	~/Library/Application Support/UnityHub/logs/info-log.json
Package Manager cache, Unity 6	~/Library/Caches/Unity/upm
Package Manager cache, Unity 2022.3	~/Library/Unity/cache
Asset Store downloads (.unitypackage)	~/Library/Unity/Asset Store-5.x
Editor log, global	~/Library/Logs/Unity/Editor.log
Editor log, per project	<project>/Logs/Editor.log
Player log of a built game	~/Library/Logs/<Company Name>/<Product Name>/Player.log

The 5.x in Asset Store-5.x is literally part of the folder name, and inside it the sub-folders are grouped by Asset Store publisher. Unity's cache page for Unity 6 says packages from the Asset Store in UPM format go into the upm cache, while classic .unitypackage files use the separate Asset Store folder. Both locations can be overridden, so a team setup may differ.

Where the Editor writes its log depends on the version. The Unity 6.0 manual lists ~/Library/Logs/Unity/Editor.log. The current Unity 6 manual says the Editor writes to Logs/Editor.log inside the open project by default, and uses the global file only if you enable Use Global Editor Log in Preferences or start it with -useGlobalLog. If you cannot find an Editor.log, look in both places.

Project data is separate

Your projects are not inside the editor folder. The Hub's Project location setting, under Settings > Projects, decides where new projects are created; Unity does not publish a default for it, so check the setting in your own Hub. Each project folder holds Assets, Packages and ProjectSettings, which are your real work, plus a Library folder of imported-asset data that Unity regenerates when it is missing. On a big project Library can be many gigabytes, so it is commonly left out of backups and version control, at the cost of a slow reimport on first open.

Freeing space safely

Editors are the biggest items, especially with extra modules such as iOS or Android build support. Remove them from the Hub:

1. Open Installs and find the version.
2. In its Manage menu, choose Uninstall.

Unity's documentation says Uninstall applies to editors installed through the Hub. For an editor you added by hand with Locate, the menu offers Remove, which only takes it off the Hub's list and leaves the files on disk. Delete that editor folder yourself afterwards, in Finder.

The Package Manager cache is safe to clear because Unity downloads packages again when a project needs them. Quit the Hub and every open editor, then move the contents of the cache folder for your Unity version to the Trash in Finder. Do the same for ~/Library/Unity/Asset Store-5.x only if you are happy to download your purchased assets again (they stay in your Asset Store account). To see the sizes first:

du -sh ~/Library/Caches/Unity/upm
du -sh ~/Library/Unity/Asset\ Store-5.x
du -sh /Applications/Unity/Hub/Editor/*

These commands only read. If a path does not exist, du says so, which tells you the folder was never created on your Mac or has been moved.

Moving an editor or setting up a new Mac

Do not drag an editor folder to another drive and expect the Hub to follow. Move it, then use Locate on the Installs page and pick the Unity.app inside, which Unity documents as the way to add an editor that is already on disk. On a new Mac, the cleaner route is to sign in to the Hub and install the versions again, then copy your project folders across.

Why a normal search misses all of this

Spotlight and Finder searches leave out ~/Library, so the caches, logs and Asset Store downloads above never show up in results. The editors are in /Applications, but every version is called Unity.app and sits several levels down inside Unity/Hub/Editor, so a search by name cannot tell them apart.

Finding it again later

Typing Asset Store-5.x or Editor.log into Everywhere lists those folders and every Editor log, including the per-project ones, and a search for Unity.app shows each installed editor with its version folder beside it. Press ⌘↵ to reveal a result in Finder. Projects kept in Documents or Desktop are included once Everywhere has Full Disk Access.

Common questions

Where does Unity Hub install editors on a Mac?

By default in /Applications/Unity/Hub/Editor/<version>/, with Unity.app inside. In the Hub, Installs, then the version's Manage menu, then Reveal in Finder opens the exact folder.

How do I change the Unity editor install location on Mac?

In the Hub, open Settings, then Installs, and change Installs location. Unity says this affects new installs only, so existing editors stay where they are.

Where is the Unity cache on a Mac?

In Unity 6, Package Manager packages are cached in ~/Library/Caches/Unity/upm (older versions such as 2022.3 used ~/Library/Unity/cache). Asset Store .unitypackage downloads are in ~/Library/Unity/Asset Store-5.x.

Where is the Unity Editor.log on macOS?

Older editors write to ~/Library/Logs/Unity/Editor.log. The current Unity 6 manual says the default is Logs/Editor.log inside the project, with the global file used when Use Global Editor Log is on.