You can use the search box at the top of the Package Manager window to find any packages that match the text you enter. The Package Manager updates the package list as you enter text, displaying every package within the current context that matches. For example, if you enter web in the search box, the list displays different results depending on whether you choose the Built-in packages list context or the Unity Registry list context:
Your search text could match the beginning, middle, or end of the package’s name. The Package Manager updates the list of packages dynamically.
Note: You can search for either Unity packages or 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 packages. The list context you choose defines where the Package Manager searches:
|List context:||Where the Package Manager searches:|
|Unity Registry||The list of packages on the Unity registry|
|My Registries||Any scoped registry defined for your project|
|In Project||The package cache and the
|My Assets||The list of Asset Store packages available with your Unity account|
|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
|The list of built-in packages on the Unity registry|
You can search for either the display name as it appears in the Package Manager window or, for Unity packages, the registered package name that begins with com.unity.
Your search text could match the beginning, middle, or end of the package’s name.
Enter the version number in version order (MAJOR.MINOR.PATCH). For example, typing 1 returns all packages with versions beginning with 1 (for example, 1.0.0, 1.3.2, 1.10.1, and 10.0.0 all match but not 0.1.0).