The Unity Manual provides documentation for a specific version of Unity. Each package has its own version, so each package provides documentation for a specific version of that package. For this reason, the package documentation isn’t part of the main Unity Manual documentation; instead, documentation for each package lives on its own micro-site on Unity’s documentation server.
To access the documentation for a specific package, you have two options:
When the package page opens, you can see four links at the top of the page (A), and a breadcrumb trail that indicates the package’s name and version number (B):
To switch back and forth between the Manual documentation, the Scripting API documentation, the Changelog, and the License information for this package, click the corresponding link at the top of the page.
Each version of the Unity Manual documentation provides a list of verified and preview packages, a list of 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, and a list of keywords with links to the matching package documentation which you can use with that version of Unity:
Note: Only packages that are compatible with the version of Unity matching the documentation appear in these lists.
You can expand the entries in the sidebar navigation (A) to access specific information about each package, including the list of compatible versions, a brief description of the package, and any associated keywords. Or you can click the link on the list pages (B) to directly open the most compatible version of that package documentation that matches the documentation version.
If you can’t find the package you want in this list, there might be several reasons:
You might be able to access the documentation through the Package Manager window for packages released in another version of Unity. In the case of private packages, try to contact the developer directly to request access.
You can find out more about a package by viewing its documentation, changelog, or license information.
To access any of these pages, you can click the View documentation, View changelog, or View licenses links from inside the Package Manager window.
To access the documentation for a specific package version:
Open the Package Manager window in Unity.
If you are looking for a preview package, select Show preview packagesA preview package is in development and not yet ready for production. A package in preview might be at any stage of development, from the initial stages to near completion.
See in Glossary from the Advanced drop-down menu.
Select the package you want information for from the list on the left.
Expand the arrow to the left of the package in the list.
A new row appears, displaying the See all versions link.
Click the See all versions link.
A scrollable list appears with all available versions.
Click on another version to select it.
The package details appear in the pane on the right.
Notice the verified tag no longer appears in this example because version 1.4.0 of the TextMesh Pro package is not verified for Unity version 2019.3.
Click the View documentation link to open the documentation for the selected version of the package.
Note: If you are offline when you click the View documentation link and the package is on your computer (that is, embedded or installed from a local folder), the Package Manager opens the first MD file it finds under the
<package-root-folder>/Documentation~ folder in your default MD viewer. If the Package Manager installed the package from a server (that is, from a package registry server or a Git remote repository), the following message appears instead:
You can follow this procedure for any version of any package. Note that the documentation is not necessarily different for each package version release, since some version updates (patches) involve only bug fixes or trivial changes.