When you have finished developing your package, you can share it with other users.
Choose from the following methods to share your package:
| Type | Description |
|---|---|
| Compressed file | You can distribute a zip file to other Unity users. That way, they can decompress the zip file to a local folder on their own computer and install the package from disk. |
| Tarball | You can distribute a tarball to other Unity users. That way, they can install the package from the local tarball directly. For information about signing and packing your package, refer to Pack and sign your package. |
| Git URL | You can distribute a link to your Git repository, using one of the supported protocols. Then users can install your package using its Git URL, because the Unity Package Manager can fetch packages from Git repository hosting services like GitHub and GitLab. |
| Scoped Registry | You can set up a package registry server to host your package and then publish it to that registry. For more information, refer to Host a scoped registry. Your package’s consumers can then configure their project settings to Use a scoped registry to fetch your custom packages from your package registry. For information about signing and packing your package, refer to Pack and sign your package. |
If you plan to distribute your package by tarball or scoped registry, first pack and sign your package. This ensures your package is compatible with Unity’s package ecosystem, which checks for package signatures in version 6000.3 and higher.
You can use the standalone Unity Package Manager (UPM) CLI tool to pack and sign your package. For information, refer to Unity Package Manager CLI workflow. Note: This link opens the documentation for a higher version of the Unity User Manual. However, you can still use the UPM CLI tool with Unity 6000.0 because UPM CLI runs standalone without any Unity Editor.
.unitypackage extension. Asset packages are a handy way of sharing and re-using Unity projects and collections of assets. More info