Documenting your package
Feature sets

Sharing your package

You can set up your own package registry server if you want to control package access to a limited number of users, or if you need to set up package registry servers in a closed network organization.

When you have finished developing your package and you want to share it with other users, you have several options:

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

Additional resources

  • Creating custom packages
  • 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

Did you find this page useful? Please give it a rating:

Documenting your package
Feature sets