Choose from multiple methods to sign packages that you create.
When you sign a package, you must associate it with one of your organizations, so package consumers can quickly determine who created and owns it.
The only packages you can sign are packages that have the Custom or Local label in the Package Manager window:
Packages folder of your project.Each method creates a signed tarball (.tgz) or a signed folder ready for distribution and compatible with Unity’s package signature ecosystem.
| Method | Description |
|---|---|
| Unity Package Manager window | Sign and export with a visual interface directly in the Unity Editor. Ideal for one-off exports that don’t need automation. |
| Unity Editor CLI (signed tarball) | Scriptable signing that runs inside the Unity Editor in batch mode to create a signed tarball. Ideal for continuous integration or continuous delivery (CI/CD) pipelines that already use Editor command-line arguments for building or testing. |
| Unity Editor CLI (signed folder) | Scriptable signing that runs inside the Unity Editor in batch mode to sign a source folder for a Git-based package. Ideal for continuous integration or continuous delivery (CI/CD) pipelines that already use Editor command-line arguments for building or testing. |
| Unity Package Manager CLI | Lightweight standalone tool that doesn’t require a Unity Editor installation. Uses service account credentials instead of personal credentials. Ideal for CI/CD pipelines and secure automated environments. Use the pack command to create a signed tarball or use the sign command to sign a source folder. |
| Scripting API | Sign packages using C# scriptsA piece of code that allows you to create your own Components, trigger game events, modify Component properties over time and respond to user input in any way you like. More info See in Glossary that run inside the Unity Editor. Ideal for custom Editor tools or workflows that already process or publish packages with scripts. |