Create and export asset packages
Create your own custom asset package to compress a collection of assets in your current Unity project.
Read time 2 minutesLast updated 22 days ago
To share any assets from your project's folder, you can export them as an asset package in the format. Asset packages are a convenient way to copy several assets or an entire scene from one project to another quickly, with little additional overhead.
Assets.unitypackageIf you want to distribute assets in a more formal way with long-term support, a defined structure, and semantic versioning, an alternative option is to create your own Unity package.
To create and export an asset package:
-
Open the project you want to export assets from.
-
Go to the Project window and select one or more items or folders. These items become the starting list for your export. You can also select thefolder to include all assets as your starting point.
Assets -
Choose Assets > Export Assets from the menu to open the Exporting package dialog.
-
In the dialog, select the checkboxes for the assets you want to include in the package.
-
Enable the Include dependencies checkbox to automatically select any assets (including scripts) used by the assets you select.
-
Enable the Include all scripts checkbox to export all scripts from your project.If you disable Include all scripts but enable Include dependencies, Unity only exports scripts that your selected items directly depend on. Unity can't trace the full chain of dependencies for your scripts, so enabling Include all scripts reduces the likelihood of compilation errors when using the exported package in another project.
-
Click Export to bring up the file explorer and choose where you want to store your package file.
-
Name and save the package.
Re-exporting asset packages
To create a new version of your asset package with updated contents, perform the export procedure again and select the changed and unchanged files to include in the new version.
Naming strategies
Name your updated package using incremental names suffixed with a version identifier, for example , , and so on. Unity recognizes these as updates of the same package. Use a naming convention that's clear for you and anyone you share it with.
MyAssetPackageVer1MyAssetPackageVer2