Last reviewed 31 Jul 2026

Applies to

Projects that already contain ProGrids Unity package migration VRChat world maintenance

Difficulty Intermediate

Migrate a Legacy ProGrids Project

Use this guide only when an existing Unity project already contains ProGrids. The package was documented as a preview package for Unity 2020.2, and it is not in Unity 2022.3's released-package list. Do not install it into a new Unity 2022.3 project.

Migration sequence

Preserve the working project, reproduce its snapping workflow, and remove the dependency only from a tested copy.

Keep the original project on its known working Unity version.
Create a separate migration copy and record the ProGrids version and snap settings.
Replace the workflow with Unity's built-in snapping before removing anything.

VRChat project note

Create or upgrade VRChat projects through Creator Companion and use the Unity version it selects. A legacy ProGrids dependency is not a reason to add the package to a clean Creator Companion project.

Confirm Which ProGrids Installation You Have

ProGrids existed in more than one installation form. Identify the form before changing the project.

What you find	Installation type	What it means
ProGrids appears under In Project in Package Manager	Unity Package Manager package	The project may have a direct `com.unity.progrids` dependency.
`com.unity.progrids` appears in `Packages/manifest.json`	Direct UPM dependency	Package Manager can remove the direct dependency from the project manifest.
A ProGrids folder exists under `Assets`	Earlier asset-folder installation	Do not treat it as a UPM package. Unity's legacy upgrade instructions handled this form separately.
ProGrids does not appear in Package Manager or `Assets`	No confirmed installation	Search project files and version-control history before deleting anything.

Do not edit Packages/manifest.json merely to test whether the project still works. Use Package Manager for a confirmed UPM installation so Unity can resolve the package graph.

Record the Working State

Open the untouched project in its known working Unity version and record:

the Unity editor version;
the ProGrids version shown in Package Manager or its package files;
the move, rotation, and scale snap values;
any custom grid axis, offset, unit, or visibility settings used by important scenes;
screenshots of modular seams, doorways, stairs, and repeated structures;
current Console errors before migration.

This record gives you a concrete comparison after the snapping interface changes.

Reproduce the Workflow with Built-In Snapping

In the migration copy:

Open the Scene view Grid and Snap overlay.
Enter the recorded values under Increment Snap.
Use Align Selected to place reference pieces on the grid.
Use automatic grid snapping or hold Ctrl on Windows or Command on macOS while moving, rotating, or scaling.
Use vertex snapping for pieces whose pivots do not match the grid.
Reopen each important scene and compare the recorded seams and Transform values.

Replace ProGrids with Unity 2022.3 Grid Snapping maps the old ProGrids controls to their built-in equivalents.

Remove a UPM ProGrids Dependency

Only continue after the project can be edited with built-in snapping and the migration copy is backed up.

Open Window > Package Manager.
Select In Project from the package list menu.
Select ProGrids.
Click Remove.
Wait for Unity to finish resolving packages and compiling scripts.
Save, close, and reopen the project.
Check the Console, important scenes, prefabs, and build or upload workflow used by the project.

Unity explains that removing a UPM package removes the project's direct dependency. If another installed package depends on it, the package can remain as an indirect dependency. Check Package Manager again after removal instead of assuming the package files are gone.

Do not manually delete Unity's global package cache. Unity's Package Manager documentation specifically discourages manipulating that cache.

Handle an Assets-Folder Installation

If ProGrids exists as files under Assets, the UPM Remove button does not manage those files. Unity's historical ProGrids instructions treated this as an earlier installation form during an upgrade.

For a migration away from ProGrids:

Keep the untouched project and a separate migration copy.
Search scenes, prefabs, and scripts for references to the ProGrids folder or types.
Reproduce the snapping workflow with built-in tools.
Remove the legacy folder only in the migration copy.
Let Unity reimport and compile.
Restore the copy if missing-script references, compile errors, or scene changes appear.

Do not delete the folder in the only working copy of the project.

Validate the Migration

Check more than whether the editor opens:

Area	What to verify
Console	No new compile errors or missing-script messages.
Scenes	Modular seams, stairs, walls, floors, and ceilings remain aligned.
Prefabs	Prefab instances open and apply changes normally.
Editing	Move, rotation, scale, vertex, and surface snapping cover the tasks previously done with ProGrids.
Packages	`com.unity.progrids` is no longer a direct dependency if it was removed through Package Manager.
Project workflow	The project's normal local build or VRChat upload preparation still completes.

If a scene changes unexpectedly, compare it with the untouched project before making more package changes.

Legacy Video Reference

This video demonstrates the old ProGrids interface. Use it to identify a tutorial's snapping action, then reproduce that action with the built-in controls.

Open the legacy ProGrids video on YouTube

Troubleshooting

ProGrids is not listed under In Project

Check Packages/manifest.json for com.unity.progrids and look under Assets for an older ProGrids folder. Do not add the package just to make a Remove button appear.

The Remove button is disabled

Hover over the disabled button for Unity's reason. The package may be locked or required by another package or feature set; inspect the dependency information before editing the manifest.

ProGrids remains after removing the direct dependency

Another installed package or feature set may still require it as an indirect dependency. Package Manager can remove the direct manifest entry while retaining a required indirect package.

The project has an Assets/ProGrids folder

That is not the same as a UPM dependency. Work only in a migration copy, search for project references, and verify scenes and scripts immediately after removing the legacy folder.

Objects no longer snap to the expected positions

Compare the recorded ProGrids values with the built-in Increment Snap values. Also check the visual grid size, active grid plane, object pivot, and Global handle orientation.

Removing ProGrids creates compile or missing-script errors

Stop the migration and restore the backed-up copy. Search the affected scripts, prefabs, and scenes for ProGrids references before attempting removal again.