|How do you use documentation throughout your workflow? Share your experience with us by taking this survey.|
When the Unity Package Manager downloads package contents and metadata, it stores them in a global cache. This makes re-using and sharing packages more efficient, and allows you to install and update stored packages even when offline.
By default, Unity stores the global cache in a root directory that depends on the operating system (and the user account type on Windows):
|Operating system||Default root directory|
|Windows (non-system user account)||
|Windows (system user account)||
The Package Manager uses two different shared caches, each serving a different purpose. They are stored in subdirectories under the folder location above:
||Stores data obtained from registries using the npm protocol. This includes package metadata and package tarballs.|
||This cache contains the uncompressed contents of package tarballs fetched from a registry.|
Inside each of these subfolders, each registry has its own path so that packages hosted on different registries are not mixed up.
Tip: You can override the location of these folders using environment variables. See Customizing the shared cache location for more information.
The user account running the Unity Editor process must have full write permissions on the root directory and its contents. Without these permissions, the Package Manager cannot download and save the package metadata and contents in the cache.