Customize the global cache location

The Package Manager maintains a global cache for registry data and uncompressed packages. The global cache includes subsidiary caches, each serving a different purpose. The Package Manager stores the global caches in a default location, which you can override.

You might want to override the cache location for several reasons:

• You want to save space on your internal drive.
• You want to store the cache on a shared drive, which is accessible to others.
• You want to store the cache in a folder that’s not in a system directory.

By default, the Package Manager uses the following folder structure for the global cache:

<global-cache-root>
  ├── npm
  │   └── <registry data (package metadata and tarballs)>
  ├── packages
  │   └── <uncompressed contents of package tarballs>
  └── git-lfs (if enabled)
       └── <downloaded Git LFS files>

For information on the default location of the global cache root, see global cache.

Note: The Package Manager maintains separate caches for the global cache and the Asset StoreA growing library of free and commercial assets created by Unity and members of the community. Offers a wide variety of assets, from textures, models and animations to whole project examples, tutorials and Editor extensions. More info
See in Glossary package cache. For information on overriding the default location for the Asset Store cache, see Customize the Asset Store cache location.

To override the default location of the global cache root, you can use the following methods:

• The Preferences window is the recommended method because of its ease and permanence. When you change the package cache location using this method, Unity stores the preference for the current session and future sessions.
  • Note: Using the Preferences window sets the cacheRoot property in a user configuration file. If you want to set the configuration file manually, see Using a configuration file.
• The environment variable method isn’t permanent, but advanced users might find it preferable in specific use cases.

Important notes before you begin

• Regardless of the method you choose, changing the cache location tells the Package Manager to use that location going forward. Existing packages that Package Manager stored in the original location remain in that folder structure.
• You can use environment variables to override the location of the global cache root or its subsidiary caches (registry data cache, uncompressed packages cache, and the Git LFS cache). However, environment variables and configuration file properties aren’t equivalent, so using different methods to configure settings can produce unexpected results.
• There are several factors that affect how setting several values with different methods work together:
  • If you used the environment variable method to change the cache location, then you can’t use the Preferences window to change the location.
  • When you use a user configuration file, the change is applied to the current user account.
  • If you set different values for the global cache root with both the UPM_CACHE_ROOT environment variable and the cacheRoot property, Package Manager uses the location in the UPM_CACHE_ROOT environment variable.
  • If you set an environment variable for the registry data cache (UPM_NPM_CACHE_PATH), the uncompressed packages cache (UPM_CACHE_PATH), or the Git LFS cache (UPM_GIT_LFS_CACHE_PATH), Package Manager uses the location specified by the environment variable, regardless of where the global cache root is.
  • If you enable the Git LFS cache (UPM_ENABLE_GIT_LFS_CACHE) without explicitly setting its path (UPM_GIT_LFS_CACHE_PATH), Package Manager uses the git-lfs folder under the global cache root as its location.

Using the Preferences window

To use the Preferences window to override the default location of the global cache, follow these steps.

1. Use one of the following methods to open the Preferences window:

   • Open the Unity menu (macOS) or the Edit menu (Windows and Linux) and select Preferences.
   • Open the Package Manager window, open the Advanced menu, and select Preferences.

2. Select the Package Manager category.

3. Under Packages, open the menu beside Cache Location .

4. Choose Change Location.

5. Choose a new location for the global cache.

Using a configuration file

You can manually edit the same configuration file that the Preferences window sets to override the location of the global cache root:

1. Locate the .upmconfig.toml user configuration file. To find the file location, see Configuration files. If the file doesn’t exist, create an empty text file.

2. Add the cacheRoot key and set its value as an absolute path to a custom location. Important: When setting Windows paths in TOML files, use forward slashes (/) or double backslashes (\\). Don’t use single backslashes (\) because they’re special characters which mark escape sequences and can cause TOML parsing errors.

   Windows example

   cacheRoot = "E:\\Unity\\cache"
   

   macOS and Linux example

   cacheRoot = "/dev/external/shared/Unity/cache"
   

You don’t need to restart the Unity Editor or the Hub after setting the cacheRoot key for the change to take effect.

Using environment variables

In scenarios that involve automation or continuous integration, it’s less practical and more error prone to configure settings in a configuration file or a preferences window. In such scenarios, you might consider using environment variables to configure settings for the global cache and its subsidiary caches. The following environment variables are available:

Important: Follow these guidelines when you use this method:

• Close the Unity Editor and Unity Hub if they’re already running before setting environment variables.
• Launch the Unity Editor or Unity Hub from the same command prompt or terminal session where you set the environment variables.
• Any environment variables you set in the table above must be set every time you launch Unity.

For information on setting environment variables, refer to the documentation for your operating system. For an introduction to environment variables, see https://en.wikipedia.org/wiki/Environment_variable.

• Setting the global cache root now supported in Package Manager configuration files in Unity 2021.2 NewIn20212