Experimental packages

Experimental packages are new packages or experimental modifications made to mature packages. Unity does not support Experimental packages because they are in the early stages of development.

Experimental packages can go through many changes before they are ready to be released in a specific version of Unity. At some point in the future, they might pass the verification requirements; however, they might also be deprecated instead. Because there is no guarantee for future support, you should not use experimental packages in production.

Packages in this state do not usually appear in the Unity Registry context of the Unity Editor, even though they are on Unity’s official package registry server. These packages are not discoverable in the Package Manager window because:

• They are too risky to use in production. Some of these packages require a lot of training and expertise and are therefore recommended only in specific circumstances.
• They provide shared or additional functionality to existing packages. You shouldn’t use them on their own because they are “support” packages only.

Undiscoverable packages can still appear in the Package Manager window if they were previously installed in your project or installed as dependencies of supported packages. However, they are hidden so that you don’t discover them by accident and use them without realizing the risks. If they do appear in the Editor, they are always marked with the label, and the following warning label appears in the Editor:

For a list of stable packages verified for this release, see Released packages.

For more information about package states, see Package states and lifecycle.