Supported browsers
For best performance, we recommend the 64-bit version of the latest modern, standards-based browsers:
- Chrome
- Firefox
- Microsoft Edge
- Safari
Only WebGL-enabled browsers are supported. Please use the latest versions of the browsers listed above.
About Internet Explorer 11
Support for Internet Explorer 11 (and Microsoft Edge Legacy) is discontinued as of version 4.18.
Hardware requirements
For desktop browsers, it is recommended to have at least 8 GB system memory and modern graphics hardware for both 2D and 3D.
Minimum requirements are a high-performance graphics card with at least 512 MB of video memory. For the best performance, it is recommended that you have a graphics card with at least 1 GB of video memory, especially for working with larger or more memory-intensive 3D scenes. High-performance, stand-alone graphics cards typically have better performance than integrated graphics cards. To get more detailed information about WebGL requirements, visit the khronos.org WebGL wiki.
Mobile devices should have a minimum of 2GB of RAM (4 GB recommended), a powerful multi-core processor and graphics card, and the latest Android or iOS version installed.
3D mobile capabilities are currently only supported on the following devices. To determine if an issue is related to mobile hardware or the browser, it is recommended to first attempt to reproduce the issue on one of the supported desktop browsers listed above.
- iOS Safari on iPhone 8, iPhone XS, iPhone 11, iPad Pro
- Android Chrome on Samsung S9, Samsung S10, Samsung S20, Samsung Tab S3, Samsung Tab S4
When using a Virtual Desktop Infrastructure (VDI), the virtual desktop client will need access to the hardware requirements listed above for desktop browsers. It is also recommended that you use the client specifically designed for your VDI. You will need to test and potentially adjust the VDI configuration to get optimal visualization performance.
About web servers
If developing a traditional web application that is to be accessed via the browser, the recommended approach is to deploy it to a web server and access it via http:// or https:// rather than file://.
In embedded scenarios, e.g. Microsoft PowerBI, Windows Store app, or Adobe Creative Cloud, a web server is not necessary for using the ArcGIS API for JavaScript.
Feature-specific requirements
Some API classes and modules have additional system requirements which are noted on a class by class basis in the API reference. For example, due to security considerations the Locate widget and Track widget don't work on insecure origins. The Fullscreen widget only works with browsers that implement the Fullscreen API. Thus, iOS Safari is not supported.
Product Life Cycle
We recommend reviewing both the ArcGIS API for JavaScript's Product Life Cycle page and the Developer Technologies section in the Esri Product Life Cycle Support Policy document. They contain detailed information on specific API version release dates and the associated product life cycle phases.