A package contains features to fit the various needs of your project. This can include any core Unity features included during the Unity Editor installation, or other packages that you can install as needed.
Unity’s Package Manager has several interfaces you can use to get packages and manage them.
| Topic | Description |
|---|---|
| Get started with packages | Learn about packages and get an introduction to Unity’s Package Manager and its core concepts. |
| Dependencies | Learn about the different types of dependencies and how Unity’s Package Manager resolves conflicts. |
| The Package Manager window | Get a tour of the Package Manager window. |
| Package management with the Package Manager window | Learn how to manage packages by using the Package Manager window. |
| Package management with the scripting API | Learn how to manage packages by using C# scriptsA piece of code that allows you to create your own Components, trigger game events, modify Component properties over time and respond to user input in any way you like. More info See in Glossary. |
| Package management with the project manifest file | Learn how to manage packages by editing a JSON file. |
| Package inspection | Learn how to get details about a package. |
| 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 |
View the lists of packages you can install. |
| Feature setsA feature set is a collection of related packages that you can use to achieve specific results in the Unity Editor. You can manage feature sets directly in Unity’s Package Manager. More info See in Glossary |
Learn about bundles of related packages that you can use for a specific task, such as building environments or optimizing specific platforms, or to find all the development tools you need in one place. Also view a list of feature sets that are available in this version of the Editor. |
Git dependenciesThe Package Manager retrieves Git dependencies from a Git repository directly rather than from a package registry. Git dependencies use a Git URL reference instead of a version, and there’s no guarantee about the package quality, stability, validity, or even whether the version stated in its package.json file respects Semantic Versioning rules with regards to officially published releases of this package. More infoSee in Glossary |
Learn about dependencies that arise from fetching a package from a Git repository. Discover the protocols and extended syntax you can use to fetch packages from a Git repository. |
| Package Manager caches | Learn about the different caches stored locally, and how to customize them. |
| Scoped registries | Learn how to user or host a custom package registry server. |
| Package Manager configuration | Configure your network, set cache locations, or configure authentication for private repositories. |
| Create custom packages | Build and share your own packages, by learning about custom package requirements, working with package manifestEach package has a manifest, which provides information about the package to the Package Manager. The manifest contains information such as the name of the package, its version, a description for users, dependencies on other packages (if any), and other details. More info See in Glossary files, and more. |
| Package Manager troubleshooting | Get information for troubleshooting Package Manager issues. |