Udon Documentation

Browse UdonSharp scripts, reusable Udon systems, official VRChat Udon references, networking guidance, persistence notes, and beginner-friendly world scripting examples.

190 articles

Start Points

Udon paths

01 Beginner Examples Small UdonSharp scripts and first interaction patterns. 02 Local Interactions Buttons, teleport pads, local UI, and object toggles. 03 Networking Events, synced variables, ownership, and late joiners. 04 Persistence Saved preferences, scores, unlocks, and player data. 05 Prefabs And Systems Reusable packages, gameplay systems, and utilities.

Official References

Official VRChat Udon references.

VRChat Udon Official Udon hub for world scripting. UdonSharp Official C# scripting path for Udon behaviours in Worlds SDK projects. Udon Networking Official reference for variables, events, ownership, and synchronized world behavior. Persistence Official reference for PlayerData, PlayerObjects, and saved world state. ClientSim Official Unity editor simulation reference for faster local world checks.

Nearby VRCreators Guides

VRCreators Udon guides.

First Interactive ButtonBuild one local UdonSharp interaction. Networking Decision GuidePick the right multiplayer pattern. Persistence GuidePlan saved state before implementation. ClientSim TestingCheck world behavior inside Unity first. World SetupGet the world project stable before scripting. Creator CompanionUse the supported project setup path. Prefab HubBrowse categorized reusable VRChat systems. Synced ToggleStart with a small synced state example.

Common Udon Decisions

Answer these before choosing a script.

Should I start with Udon Graph or UdonSharp?

Use UdonSharp when you are comfortable reading small C# scripts or want reusable code. Use Udon Graph when a visual node setup is enough for a small behavior.

Does this need networking?

If the result only affects one player, keep it local. If everyone needs to see the same state, decide between a network event, a synced variable, ownership transfer, or persistence.

When does ownership matter?

Ownership matters when one client is allowed to write or synchronize state for an object. Check ownership before debugging synced variables or shared interactions.

When should I use persistence?

Use persistence for saved preferences, scores, unlocks, progress, or per-player objects that need to survive beyond the current instance.

Can ClientSim replace uploaded testing?

No. ClientSim is useful for fast editor checks, but multiplayer, platform behavior, and final SDK behavior still need VRChat testing before release.

Should I import a prefab first?

Use a prefab when you understand its setup requirements. If the concept is new, build one small local or synced example first so you know what the prefab is solving.