Comparison of package creation locations
Choose whether to create your package inside or outside of the project's Packages folder.
Read time 1 minuteLast updated 20 days ago
Compare the different locations where you can place the package you create.
By default, Unity places packages you create in the folder of your project. However, you can move a package outside the project folder during development and optionally link it back to the project.
PackagesPackages in either location are identical in structure, but each supports different workflows, especially involving modularity, reuse, and collaboration. Understanding these differences can help you avoid refactoring later.
Use the following table to understand the key differences between packages you create inside and outside of your project:
Feature or characteristic | Packages in your project folder | Packages outside your project folder |
|---|---|---|
| Package location | Inside the | Outside the |
| Typical use | Develop a package within a single project (the current project) | Develop and reuse the package across multiple projects |
| Creation method | Package Manager window | Package Manager window with some manual steps |
| Project manifest file reference | Implicit (Unity automatically detects packages in the | Explicit reference required |
| Version control | Same repository as the project | Different repository than the project |
| Portability during development | Highly portable if the project uses version control | Limited due to environment-specific paths and system configuration |
| Identifying label that appears in Package Manager window | Custom | Local |
After you decide on a location for the package you will create, begin the package creation process by referring to package development workflow.