Unity Package Manager (UPM) Publishing on Asset Store

UPM packages provide a standardized and structured folder with a package manifest (package.json file) and specific required metadata. It is better for managing dependencies and version control. See more details on the difference with .unitypackage here.

We will begin inviting participants in November 2025. At the time of the early access release, we are unable to support all use cases for UPM packages. For example, the initial phase only covers SDK and editor extension (tools) packages that are free to users. If we are able to accommodate your use case, you will receive an email from us to invite you to participate in early access. 

Please note that early access invites will be rolling out in phases, so even if your package fits the above criteria, you may not receive your invite to get started immediately. 

If you are not invited, you will still be notified of when UPM publishing on Asset Store becomes generally available (GA).

If accepted to join, you will be asked to provide the following information:

• Account Type = Individual or Organization

• Basic information = Legal name, country of residence, email, phone number

• Organization information (if applicable) = Company address, registered and active domain name, DUNS #

Early access will only support some use cases and acceptance to the program will be determined based on the type of package you would like to publish. If accepted, we will send an email invite to notify you to enroll and get started. When UPM publishing is generally available for all tools, publishers will be informed and can sign up via a self-serve enrollment process. However, please note that UPM packages are best suited for tools. See the “Who is this intended for?” section of the FAQ.

The timeline for availability for all tools is fluid based on the feedback received in the early access phase. Currently, we can only support free tools. Our aim is to offer UPM publishing for all tools (free and paid) by Spring 2026.

UPM publishing is ideal for modular and maintainable tools and SDKs. The structured format allows for easier updates and version control. UPM format is intended and designed to be immutable, so it is not a great fit for art and packages that frequently require modifications.

Your existing packages will continue to operate normally for those who have already acquired them. With UPM publishing creating a better publishing and end user experience, you can encourage your users to adopt the latest UPM package version by visiting your new UPM Product Details Page (PDP) to acquire your UPM packages. Once the UPM package is acquired for the first time, any future updates can be installed by users directly in the Package Manager.

• Please visit Unity’s user manual here to learn about the differences between package types.

• See recommendations for how to structure your UPM package manifest here.

• If you still have questions, please fill out a support request form with Unity Support.