The Package Manager can load a package from anywhere on your computer even if you saved it outside your Unity project folder (for example, if you have a package called com.unity.my-local-package and you save it on the
Desktop but your Unity project is under the
You can also use a folder inside your project folder, provided that it is not one of the reserved project sub-folders.
To load a package from your local disk:
Open the Package Manager window, if it’s not already open.
Click the add button in the status bar. The options for adding packages appear.
Select Add package from disk from the add menu to bring up a file browser.
Navigate to the folder root of your local package.
package.json file in the file browser.
The file browser closes, and the package now appears in the package list with the tag.
Note: If you have a package installed locally that matches a version in the registry, the Update button still appears and the list might display the same version twice as Currently Installed and Recommended:
Remember that if you updated to the registry version but you made changes locally to your project, the registry version will overwrite your local changes.
You can place a local package anywhere inside your project except under these folders:
|If you place a package inside this folder, the Asset Database imports any assets under this folder twice: once as assets and once as package contents.
|Do not modify the contents of this folder.
|This folder is for settings assets only.
|If you place a package under this folder, the Package Manager automatically interprets it as an Embedded package
See in Glossary, regardless of the reference in the project manifestEach Unity project has a project manifest, which acts as an entry point for the Package Manager. This file must be available in the
<project>/Packages directory. The Package Manager uses it to configure many things, including a list of dependencies for that project, as well as any package repository to query for packages. More info
See in Glossary.