What Unity Version Does VRChat Use? | Exact Unity Build

VRChat isn’t “Unity in general.” It’s one specific Unity editor build, paired with a matching VRChat SDK package set. When your editor version drifts, small things break first, then uploads and builds can fail.

Below you’ll get the exact version, where to verify it, why VRChat pins to a single Unity LTS patch, and how to move an older project onto the current toolchain without trashing your files.

Why VRChat Pins To One Unity Editor Build

VRChat’s client is built on a Unity LTS line, and its creator tooling (SDK + packages) is tested against one editor build from that line. Locking the version keeps uploads predictable across Windows and Android workflows.

Unity patch builds differ in places creators feel: shader compilation, Android tooling, asset database behavior, and package APIs. Opening a VRChat project in a different patch can trigger a reimport that rewrites metadata, which is why version drift can create a messy diff in git or a “why did my materials change?” moment.

What Unity Version Does VRChat Use? For Avatars And Worlds

Right now, VRChat’s recommended Unity editor build for creators is 2022.3.22f1. Install that exact patch if you’re making or updating avatars and worlds with the current VRChat SDK.

The simplest route is VRChat Creator Companion. It sets up projects with the right packages, and it points you at the correct editor build. Unity Hub works too, as long as you install the exact patch VRChat recommends.

Client Version Vs Creator Version

The VRChat app can move between Unity patches on its own schedule, while creators follow the SDK recommendation. Your project should follow the creator recommendation, since uploads are validated through that toolchain.

How To Check Your Unity Version In A VRChat Project

Confirm the editor version before you chase any other error. It takes less time than reinstalling packages.

Check In Unity

• Open the project in Unity.
• Go to Help → About Unity.
• Compare the version string to VRChat’s recommended build.

Check In VRChat Creator Companion

• Open Creator Companion and select your project.
• Read the Unity version shown for that project.
• If it offers an install button, use it so you land on the exact patch.

Check The Project On Disk

If you need a quick sanity check, open ProjectSettings/ProjectVersion.txt in a text editor. It usually shows the Unity version the project was created with. Treat it as a clue, then confirm in the editor.

What Breaks When The Unity Version Is Wrong

Some mismatches fail loudly. Others fail in ways that burn time. These are the patterns creators hit most often.

Packages Won’t Resolve Cleanly

VRChat projects rely on a tested set of packages. With the wrong editor patch, Unity’s package manager can pull different dependency versions, leading to compile errors or missing VRChat menus.

Shaders And Materials Shift After Reimport

A different editor patch can trigger a full reimport. That can change generated files, rebuild shader variants, or alter how materials serialize. You might only notice it after build, when lighting or materials look off.

Quest Builds Fail In Gradle

Quest builds depend on Unity’s Android toolchain. Patch-level differences can change Gradle templates and dependency resolution. If a Quest build fails after a version swap, return to the recommended editor patch before you tweak Android settings.

SDK Panels Disappear

The SDK hooks into the editor. If scripts don’t compile, the VRChat control panels that handle builds and uploads can vanish. When you see that, assume a version mismatch until proven otherwise.

How To Install The Exact Unity Build VRChat Wants

If you want the least friction, install Unity through Creator Companion, since it nudges you to the correct editor patch and sets up VRChat packages in place.

If you manage installs yourself, match the exact editor version VRChat lists on its creator docs page: Current Unity Version. Treat the patch number as part of the requirement, not decoration.

How Unity Version Changes Roll Out In VRChat

VRChat doesn’t ask creators to chase each Unity release. It updates the recommended editor patch when the SDK and packages have been tested against it, then it nudges creators through Creator Companion and the upgrade pages.

When the recommended patch changes, treat it like a small project milestone. Finish any time-sensitive uploads first, then upgrade in a copy of your project. Open the copy on the new patch, let the reimport finish, run a test build, and do a small upload. If anything looks off, you still have the original project folder on the old patch.

If you work with others, agree on a switch date and keep all teammates on the same patch. Mixing patches during an upgrade week is where most “it works on my machine” bugs come from.

Upgrading From Unity 2019 To Unity 2022 With Fewer Surprises

Many long-running VRChat projects started on Unity 2019. Moving them to Unity 2022 works best as a planned migration, not a casual open-and-save. VRChat’s upgrade notes outline the current target patch and the general approach.

Backup The Project Folder

Copy the whole project folder before the first open on Unity 2022. Unity upgrades can rewrite assets and meta files. A clean backup lets you revert fast if the package set lands in a bad state.

Upgrade Packages As A Set

During migration, keep the VRChat packages aligned. Mixing an older SDK package set with a newer editor patch is a common cause of compile errors. Creator Companion helps because it upgrades the package set in a consistent order.

Let The First Import Finish

The first open in Unity 2022 can take a while because Unity rebuilds caches and reimports assets. Let it finish, then fix compile errors before you edit scenes or avatar setups.

Spot Check Builds Early

After the migration, run Play mode, then do a test build and a small upload. Pay attention to custom shaders, post processing, and third-party scripts that were written for older Unity APIs.

Unity 2022 LTS And The Patch Level

Unity’s 2022 LTS line is a family of patches, and VRChat picks one of them for creators. The patch number is where Unity ships editor fixes and Android tooling updates. Unity’s overview page is here: Unity 2022 LTS release overview.

If you want repeatable uploads, stay on the exact patch VRChat lists, even if a nearby patch looks close enough.

Common Scenarios And What To Do Next

You’re Starting Fresh

Install the recommended Unity patch, create a new project through Creator Companion, then add the VRChat packages through it. You’ll start from a clean baseline that matches the current SDK.

You’re On Unity 2022, But The Patch Is Different

Install the correct patch and open the project in that build. If Unity triggers a reimport, let it complete. Then run a test build and confirm the VRChat SDK panels load with no compile errors.

You Collaborate With Other Creators

Standardize on one editor patch for the whole team and write it down in your repo notes. If teammates open the same project on different patches, you’ll see noisy diffs, meta file churn, and inconsistent imports.

Fast Troubleshooting Checklist For Version Issues

When something breaks, start with version alignment. It solves more problems than a random reinstall loop.

Small Habits That Keep VRChat Projects Stable

Keep A Dedicated Unity Install For VRChat

Use a separate Unity install for VRChat and avoid upgrading it unless VRChat changes its recommendation. That keeps imports and builds consistent.

Freeze Packages During A Release Push

If you’re close to shipping a world or avatar update, avoid package updates on a whim. Upgrade in a copy of the project, test builds, then merge once you’re happy with the result.

Test A Tiny Upload After Any Change

After you change the Unity patch or VRChat packages, do a small upload test. It catches build issues early, before you’ve sunk hours into content edits.

Answer Recap

VRChat creators should use Unity 2022.3.22f1 for current SDK work, then keep all collaborators on that same patch so imports and builds stay consistent.

Send us your feedbackTell us what you thought about this post

⚠Please use a real email you check. If it's fake or mistyped, your message won't reach us and we can't reply — wrong addresses are rejected automatically.

Name *Email *

Your comment *

Quick check — what is …? *

Send feedback