When the Unity Package Manager fetches UPM packagesA Package managed by the Unity Package Manager. Refer to Packages.
See in Glossary, it stores the package contents and metadata in a global cache. This makes reusing and sharing packages more efficient, and allows you to install and update stored packages even when offline.
Note: Storing packages in the global cache applies to UPM packages fetched from a registry. Packages in the UPM format that come from 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 are also stored in the global cache. However, asset packagesA collection of files and data from Unity projects, or elements of projects, which are compressed and stored in one file, similar to Zip files, with the .unitypackage
extension. Asset packages are a handy way of sharing and re-using Unity projects and collections of assets. More info
See in Glossary in the .unitypackage
format that come from the Asset Store aren’t stored in the global cache. The Package Manager stores asset packages in a separate cache. For more information, refer to Asset Store packages.
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 | Example |
---|---|---|
Windows (user account) | %LOCALAPPDATA%\Unity\cache\upm |
C:\Users\yourname\AppData\Local\Unity\cache\upm |
Windows (system user account) | %ALLUSERSPROFILE%\Unity\cache\upm |
C:\ProgramData\Unity\cache\upm |
macOS | $HOME/Library/Caches/Unity/upm |
/Users/yourname/Library/Caches/Unity/upm |
Linux | $HOME/.cache/Unity/upm |
/home/yourname/.cache/Unity/upm |
Tip: You can override the location of this root directory. Refer to Customize the global cache for more information.
The Package Manager global cache uses subsidiary caches, each serving a different purpose. The Package Manager stores these subsidiary caches in subfolders under the folder of the global cache:
Subfolder | Description |
---|---|
db |
Registry data cache used for storing package content and metadata. |
git-lfs |
Contains downloaded Git Large File Storage (LFS) files, if you’ve enabled Git LFS. |
packages (obsolete) |
If you’ve created projects with Unity Editor 2023.2, this subfolder might exist. However, starting with Unity 6, the Package Manager doesn’t use this subfolder. |
Inside each of these subfolders, each registry has its own path so that packages hosted on different registries aren’t mixed up.
Tip: You can override the location of these folders. Refer to Customize the global cache for more information.
Starting with version 2023.2.0f1 of the Unity Editor, the size of the registry data cache (the db
subfolder) is limited to 10 gigabytes (GB). When that limit is reached, the Package Manager prunes the registry data cache by evicting the least recently used content (based on oldest date a package was installed into a project). In other words, the first packages the Package Manager evicts are the ones you added to a project the longest time ago. However, although the Package Manager evicts these packages from the cache, they remain in any projects where you installed them. The next time you add these packages to a different project, the Package Manager will fetch them from the appropriate registry, rather than from your cache.
You can override the size of the registry data cache limit. For information, refer to Customize the global cache.
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 can’t download and save the package metadata and contents in the cache.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.
When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.
More information
These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partners. They may be used by those companies to build a profile of your interests and show you relevant adverts on other sites. They do not store directly personal information, but are based on uniquely identifying your browser and internet device. If you do not allow these cookies, you will experience less targeted advertising. Some 3rd party video providers do not allow video views without targeting cookies. If you are experiencing difficulty viewing a video, you will need to set your cookie preferences for targeting to yes if you wish to view videos from these providers. Unity does not control this.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms. You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information.