A package contains features to fit the various needs of your project. This can include any core Unity features included during the Editor installation, or other packages that you can install as needed.
|View the lists of supported packages for this version of the Unity Editor, and learn about the criteria a package must meet to be in these states.|
|Release candidates||Learn about the criteria a package must meet for being a Release candidate.|
|Core packages||View the list of packages that are bound to this version of the Unity Editor.|
|Built-in packagesBuilt-in packages allow users to toggle Unity features on or off through the Package Manager. Enabling or disabling a package reduces the run-time build size. For example, most projects don’t use the legacy Particle System. By removing the abstracted package of this feature, the related code and resources are not part of the final built product. Typically, these packages contain only the package manifest and are bundled with Unity (rather than available on the package registry).
See in Glossary
|View the list of built-in packages, which you can enable or disable to adjust the runtime build size.|
|Experimental packages||Learn about unsupported packages that are in the early stages of development.|
|Packages by keywords||View a list of packages, which you can locate by keyword.|
|Unity’s Package Manager||Learn about the different ways you can interact with Unity’s Package Manager, to do things like finding and adding or removing packages, resolving package conflicts, and much more.|
|Creating custom packages||Build and share your own packages, by learning about custom package requirements, working with manifest files, and more.|
|Feature sets||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.|