Build Settings and Export Basics
Build Settings is where Unity decides what scenes are included in a build and which platform the project is targeting. For beginners, this window often looks small and simple, but it controls some very important parts of the export process.
If Build Settings is wrong, you can easily:
- build the wrong scene
- miss important content
- target the wrong platform
- end up with materials or features behaving unexpectedly
That is why it is worth understanding early.
Use Build Settings as a final sanity check before testing, exporting, or publishing a Unity or VRChat world.
- Save the scene and confirm the correct scene is listed in Scenes In Build.
- Confirm the active platform matches the build or upload you are about to test.
- Clear Console errors before blaming the export or VRChat SDK publish step.
For VRChat worlds, Unity Build Settings and the VRChat SDK publish flow are related but not identical. Confirm the supported Unity version, SDK packages, scene descriptor, and PC or Android target before uploading.
Playlist Companion
This video fits here because it shows the moment when scene setup, platform targeting, and the actual publish handoff all collide in a real beginner world workflow.
Uploading to PC & Quest - Create Your First VRChat World
Platform-switch follow-up: Easy Quest Switch, a MUST for quest world creators - Udon / VRChat SDK3.0
Where to Open Build Settings
Open it from:
- File -> Build Settings
This window controls which scenes are included and which platform Unity is currently preparing for.
| Build Settings area | What to check |
|---|---|
| Scenes In Build | The correct world or test scene is listed and enabled. |
| Platform | The active target is the one you intend to build or test. |
| Switch Platform | Use this when moving between PC and Android targets. |
| Player Settings | Project-level settings that can affect output and platform behavior. |
| Build options | Development or debug options should match the purpose of the build. |
What "Scenes In Build" Means
The Scenes In Build list is the set of scenes Unity includes when building.
This matters because Unity will not automatically include every scene in your project just because it exists in the Assets folder.
If a scene is not in the build list, it may not be part of the final build output.
For normal Unity builds, the scene list directly controls what gets included. For VRChat world publishing, the SDK workflow also depends on the active scene containing the correct world setup, so do not treat Build Settings as the only upload checklist.
How to Add a Scene to the Build
To add the currently open scene:
- Open the scene
- Save it
- Open Build Settings
- Click Add Open Scenes
This is one of the easiest beginner steps to forget.
Why Scene Order Matters
The order of scenes can matter depending on the project workflow.
For example:
- the first scene may be treated as the entry scene in some workflows
- test scenes left in the wrong place can cause confusion
Even when you are only working with one main scene, it is good practice to review the build list instead of assuming it is correct.
For a simple VRChat world, you normally want to be extremely clear about the one main world scene you are testing or publishing. Old sample scenes and abandoned test scenes should not be left around to create confusion.
Choose the Correct Platform
Build Settings also controls the active target platform.
This matters because platform choice can affect:
- import settings
- shader behavior
- package compatibility
- build output
If the project targets the wrong platform, you may see visual differences or unexpected build problems.
| Goal | Typical target to verify |
|---|---|
| Desktop VRChat world testing | PC, Mac & Linux Standalone / Windows-style desktop target. |
| Quest or Android world testing | Android target with Android Build Support installed. |
| Generic Unity desktop build | The desktop platform you intend to export. |
| Mobile Unity build | The correct mobile platform and installed build module. |
What Happens When You Switch Platform
When you switch the target platform, Unity may need to reimport assets.
This can take time.
During that process:
- wait for Unity to finish
- do not interrupt it without a good reason
- expect some temporary slowdown
Beginners sometimes think Unity is frozen when it is actually just reprocessing project data for the new platform.
For VRChat projects, switching to Android can also reveal material, shader, texture, or SDK warnings that were less obvious on desktop. Treat those warnings as platform-specific feedback, not random noise.
A Safe Beginner Build Checklist
Before building, confirm:
- the correct scene is open
- the correct scenes are listed in Build Settings
- the target platform is correct
- there are no red Console errors
- major references are not missing
- important materials and lighting have been checked
- the VRChat scene descriptor is present when publishing a world
- the SDK Control Panel has been checked for build or upload warnings
If you build without checking those basics, mistakes are much more likely.
Why the Wrong Scene Gets Built So Often
This is a very common beginner problem.
It usually happens because:
- a test scene was left in the build list
- the main scene was never added
- the build list is old and was not updated
If the result looks wrong, always check the scene list before assuming the build process itself is broken.
Build Settings and Testing
Even if you are not making a final release build, Build Settings is still useful because it forces you to verify:
- which scene is considered active
- whether the scene list is clean
- whether the platform target matches your intent
That makes it a useful project sanity check, not just an export window.
Common Beginner Problems
The wrong content appears in the build.
This is usually caused by the wrong scene in the build list, outdated scene order, or a saved test scene being built instead of the main scene.
Materials or shaders look different after switching platform.
This may be caused by platform-specific import settings, render pipeline setup, shader compatibility, or Android and Quest constraints that do not apply the same way on desktop.
The build fails unexpectedly.
Start with Console errors, missing references, package problems, scene list correctness, and SDK warnings before changing unrelated project settings.
The VRChat upload panel does not match what I expected.
Check the active scene, scene descriptor, SDK packages, active platform, and whether you are using Build & Test or Build & Publish in the VRChat SDK workflow.
A Good Beginner Habit
Before each important build or publish step:
- Open Build Settings
- Confirm the scene list
- Confirm the active platform
- Confirm the project is error-free
That quick check prevents many avoidable mistakes.
Exporting vs Publishing
It is also useful to understand that "build/export" and "publish" are not always the same thing.
In many workflows:
- Build/export means Unity creates a runtime output for a target platform
- Publish means that output or scene is then uploaded or distributed through another platform or workflow
Understanding that distinction helps beginners make more sense of why Build Settings matters even when another SDK or tool handles the final publish step.
| Term | Meaning |
|---|---|
| Build | Unity creates output for the active target platform. |
| Build and Run | Unity builds and tries to launch that output on the target device or platform. |
| Build and Test | In VRChat workflows, the SDK can build the world and launch a test session. |
| Build and Publish | In VRChat workflows, the SDK uploads the world so it can be visited through VRChat. |
References
-
Official source: Unity Build Profiles / Build Settings - reviewed 2026-05-26.
-
Official source: VRChat Creating Your First World - reviewed 2026-05-26.
-
Official source: VRChat Build and Test for Android Mobile - reviewed 2026-05-26.
-
Local note: Unity build terminology and VRChat SDK build/publish terminology are separate; keep future edits explicit about which tool is being described.
Helpful follow-up pages
Final Advice
Build Settings is easy to ignore until it causes a mistake. The safest approach is to treat it like a final checkpoint:
- right scene
- right order
- right platform
- right project state
That one habit will prevent a surprising number of beginner build issues.
Help! I cannot find the window, object, or setting shown here.
Reset to Unity's default layout, check the Window menu, and make sure you are editing the correct scene or selected object before troubleshooting deeper.
Help! I changed the wrong thing.
Undo immediately if possible, then save a known-good state before continuing. For important scenes, work from a duplicate until the workflow is comfortable.
