Last reviewed 31 Jul 2026

Applies to

Unity 2022.3 VRChat Creator Companion Tutorial compatibility Project upgrades

Difficulty Beginner

Unity Version Differences for VRChat Projects

A Unity project is not independent of its editor version. Opening it with a different release can change serialized assets, packages, scripts, shaders, lighting data, and project settings.

For VRChat work, check three versions before opening or changing a project:

The Unity editor version currently supported by VRChat.
The Unity version recorded by the project.
The Unity version expected by any tutorial, package, shader, or asset you are using.

Check before opening a project

Match the project and platform requirements before allowing Unity to upgrade anything.

Check VRChat's current supported Unity version.
Check the editor version shown for the project in Creator Companion or Unity Hub.
Install and open the project with that exact editor version unless an official migration requires a change.

Current VRChat editor version

VRChat currently specifies Unity 2022.3.22f1. Its documentation warns that uploading with another Unity version can prevent content from loading. Recheck the official version page before installing or migrating because this requirement can change.

The Three Versions to Compare

Version to check	Where to find it	Why it matters
VRChat-supported version	VRChat's Current Unity Version page or Creator Companion	Determines which editor VRChat expects for uploaded avatars and worlds
Project version	Creator Companion, Unity Hub, or `ProjectSettings/ProjectVersion.txt`	Identifies the editor that last wrote the project
Guide or package version	Tutorial description, package documentation, release notes, or compatibility table	Explains differences in menus, APIs, packages, and setup steps

The platform requirement takes priority for a VRChat project. A tutorial written for another version may still explain a concept, but its exact menu paths or package instructions may not match.

What `2022.3.22f1` Identifies

Unity editor releases use a complete version identifier. In VRChat's supported version:

2022 identifies the release family.
.3 identifies the 2022 LTS stream.
.22 identifies a specific update in that stream.
f1 identifies the first final build of that update.

The complete value matters. Another 2022.3 release is still a different editor build, even though both belong to Unity 2022 LTS.

Unity Hub can install multiple editor versions side by side. Keep the VRChat-supported version installed even if another project requires a newer Unity release.

Find an Existing Project's Version

Creator Companion

Creator Companion displays the Unity version associated with projects in its project list. For a VRChat project:

Open Creator Companion.
Select Projects.
Find the project and inspect its Unity version.
Open Manage Project to review its VRChat packages before launching Unity.

If Creator Companion cannot locate an installed editor, use its Settings page to select the editor executable or install the supported version through Unity Hub.

Unity Hub

Unity Hub shows an editor version for each project in the Projects list. If the required version is not installed, install it before opening the project.

Do not select another installed version merely to dismiss a missing-editor warning. That action begins a version change.

Project settings file

With Unity closed, open:

ProjectSettings/ProjectVersion.txt

The recorded editor version is useful when Creator Companion or Unity Hub has not identified the project correctly. Read the file; do not edit it to force compatibility. Changing the text does not migrate project data, packages, or assets.

Why Guides Look Different

Version differences commonly appear in:

Symptom	Check first
A menu item is missing	Whether the feature moved or became a package in your editor version
The Inspector has different fields	The Unity version and installed package version used by the guide
Package Manager offers another version	The package's Unity compatibility and the project's manifest
Materials turn pink or render differently	The render pipeline, shader, and Unity version expected by the asset
A script no longer compiles	API changes, package changes, and the first Console error
Lighting or baking controls differ	The Unity release and lighting backend used by the guide

Use documentation that matches the editor release whenever possible. Unity's manual version selector changes the documentation set without changing your project.

Editor, Package, and SDK Versions Are Separate

The Unity editor version does not identify every dependency in the project.

Unity editor version: the installed Unity application used to open the project.
Unity Package Manager version: the version of each package recorded in Packages/manifest.json and resolved in Packages/packages-lock.json.
VRChat SDK and VPM packages: packages managed from Creator Companion's Manage Project screen.
Asset or shader version: compatibility information supplied by its publisher.

Changing one layer does not automatically make the others compatible. Review package and asset requirements before an editor migration.

