Last reviewed 31 Jul 2026

Applies to

Unity packages VRChat Creator Companion packages Unity asset packages

Difficulty Beginner

Install and Remove Unity Add-ons Safely

“Add-on” can mean a VPM package, a Unity Package Manager package, an Asset Store package, or files imported from a .unitypackage. Identify the format first, because each type has a different install, update, and removal path.

Identify the Add-on Type

What you received	Use this tool	Typical location
Package shown under Manage Project in Creator Companion	VRChat Package Manager	Packages and the VPM manifest
Package name such as com.unity.probuilder	Unity Package Manager	Packages/manifest.json
Git URL, local package folder, or .tgz package	Unity Package Manager	Referenced through the project manifest
Asset Store purchase or download	Package Manager My Assets	Imported files under Assets
Local .unitypackage file	Assets > Import Package > Custom Package	Imported files under Assets
Loose files or folders	Project window	Copied directly under Assets

Do not assume two similarly named add-ons use the same manager. Follow the publisher's current installation documentation and preserve the package identifier it provides.

Create a Backup

For a VRChat project:

1. Close Unity.
2. Open the project in Creator Companion.
3. Select Make Backup.
4. Wait for the backup ZIP to finish before changing packages.

Creator Companion stores backups under %LOCALAPPDATA%\VRChatCreatorCompanion\Project Backups by default. Source control is also useful, but Unity's Library folder should not be treated as source content.

Install a VPM Package

Use Creator Companion for official, curated, community, and user VPM packages:

1. Open Creator Companion and select Projects.
2. Select Manage Project for the correct project.
3. Find the package and review its installed and available versions.
4. Select the version documented for the project, or use the available add control.
5. Open the project and allow Unity to finish resolving and compiling.
6. Check the Console before opening important scenes.

Creator Companion distinguishes:

• Official Packages, including VRChat Base, Worlds, and Avatars;
• Curated Packages listed by VRChat;
• Community Packages supplied through added repositories;
• User Packages loaded from local package folders.

A curated listing does not replace the package author's documentation. Check the package's supported Unity, SDK, project type, and platform versions before installing it.

Add a Community Repository

Only add a repository from a publisher you intend to trust:

1. Open Creator Companion Settings.
2. Open the Packages tab.
3. Select Add Repository.
4. Enter the repository URL supplied by its publisher.
5. Review the repository name and included packages before confirming.

Removing a repository stops it from appearing as a source in Creator Companion. It does not automatically prove that packages previously added from that repository are safe to remove from a project.

Install a Unity Package Manager Package

Open Window > Package Manager in Unity.

The install menu supports several sources:

Install option	Use it when
Registry list	The package is visible in Unity Registry or another configured registry.
Add package by name	Official documentation gives an exact package ID.
Add package from Git URL	The publisher documents a Git repository URL and revision.
Add package from disk	A local folder contains a valid package.json.
Add package from tarball	The publisher supplies a UPM .tgz archive.

For Add package by name, copy the complete identifier exactly. Do not guess a version number. If a specific version is required, use the version documented for the project.

After installation:

1. Wait for package resolution and script compilation.
2. Read the Unity Console.
3. Open the package's documentation or Samples tab when provided.
4. Test its editor window or component in a disposable scene.

Import an Asset Store Package

Open Window > Package Manager, then select My Assets:

1. Sign in through Unity Hub if prompted.
2. Find the asset.
3. Download the required version.
4. Select Import.
5. Review the file list and deselect demo content or optional files you do not need.
6. Complete the import and inspect the Console.

Asset packages copy files into Assets. They are not the same as UPM packages referenced by Packages/manifest.json.

Import a Custom .unitypackage

Use Assets > Import Package > Custom Package, select the file, and inspect the import list.

Before selecting Import, check for:

• project settings or editor configuration;
• scripts and precompiled plug-ins;
• shader and render-pipeline dependencies;
• folders that overlap existing assets;
• demo scenes, textures, and models you do not need;
• files with names already present in the project.

A .unitypackage import can merge files directly into existing folders. A backup is the reliable rollback path if the package does not provide a complete uninstall list.

Update One Package at a Time

Before updating:

1. Read the package changelog.
2. Confirm its Unity and VRChat SDK compatibility.
3. Back up the project.
4. Update one package through the manager that installed it.
5. Open or return to Unity and wait for compilation.
6. Test the affected scene, avatar, prefab, or editor window.
7. Run the relevant VRChat build validation.

Do not update unrelated packages during the same diagnostic pass. If an error appears, the changed package and version should be unambiguous.

Remove the Correct Package Type

Remove a VPM package

Remove VPM packages with Creator Companion or other documented VPM tooling instead of deleting their folders under Packages. Open the project's Manage Project screen and use the available package controls.

Do not force-remove VRChat Base or another required dependency simply to clear an error. VRChat's VPM command documentation warns that forced removal can break the project.

Remove a UPM package

In Unity:

1. Open Window > Package Manager.
2. Select In Project.
3. Select the package.
4. Review its dependencies.
5. Select Remove.

Unity disables removal when another installed package or feature set requires the package. Removing a direct dependency from the manifest does not necessarily remove it when another package still depends on it.

Remove imported assets

Files imported from My Assets or a custom .unitypackage are stored under Assets. Do not use the UPM removal instructions for them.

Unity 2022.3 does not track dependencies between imported assets. To remove an imported Asset Store package:

1. Open Window > Package Manager and select My Assets.
2. Select the package and note its package and publisher names.
3. In the Project window, locate the publisher's imported files under Assets.
4. Confirm which scenes, prefabs, materials, and scripts use those files.
5. Delete only the identified assets, or restore the pre-import backup when the package merged into shared folders.

Removing imported files from the project does not remove the downloaded .unitypackage from Unity's Asset Store cache or from the My Assets list.

Verify the Project

After installing, updating, or removing an add-on:

• wait until Unity finishes compiling;
• inspect the Console for new errors and warnings;
• confirm the package no longer reports missing dependencies;
• open the scenes or prefabs that use it;
• run VRChat SDK validation;
• perform a local avatar or world test when runtime content changed.

Troubleshooting

The add-on does not appear in Creator Companion.

Confirm that it is a VPM package and that its official, curated, community, or user repository is enabled. A UPM package or unitypackage will not appear in Creator Companion's package list.

Unity Package Manager cannot find the package name.

Copy the exact package ID from its official documentation and confirm the required registry is configured. A display name is not necessarily the package ID.

The Remove button is disabled.

Review the package's dependencies in Package Manager. Unity prevents removal when another installed package or feature set still requires it.

A custom unitypackage overwrote existing files.

Stop making further changes and restore the backup or source-control state created before the import. Deleting only the obvious new folder may not restore files that were merged or overwritten elsewhere.

The project has compile errors after an update.

Record the first relevant Console error, package ID, old version, and new version. Restore the backup or return to the documented compatible version through the same manager used for installation.

I removed the imported files, but the package remains in My Assets.

My Assets lists packages associated with the Unity account and cache. Removing files from the current project's Assets folder does not remove that listing or the cached download.

Official references

• Unity Package Manager Window
• Unity: Add and Remove Packages
• Unity: Add a Package by Name
• Unity: Import a Custom Asset Package
• Unity: Remove Imported Assets
• Creator Companion Package Manager
• VPM Package Types
• VPM command-line package controls
• Creator Companion Community Repositories
• VRChat Curated Community Packages
• Creator Companion FAQ

Continue learning

• Package Manager Basics
• Unity and VRChat Tools for World Building
• Unity and VRChat Troubleshooting
• Understand Unity Package Manifest Files
• Unity and VRChat Creator Tools