Version: 2021.2
Installing a feature set
Installing a package from a local folder

Installing from a registry

Note: When you install a package through the Package Manager window, the Package Manager evaluates other packages and their dependenciesIn the context of the Package Manager, a dependency is a specific package version (expressed in the form package_name@package_version) that a project or another package requires in order to work. Projects and packages use the dependencies attribute in their manifests to define the set of packages they require. For projects, these are considered direct dependencies; for packages, these are indirect, or transitive, dependencies. More info
See in Glossary
to see if there are any version conflicts with the version you selected. If it detects any conflicts or restrictions, it installs whatever version resolves these issues. For more information, see Dependency and resolution.

Use the same process for installing a package from either the Unity registry or any scoped registry defined in your project. The only difference is what you choose from the Packages drop-down menu:

  1. Open the Package Manager window and select Unity Registry from the PackagesPackages are collections of assets to be shared and re-used in Unity. The Unity Package Manager (UPM) can display, add, and remove packages from your project. These packages are native to the Unity Package Manager and provide a fundamental method of delivering Unity functionality. However, the Unity Package Manager can also display Asset Store packages that you downloaded from the Asset Store. More info
    See in Glossary
    drop-down menu. If you want to install a package from a scoped registry, choose My Registries instead.

    Change the context to Unity Registry
    Change the context to Unity Registry

    Note: If you haven’t defined any scoped registries for this project, My Registries does not appear in the drop-down menu.

  2. Select the package you want to install from the list of packages. The package information appears in the details view.

    Note: By default, the Package Manager does not display preview packages. If you don’t see the package in the list of packages, it may be a preview packageA preview package is in development and not yet ready for production. A package in preview might be at any stage of development, from the initial stages to near completion.
    See in Glossary
    . Open the Package Manager project settingsA broad collection of settings which allow you to configure how Physics, Audio, Networking, Graphics, Input and many other areas of your project behave. More info
    See in Glossary
    and make sure the Enable Preview Packages project setting is enabled.

  3. Select the version to install. For more information on available versions, see Finding a specific version.

  4. Click the Install button.

Install button in the bottom right corner of the details view

When the progress bar finishes, the new package is ready to use.


Installing a feature set
Installing a package from a local folder