VRChat's Quest open beta jumps to Unity 6, but creators must stay on Unity 2022
VRChat has moved its Quest standalone client onto Unity 6, but only on the open beta branch, and only for players who opt in. VRChat’s release notes for Build 1913, dated September 15, say the regular OpenBeta branch for testing Quest in standalone mode now uses Unity 6000.0.67f1.
Worlds and avatars like these are still built and uploaded from Unity 2022.3.22f1. Image: VRChat
Creators are told to stay exactly where they are. “Nothing has changed about the SDK side. Do NOT upgrades your SDK projects to Unity 6. It will not work,” the warning reads, with the typo and the capitals as VRChat wrote them, and the notes add: “We’ll let you know once that is ready.”
The separate unity-6 branch is closing
Unity 6 builds had been kept on their own opt-in branch. VRChat says Unity 6 is “now stable enough that we consider it ready for the regular open-beta branch”, so the unity-6 branch will be closed and the ordinary beta branches will hand out Unity 6 builds instead.
The headset is the new part of that. VRChat says Unity 6 “is now available on Quest”, putting the headset build on the same engine as the rest of the open beta.
What a new engine version changes on a headset
The VRChat client is a Unity application, so the engine version decides how every world and avatar is drawn, simulated and held in memory on the Quest’s own chip. Moving to Unity 6 swaps that layer out underneath worlds and avatars built in Unity 2022, which is why a beta build is where it happens.
Build 1913 fixes a crash that could happen during world loads, a crash tied to certain buffer particle setups, and an issue where TextMeshPro.renderer was unavailable to Udon. VRChat says the frame rate with high polling-rate mice is better but not properly fixed, and that it is still working with Unity and Microsoft on that one.
There are no numbers attached to any of it. VRChat has published no frame rate, memory or load time figures for the Unity 6 Quest build and calls it stable enough for the open beta, so what beta testers see is the only evidence so far.
Creators keep uploading from Unity 2022
Worlds and avatars still have to be built in Unity 2022.3.22f1, the version VRChat’s creator documentation lists as current. A creator who upgrades a project to match the client ends up with a project the SDK cannot use, and VRChat’s warning about that is a flat “It will not work”.
So the client engine and the SDK engine are on separate clocks for now. VRChat has given no date for Unity 6 support on the creator side, and no date for 2026.3.3 leaving beta. Unity’s own editor tooling has kept moving in the meantime: the engine now ships official Codex and Claude Code plugins.
Everyone else is still on the September 1 release
None of this has shipped to the wider player base. The current release for everyone is 2026.3.2, which VRChat put live on September 1, and the beta has carried on moving since Build 1913: Builds 1914 and 1915 both landed on September 18, the second of them Steam only, fixing intermittent SteamVR soft locks.
Until 2026.3.3 goes live, Unity 6 on Quest is something you have to go and switch on.
