Version: 2017.2 (switch to 2017.3b)
Getting started with WebGL development
Building and running a WebGL project
Other Versions

WebGL Browser Compatibility

Unity WebGL supports all major desktop browsers to some degree. However, the level of support and the expected performance varies between different browsers. See the table below for an overview of browser features of interest to Unity WebGL content, and which browsers support them.

Note that Unity WebGL content is not currently supported on mobile devices. It may still work, especially on high-end devices, but many current devices are not powerful enough and don’t have enough memory to support Unity WebGL content well. For this reason, Unity WebGL shows a warning message when trying to load content on mobile browsers (which can be disabled if needed).

Note that this compatibility table is valid for the specific versions of the browsers as stated. Support should continue for future versions, but may not be stable in previous versions.

Desktop browser compatibility table
Mozilla Firefox 52 Google Chrome 57 Apple Safari 11 MS Edge 16
WebGL Support Yes
GPU blacklists apply. WebGL may be unsupported for specific older graphics cards. Details available on the Mozilla wiki page on Blocklisting/Blocked Graphics Drivers and the Khronos wiki page on Blacklists and Whitelists.
Yes
GPU blacklists apply. WebGL may be unsupported for specific older graphics cards. Details available on the Mozilla wiki page on Blocklisting/Blocked Graphics Drivers and the Khronos wiki page on Blacklists and Whitelists.
Yes
Safari 8 and higher
Yes
Web Audio
(See Web Audio)
The Web Audio API is required to play sound in Unity WebGL content.
Yes Yes Yes Yes
Full-screen support
(See Full-screen support)
Yes Yes Yes
Safari 10.1 or newer
Yes
Cursor locking support
(see Cursor Locking support)
Yes Yes Yes Yes
Edge 13 and newer.
Gamepad support
(See Gamepad support)
Yes Yes Yes Yes
IndexedDB
Required for local storage as used by the Data Caching feature, the PlayerPrefs class, and WWW.LoadFromCacheOrDownload.
Yes
Firefox up to version 42 does not support IndexedDB for content running in an iFrame. Firefox 43 and higher fixes this.
Yes Yes
Safari does not support IndexedDB for content running in an iFrame.
Yes
WebSockets
Required for Networking.
Yes Yes Yes Yes
WebRTC
Required by the WebCamTexture class.
Yes Yes No Yes
WebGL 2.0
(See WebGL 2.0)
Yes
Firefox 51 and newer
Yes
Chrome 56 and newer
No No
asm.js AOT compilation
asm.js is a susbset of JavaScript for which a browser can specifically optimize. Browsers which implement asm.js support may be able to run Unity WebGL content faster, because Unity uses asm.js.
Yes No No Yes
WebAssembly
WebAssembly or wasm is a new portable, size-efficient and load-time-efficient format suitable for compilation to the web.
Yes
Firefox 52 and newer.
Yes
Chrome 57 and newer.
Yes
Safari 11 or newer
Yes
Edge 16 or newer
Large-Allocation Http header
Helps browsers make sure enough memory is available to load your content (See Large-Allocation Http Header)
Yes
Firefox 53 and newer.
No No No
Brotli Compression
Reduces build size (See Brotli compression)
Yes Yes No Yes

Notes

  • Chrome may need a large amount of memory to parse the generated JavaScript code, which can cause out-of-memory errors or crashes when loading content on 32-bit browsers. See Memory Considerations for more information on memory usage.




  • 2017–05–15 Page amended with no editorial review

  • Brotli compression first documented on this page in User Manual 5.6

Did you find this page useful? Please give it a rating:

Getting started with WebGL development
Building and running a WebGL project