Version: 2021.3
Language : English
List view
Features (detail) view

Details view

The right panel of the Package Manager window displays details for the selected package.

Package details for a Unity Package Manager (UPM) package (left) and an asset package (right)
Package details for a Unity Package Manager (UPM) package (left) and an asset package (right)

These details include the following information:

(A) The display name. For UPM packagesA Package managed by the Unity Package Manager. Refer to Packages.
See in Glossary
, a lock icon () and any labels that apply to the package also might appear after the name.

Note: The lock icon appears when an installed feature set requires the selected package. It prevents you from accidentally changing the version of the package so the feature set continues to work effectively.

(B) The package author or Asset Store package publisher.

(C) The package version and date the package was published to the registry or the Asset Store. If available, the information button might also appear after the version and date information. When you click the information button, Unity displays information about the package (for example, if the package version you requested does not match the version installed).

(D) The name of the package registry. For UPM packages, this is always “Unity”. For scoped package registries, this matches the name property for this scoped registry in the 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
.

(E) For UPM packages, the links to open the package documentation page, the package change log (if available), and the license information. For 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
, the links to open the package’s official page on the Asset Store, and if available, links to the publisher’s website and their support page.

(F) A brief description. By default, Unity displays only the first three lines, but you can click the More link to see the rest of it.

(G) Thumbnails of the marketing images, audio, and video available on the Asset Store for Asset Store packages. Click on the link underneath the thumbnails to open the Asset Store package’s official page on the Asset Store.

(H) Dependency information for UPM packages. By default, this section is hidden, but you can display it by enabling the Show Dependencies project setting.

This section lists dependencies in two directions:

  • Is using: Whether this package depends on another package, and if so, which version. Installed packages display the status of the dependencies after the version number.
  • Used by: Whether another package depends on this one, and if so, which version.

Packages without dependencies display the message “No dependencies”.

(I) For Asset Store packages, the following additional information is available here:

  • The disk space required and the supported versions of Unity.
  • The date you purchased the Asset Store package.
  • The Asset Store package’s release information, including when it was originally released and when the current version was released.
  • Any labels you assigned this Asset Store package.

(J) UPM packages that include sample assets display the samples along with an import button. To import the sample code, click the Import button next to the sample.

(K) Button(s) to unlock, install, update, remove, or disable a UPM package.

(L) Button(s) to download, import, or update an asset package.

Labels (tags)

Some packages display labels (also known as tags) next to the package name or version number. These labels offer information about the source or state of the package:

  • Source label types indicate where the package originates from (for example, whether it comes from a local folder or is downloaded from the package registry).
  • State label types indicate the package’s stage of the development cycle. For example, whether it is custom, an experimental package, or on the release track for a specific Unity version.
  • 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
    labels indicate that the package originated from the Asset Store and may also indicate some special status (for example, deprecated).

Some source labels imply state labels and vice versa (for example, if a package is embedded in your project, then Unity automatically assumes it is a custom package in development, so only the custom label appears in the details view).

The Package Manager window displays the following values:

Tag Type Meaning
Released state Unity officially released this package and fully supports it. The Quality Assurance team has tested this version of the package and guarantees that it works with a specific version of the Editor and all other packages released for that Editor version.
Release Candidate state This version of the package is on track to be fully “released” within the next TECH stage of the current release cycle.
Pre-Release state This version of the package is at an earlier stage of development, but Unity guarantees to release it by the end of the LTS release cycle. It might not have complete documentation, or it might not be fully validated by either the development team or Unity’s Quality Assurance team.
Experimental state These packages are either new packages or contain experimental modifications. Unity does not support Experimental packages because they are in the early stages of development.
Custom state
source
This package is embedded in your project. Most custom package developers start by embedding a new package in their project, which is why the “Custom” label appears.
local source The Package Manager installed this package from a folder or tarball file on your local disk external to your Unity project folder.
git source The Package Manager installed this package in your project directly from a Git repository.
asset store asset This is an asset package that you purchased or downloaded from the Asset Store.
deprecated asset This package is no longer available on the Asset Store unless you have downloaded or purchased it previously. That is, it is no longer discoverable by new customers.

Note: This label applies only to Asset Store packages. Unity packages that have been deprecated never appear in the Unity Editor.

Additional resources

List view
Features (detail) view