Build your WebGL application

To create a build for WebGL, go to File > Build Settings from Unity’s main menu. In the Platform list, select WebGL and then click Switch Platform.

When you have configured the Build Settings, choose from one the following options:

• Build: Builds your application into a Player.
• Build and Run: Builds your application in a Player, and opens that Player on your target platform.

The Unity build system for WebGL supports the following settings:

For changing the settings for Asset Import Overrides, refer to Build Settings.

Build folder structure

When you build your WebGL application, Unity creates a Build folder with the name you specify in the Build Settings window. The Build folder has the following files, where [ExampleBuild] represents the name of the target build folder.

If you enable a Compression Method for your build, Unity identifies the extension that corresponds with the compression method and adds this extension to the names of the files inside the Build sub folder. If you enable Decompression Fallback, Unity appends the extension .unityweb to the build file names. Otherwise, Unity appends the extension .gz for the Gzip compression method, or .br for the Brotli compression method. For more information, refer to Compressed builds and server configuration.

If you enable Name Files As Hashes in the Player Settings, Unity uses the hash of the file content instead of the default file name. This applies to each file in the build folder. This option allows you to upload updated versions of the game builds into the same folder on the server, and only upload the files which have changed between build iterations.

ノート: ファイルシステムから直接プレイヤーを開くと、ブラウザーによっては動作しないことがあります。これは、ローカルファイルの URL に適用されるセキュリティ制限によるものです。

Enable exceptions

Use Enable Exceptions to specify how to handle unexpected code behavior (also known as errors) at runtime.

1. To access Enable Exceptions, go to the WebGL Player Settings > Publishing Settings section.

2. In the Enable Exceptions option, choose from the following options:

   • None: Select this if you don’t need any exception support. This gives the best performance and smallest builds. With this option, any exception thrown causes your content to stop with an error.

   • Explicitly Thrown Exceptions Only (default): Select this to capture exceptions which are explicitly specified from a throw statement in your scripts and to also to make sure finally blocks are called. Note that selecting this option makes the generated JavaScript code from your scripts longer and slower; This might only be an issue if scripts are the main bottleneck in your project.

   • Full Without Stacktrace: Select this option to capture:

     • Exceptions which are explicitly specified from throw statements in your scripts (the same as in the Explicitly Thrown Exceptions Only option)
     • Null 参照
     • 範囲外の配列アクセス

   • Full With Stacktrace: This option is similar to the earlier option, but it also captures Stack traces. Unity generates these exceptions by embedding checks for them in the code, so this option decreases performance and increases browser memory usage. Only use this for debugging, and always test in a 64-bit browser.