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 scope 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 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 scope or the All packages scope:
Note: You can search for either Unity packages or Asset packagesA collection of files and data from Unity Projects, or elements of Projects, which are compressed and stored in one file, similar to Zip files, with the
.unitypackage extension. Asset packages are a handy way of sharing and re-using Unity Projects and collections of Assets. More info
See in Glossary. The filter you choose defines where the Package Manager searches:
|Filter setting:||Where the Package Manager searches:|
|All packages||Any package on the Unity Package Manager registry, in a scoped registry, and anywhere in the project, including under the
|In Project||Any package installed or embedded in your current project (including locally installed packages).|
|In Development||Inside the
|My Assets||The list of purchased or downloaded assets for your account (your My Assets page).|
|Built-in packages||Any built-in package.|
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).