Use the Build Settings window to choose your target platform, adjust the settings for your application build, and start the build process. To access the Build Settings window from Unity’s main menu, go to File > Build Settings.
This documentation describes how to define the Scenes, target platform, and settings for your build. When you have configured the Build Settings, there are two options: Build, and Build and Run.
The Scenes In Build pane displays a list of the Scenes from your Project that Unity includes in the build. If you can’t see any Scenes in this pane, select Add Open Scenes to add all currently open Scenes to the build. You can also drag Scene Assets from your Project windowA window that shows the contents of your
Assets folder (Project tab) More info
See in Glossary into this window.
To exclude a Scene in the list from the build, clear the checkbox next to that Scene. This removes the Scene from the build, but not from the list. To remove a Scene from the list, select it and press the Delete key on your keyboard.
When you select Build or Build and Run, Unity creates a build that includes all Scenes in the Scenes in Build list. Unity uses the list of Scenes to determine the order that it loads the Scenes in. To adjust the order of the Scenes, drag them up or down the list.
The Platform pane lists all platforms available in your Unity Editor. The list displays the Unity icon next to the name of the platform currently selected as the target platform.
Unity determines the platforms available to you depending on the platform modules you have installed.
To install further platform modules to your Project, do the following:
To change the target platform (the platform you want to build for), select the platform you want to switch to, then select Switch Platforms. This might take some time, because Unity might need to re-import your Assets in formats that match your target platform.
When you select a platform, Unity displays a list of options that you can adjust for the build. Each platform has unique settings which are listed on each <platform-specific (anchor)> manual page.
Some platforms have specific Build Settings. This section outlines the differences between platform build requirements, and provides links to further documentation on platform-specific build settings. For settings that apply to all platforms, see the next section, Generic platform settings.
Select the PC, Mac and Linux Standalone build target to build standalone applications for most desktop platforms. For specific build settings, see PC, Mac, and Linux Standalone build settings.
The Universal Windows PlatformAn IAP feature that supports Microsoft’s In App Purchase simulator, which allows you to test IAP purchase flows on devices before publishing your application. More info
See in Glossary (UWP) is developed by Microsoft and is only available if you build your application on the Windows operating system. Select the Universal Windows Platform build target to run your build on Desktop, Xbox OneMicrosoft’s eighth generation video game console.
See in Glossary, and Hololens. For an overview of UWP functionality see Universal Windows Platform Getting Started.
For specific build settings, see Universal Windows Platform build settings.
Select the tvOS build target to build for the Apple TV platform. tvOS extends from the foundation of the iOSApple’s mobile operating system. More info
See in Glossary Platform, which is also an available build target.
For specific build settings, see tvOS build settings.
Select the iOS build target to build for iOS devices such as iPhones and iPads. You need to set up an Apple Developer account if you want to publish to iOS devices. However, you can use any Apple ID if you want to build to your own device for testing. For an overview of developing for iOS, see Getting Started with iOS development.
For specific build settings, see iOS build settings.
Select the Lumin build target to build for Magic Leap using the Lumin SDK. To build for Magic Leap, you need to register a Magic Leap creator account and download the Lumin SDK. For an overview on creating Magic Leap applications, see Partners - Magic Leap.
Select the Android build target to build for Android devices. To develop and build for Android, you need to complete a specific environment setup; to do this, follow the steps outlined in Getting started with Android development.
For specific build settings, see Building apps for Android.
See in Glossary API, and other web standards.
For specific build settings, see Building and Running a WebGL project.
To build to these consoles, you need to be a registered console developer. For more information, see the Platform module installation page.
The following settings apply to all platforms.
|Development BuildA development build includes debug symbols and enables the Profiler. More info
See in Glossary
|Enable this setting to include scripting debug symbols and the ProfilerA window that helps you to optimize your game. It shows how much time is spent in the various areas of your game. For example, it can report the percentage of time spent rendering, animating or in your game logic. More info
See in Glossary in your build. When you enable this, Unity sets the DEVELOPMENT_BUILD scripting define. You should use this setting when you want to test your application
|Autoconnect Profiler||Enable this setting to automatically connect the Unity Profiler to your build. This setting is only available if you enable Development Build.|
|Deep Profiling Support||Enable this setting to turn on Deep Profiling in the Profiler. This makes the Profiler instrument every function call in your application and returns more detailed profiling data. When you enable Deep Profiling Support, it might slow down script execution. This setting is only available if you enable Development Build.|
|Script debugging||Enable this setting to allow your script code to be debugged. Not available on WebGL. This setting is only available if you enable Development Build.|
|Scripts Only Build||Enable this setting to only rebuild the scriptsA piece of code that allows you to create your own Components, trigger game events, modify Component properties over time and respond to user input in any way you like. More info
See in Glossary in your application, and reuse data files from the build you previously executed. Before you can use this setting, you must build your whole Project once. The Scripts Only Build option significantly improves iteration times if you only changed the code in your application. This setting is only available if you enable Development Build.
CompressionA method of storing data that reduces the amount of storage space it requires. See Texture Compression, Animation Compression, Audio Compression, Build Compression.
See in Glossary Method (Not available on Lumin or WebGL platforms)
|Compress the data in your Project when you build the Player. This includes AssetsAny media or data that can be used in your game or project. An asset may come from a file created outside of Unity, such as a 3D Model, an audio file or an image. You can also create some asset types in Unity, such as an Animator Controller, an Audio Mixer or a Render Texture. More info
See in Glossary, ScenesA Scene contains the environments and menus of your game. Think of each unique Scene file as a unique level. In each Scene, you place your environments, obstacles, and decorations, essentially designing and building your game in pieces. More info
See in Glossary, Player settings, and GI data. Choose between the following methods:
|Default||On PC, Mac, Linux Standalone, and iOS, there is no compression by default. On Android, the default compression is ZIP, which gives slightly better compression results than LZ4HC, but data is slower to decompress.|
|LZ4||A fast compression format that is useful for development builds. For more information, see BuildOptions.CompressWithLz4.|
|LZ4HC||A high compression variant of LZ4 that is slower to build but produces better results for release builds. For more information, see BuildOptions.CompressWithLz4HC.|