Version: 2020.3
Installing from a registry
Installing a package from a local tarball file
How do you use documentation throughout your workflow? Share your experience with us by taking this survey.

Installing a package from a local folder

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 and you save it on the Desktop but your Unity project is under the Documents folder).

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:

  1. Click the add button in the status bar.

  2. The options for adding packages appear.

    Add package from disk button
    Add package from disk button
  3. Select Add package from disk from the add menu to bring up a file browser.

  4. Navigate to the folder root of your local package.

  5. Double-click the package.json file in the file browser.

The file browser closes, and the package now appears in the package list with the local tag.

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.

Local packages inside your project

You can place a local package anywhere inside your project except under these folders:

Project folder: Reason:
Assets 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.
Library Do not modify the contents of this folder.
ProjectSettings This folder is for settings assets only.
Packages 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

Installing from a registry
Installing a package from a local tarball file