When you “remove” a UPM packageA Package managed by the Unity Package Manager. Refer to Packages.
See in Glossary from your project, the Package Manager is actually removing the project’s direct dependencyA direct dependency occurs when your project “requests” a specific package version. To create a direct dependency, you add that package and version to the dependencies property in your project manifest (expressed in the form package_name@package_version
). More info
See in Glossary from your project manifestEach Unity project has a project manifest, which acts as an entry point for the Package Manager. This file must be available in the <project>/Packages
directory. The Package Manager uses it to configure many things, including a list of dependencies for that project, as well as any package repository to query for packages. More info
See in Glossary. The result of removing the direct dependency varies, based on the dependencies for the package you are removing:
alembic@1.0.7
package which in turn depends on the timeline@1.0.0
package, then your project has an direct dependency on Alembic and an indirect dependency on Timeline. More infoMake sure you understand these important notes before you begin:
Use this procedure to remove a package only if you added it to the current project by installing it, such as (but not limited to) Install a feature set, Install a UPM package from a registry, Install a UPM package from Asset Store, and installing custom packages. Don’t use this procedure to try to:
.unitypackage
extension. Asset packages are a handy way of sharing and re-using Unity projects and collections of assets. More infoIf you use this procedure to remove a UPM package that you installed from a registry or installed from the Asset Store, the operation removes the package from the current project. It doesn’t remove the same package that might exist in other projects. It also doesn’t remove the package from the global cache; this action isn’t supported by the Package Manager, and manually manipulating the global cache is discouraged.
If you use this procedure to remove a package that you embedded in your project, the Package Manager deletes the entire package folder from your computer. However, removing packages installed from any other source (including local packages) removes only the reference to the package in the manifest but leaves the package itself and its contents intact.
To remove an installed package:
Open the Package Manager window and select In Project from the navigation panel.
Select the package you want to remove from the list of packages. The details panel now displays that package’s information.
Click Remove.
If this button isn’t displayed, you might be viewing the My Assets list. Refer to Before you begin.
If this button is disabled, you can’t remove this package. Hover over the button to find out why you can’t remove the package. For more information, refer to Locked and non-removable packages.
When the progress bar finishes, the package disappears from the list.
If you want to restore a removed UPM package, follow the instructions to install a UPM package from a registry or install a UPM package from the Asset Store.
Note: You can remove multiple packages with one click by using the multiple select feature. For more information, refer to Perform an action on multiple packages or feature sets.
You can remove packages only if they’re not required by another package or a feature set. The Package Manager enforces this by disabling the Remove button for all required packages.
Required by | Description |
---|---|
A feature set | If a feature set requires the package, it displays a lock icon (![]() However, even if you click the Unlock button, you still can’t remove the package from your project until you remove all feature sets that require it. Unlocking the package lets you request a different version for your project, but it still doesn’t let you remove it. |
Another package | If one or more packages require the selected package, the Remove button is disabled. You can find the name of the package that has the dependency from the Dependencies tab in the details panel. If you don’t need the other packages, you can remove them and the Package Manager automatically removes this package too. |
Note: You can unlock multiple packages with one click by using the multiple select feature. For more information, refer to Perform an action on multiple packages or feature sets.
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.