Important: This is an early access workflow, and is available only to selected publishers to publish free Unity Package Manager (UPM) packages. To register your interest and apply for early access to UPM publishing, go to UPM Publishing on the Asset Store.
You can create a Unity Package Manager (UPM) package from assets that you own and make it available to download on Unity’s Asset StoreA growing library of free and commercial assets created by Unity and members of the community. Offers a wide variety of assets, from textures, models and animations to whole project examples, tutorials and Editor extensions. Unity Package Manager (UPM) package from assets that you own and make it available to download on Unity’s Asset StoreA growing library of free and commercial assets created by Unity and members of the community. Offers a wide variety of assets, from textures, models and animations to whole project examples, tutorials and Editor extensions. More info
See in Glossary. Manage UPM packagesA Package managed by the Unity Package Manager. Refer to Packages.
See in Glossary through the UPM publishing portal, which differs from the asset package publishing workflow.
Important: An Asset Store package must meet certain legal requirements. For more information, refer to the Asset Store Provider Agreement and the Submission Guidelines.
The early access UPM publishing workflow introduces the concept of a product. A product is different from a package in the following ways:
You create a product draft in the Publisher Portal to manage and configure the structure of your packages. A product can contain one or multiple packages. For more information, refer to Create a Publisher Portal package draft (Beta).
UPM packages require consistent namespaces. The following table shows each of the namespaces you need to set for the different stages of the UPM publishing workflow:
| UPM workflow step | Namespace action | Description | 
|---|---|---|
| Sign up to the early access UPM workflow | Set a publisher namespace. | Establish and claim a namespace for your packages during the early access enrollment process. | 
| Create a UPM product draft for a single package | Set a product namespace. | Assign a product namespace. The product namespace becomes part of the technical name. | 
| Create a UPM product draft for multiple packages | Set a product namespace and a package namespace for each package. | Assign a package namespace for each package you add. The package namespace becomes part of the technical name. | 
| Create and validate UPM packages | Set the UPM package folder and package.json namespaces in the name field. | 
	The UPM package folder and the package.json name must match the package’s technical name. | 
| Upload UPM packages | The Asset Store Publishing Tools checks and matches the package technical name to the one set on the Publisher Portal. | If the publisher space doesn’t match the product namespace, a button appears that you can select to create a new ID. If the technical name doesn’t match the product namespace, a button appears that you can select to create a new product draft. | 
For more information about setting namespaces, refer to Create a Publisher Portal package draft (Beta).
To publish assets to the UPM publishing portal, you must first create the following:
To publish a UPM package to the Asset Store, you need an invitation to the closed beta. To apply to join the UPM publishing early access program, go to UPM Publishing on the Asset Store.
If accepted, you receive an email invite with a link to enroll in early access, and then must perform the following steps:
You can then check the status of the package, and once published, you can make further updates in the Publisher Portal.