Working with the Package Manager

A package is a container that stores various types of features or Assets, such as:

• Editor tools and libraries, such as a text editor, an animation viewer or test frameworks.
• Runtime tools and libraries like the Physics API or a Graphics pipeline.
• Asset collections, such as Textures or animations.
• Project templates to share common project types with others.

Packages are newer, more tightly integrated versions of Asset packages, able to deliver a wide range of enhancements to Unity through the Package Manager. In the Editor, you can access the Package Manager window through this menu: Window > Package Manager.

How Unity works with packages

When Unity opens a Project, the Unity Package Manager reads the Project manifest (1) to figure out what packages to load in the Project. Then it sends a request (2) to the registry server (3) for each package that appears as a dependency in the manifest. The registry server sends the requested information and data back to the Package Manager (4), which then installs those packages (5) in the Project. Each Project has its own manifest which lists the packages to load as “dependencies” of the Project.

If you want to include a package in your Project, you must update the Project manifest to include it in the list of dependencies. If you want to, you can modify the Project manifest directly, but it is safer and easier to let the Package Manager do that. For more information on using the user interface, see the documentation for the Package Manager window.

• Unity Package Manager added in Unity 2018.1 NewIn20181