For package-specific work, use Unity Package Manager Basics. Manage the VRChat SDK through Creator Companion rather than treating it as an ordinary Unity Registry package.

Render Pipeline Differences

Built-in, Universal Render Pipeline, and High Definition Render Pipeline projects use different shaders, materials, renderer settings, and package dependencies.

VRChat's current project setup documentation instructs creators to use its Creator Companion templates and states that standard VRChat projects do not use URP or HDRP. Do not convert a VRChat project to another render pipeline simply because a general Unity tutorial uses it.

When evaluating a tutorial or asset, confirm:

its Unity editor version
its render pipeline
its package versions
whether it explicitly supports VRChat

Open a Project Without Changing Its Version

Close any other Unity editor instances using the project.
Confirm the project has a recoverable backup or version-control checkpoint.
Find the recorded version in Creator Companion, Unity Hub, or ProjectVersion.txt.
Install that exact editor through Creator Companion, Unity Hub, or Unity's download archive.
Launch the project with that editor.
Wait for import and compilation to finish.
Resolve the first Console error before changing unrelated settings or packages.

If the project already matches VRChat's supported version, there is no version migration to perform.

Upgrade a VRChat Project Safely

Only migrate when VRChat documentation or another verified project requirement calls for it.

Read the applicable VRChat migration guide completely.
Close Unity.
Create a backup with Creator Companion, version control, or a separate project copy.
Preserve the original project instead of opening it with the new editor.
Install the required Unity version.
Open the copied project with the required editor and accept documented upgrade prompts.
Close Unity and update VRChat packages through Creator Companion when the migration guide requires it.
Reopen the project and resolve Console errors.
Test scenes, shaders, scripts, animation, lighting, platform switching, and uploads affected by the project.

VRChat has separate instructions for migrating Unity 2019 projects to Unity 2022 and for smaller supported-version changes. Follow the guide that matches the starting project.

Do Not Downgrade an Upgraded Working Copy

Opening a project in a newer Unity version can rewrite assets and settings. Reopening that changed working copy in an older editor is not a reliable rollback.

If an upgrade fails:

Close Unity.
Keep the failed copy for diagnosis if needed.
Restore the untouched backup or version-control state.
Open the restored project with its original editor version.

This is why the backup must exist before the first upgraded-editor launch.

Verify a Version Change

Creator Companion and Unity Hub identify the intended editor version.
Unity finishes importing and compiling.
The Console has no new compile or package-resolution errors.
Important scenes open without missing scripts.
Materials use their expected shaders.
Prefabs, animations, constraints, and custom editors still work.
Lighting and other generated data are rebuilt when required.
Platform switching completes for every intended build target.
VRChat SDK validation passes.
A world is checked with Build & Test, or an avatar is tested through the relevant SDK workflow.

Troubleshooting

Unity Hub wants to open the project with another editor version

Cancel the launch and check `ProjectSettings/ProjectVersion.txt`. Install the recorded version, or follow the official migration guide if the project is intentionally being upgraded.

Creator Companion cannot find Unity 2022.3.22f1

Install the supported editor through Creator Companion or Unity Hub. If it is already installed, open Creator Companion Settings and select the editor executable so the application can locate it.

A tutorial's menu path does not exist

Check the tutorial's editor and package versions, then open the matching Unity manual. The feature may have moved, changed names, or become available through Package Manager.

The project has pink materials after opening it

Confirm the project's render pipeline and the shaders required by its materials. Do not run a render-pipeline conversion until the asset or project documentation verifies that conversion is intended.

The project produces compile errors after an upgrade

Start with the first Console error. Check the affected package, script, or assembly against the target Unity version before updating additional dependencies. Restore the backup if the required dependency does not support the target editor.

I opened the project in a newer Unity version by mistake

Close Unity and restore the project from the untouched backup or version-control checkpoint. Do not rely on reopening the changed files in the older editor as a rollback.

Continue Learning

Official References

Next Step

Continue with Install and Configure Unity Hub for VRChat if the required editor is not installed, or Back Up and Restore Unity Projects before a migration.