Skip to content

Build Profiles and scene lists

↑

Unity 6 uses Build Profiles to organize settings per platform and build configuration. The profile chooses a target, scene list and optionally overrides shared Player or quality settings. The Platform Browser helps you manage platform support; a target module must be installed for its builds to work.

A scene list is not a file-system scan. Only included/enabled scenes are available for ordinary scene-based loading in the player. The startup scene is generally the first enabled scene in the active build’s scene list; keep menu/boot scenes deliberate. Store profile assets in version control so colleagues and CI use the same configuration.

A profile selects one target platform. Create separate Windows x64 and Linux x64 profiles rather than treating “Windows/Linux” as one target. Windows 10 and Windows 11 share a Windows target, but both require player testing. Install the correct platform module on your build host and check backend/toolchain support before cross-building. Give each profile its own output directory so builds cannot overwrite another platform’s files.

ExampleProfiles.txt
Windows-Development
Target: Windows x64 (Windows 10 and Windows 11)
Scenes: Boot, Menu, Level01
Development: enabled
Windows-Release
Target: Windows x64 (Windows 10 and Windows 11)
Scenes: Boot, Menu, Level01
Development: disabled
Linux-Development
Target: Linux x64
Scenes: Boot, Menu, Level01
Development: enabled
Linux-Release
Target: Linux x64
Scenes: Boot, Menu, Level01
Development: disabled

Pitfall: Overriding project-wide settings in one profile can create subtle differences from Editor testing. Record which profile was used for each artifact. Try it: Create separate development and release profiles and compare their overrides.

Further reading: Profile setup, Scene lists, Profile overrides.