Unity Package Cheatsheet

Surprisingly enough, I haven’t been able to find a convenient page that lists all packages along with links to the latest documentation… so I made my own.

Missing package? Broken link? Outdated info? You can help keep this page up to date on Github.
Feel free to add useful links to blog posts, video tutorials, forums, threads, etc.

• About packages
• Package list
• About built-in packages
• Built-in package list

About packages

A “package” is a container that stores various types of features or assets, such as:

• Editor tools and libraries, such as a text editor, an animation viewer or test frameworks.
• Runtime tools and libraries like the Physics API or a Graphics pipeline.
• Asset collections, such as Textures or animations.
• Project templates to share common project types with others.

Install packages using the Unity Package Manager.

Some packages (eg. experimental ones) might not show up in the package list automatically; to install them use the Add package by name... option. Look up the Package ID in the table below.

On older Unity versions, you can use the Add package from Git URL... option instead (simply paste the Package ID instead of the repository URL).
If you prefer, you can also manage packages via the manifest.json file stored in Assets/Packages/ in your project path.

Learn how the package manager works here.
Read about package states, versions and lifecycle here.

Package list

About built-in packages

Built-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.

When you remove a built-in package for a feature, Unity does not include the related code and resources when you build your final application. Typically, these built-in packages contain only the package manifest and are bundled with Unity (rather than available on the package registry).

You can add or remove built-in packages in the Package Manager, in the Built-in tab. Disabling unneeded packages early in development will help you avoid referencing them by accident.

Built-in package list

Todo

• Keep adding missing packages (eg. ones only available on GitHub)
• Add more links (eg. YT tutorials)
• Add list of built-in modules
• Improve table readability