To deploy a Web build, you must configure your server and make sure you're using the correct response headers, so that the browser receives a proper response and processes it correctly.

There are two main settings in Unity that affect how you set up the server:

Choose the compression type from the Web Player Settings window (menu: Edit > > Player, then select Web and expand the Publishing Settings section):

For more information on browser support for selected compression methods, refer to the documentation on Web browser compatibility.

You might need to adjust your server configuration to match your specific build setup. In particular, there might be issues if you already have another server-side configuration to compress hosted files, which could interfere with this setup. To make the browser perform decompression natively while it downloads your application, append a Content-Encoding header to the server response. This header must correspond to the type of compression Unity uses at build time. For code samples, refer to Server Configuration Code Samples.

The decompression fallback option enables Unity to automatically embed a JavaScript decompressor into your build. This decompressor corresponds to your selected compression method, and decompresses your content if the browser fails to do so.

Enable decompression fallback from the window (menu: Edit > Project Settings > Player, then select Web and expand the Publishing Settings section).

When you enable decompression fallback, Unity adds a extension to the build files. You should consider using Decompression Fallback if you have less experience with server configuration, or if server configuration is unavailable to you.

The Decompression Fallback option is disabled by default. Therefore, by default, build files include an extension that corresponds to the compression method you select.

There are two compression methods to choose from: gzip or Brotli. For further information refer to the compression format section.

To enable browsers to natively decompress Unity build files while they're downloading, you need to configure your web server to serve the compressed files with the appropriate HTTP headers. This is called native browser decompression. It's faster than the JavaScript decompression fallback, which can reduce your application's startup time.

The setup process for native browser decompression depends on your web server. For code samples, see Server Configuration Code Samples.

A Content-Encoding header tells the browser which type of compression Unity has used for the compressed files. This allows the browser to decompress the files natively.

Set the Content-Encoding response header to the compression method selected in the Player Settings.

Content-Encoding: gzip

Content-Encoding: br

WebAssembly streaming allows the browser to compile the WebAssembly code while it's still downloading the code. This significantly improves loading times.

For WebAssembly streaming compilation to work, the server needs to return WebAssembly files with an MIME type. To use WebAssembly streaming, you need to serve WebAssembly files with the response header. A Content-Type header tells the server which media type the content is. This value should be set to for WebAssembly files.

Content-Type: application/wasm

If your file contains JavaScript, you should add the Content-Type header. Some servers might include this automatically, while others don't.

Content-Type: application/javascript