Unity 6.6 expands the options for browser-game builds

Unity's September 1 release announcement marks WebGPU as ready for production use in Unity 6.6 web builds. Developers must opt in: WebGL 2 remains the default, with a fallback for browsers and devices that lack WebGPU support.

The release also introduces Progressive Asset Loading. Instead of requiring the whole asset set before startup, a build can download what its first scene needs and load later scenes during play. Unity says the existing SceneManager and Addressables interfaces continue to work.

These features address separate problems. A newer graphics interface can expand rendering options, while a smaller initial download can reduce the wait before interaction. Neither removes the need to test the intended browser and device combinations.

Teams evaluating the release should check both paths: the enhanced rendering configuration and the fallback experience. They should also measure an uploaded build on realistic connections. Unity's announcement describes available capabilities; it does not establish a performance improvement for every project.