System Requirements

Supported browsers

For best performance, we recommend the 64-bit version of the latest modern, standards-based browsers.

The API targets the latest two versions of Chrome, Firefox, and Edge, and the latest two major versions of Safari and iOS Safari, and the most recent Firefox ESR.

For version 4.19 this means:

  • Chrome 89-90
  • Edge 89-90
  • Firefox 87-88
  • Firefox 78
  • iOS Safari 13.0-14.4
  • Safari 13-14

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) was 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.

SceneView is only supported on displays with a resolution up to 4K.

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.

Starting with API version 4.18, semi-transparent symbol rendering is improved, using order-independent transparency. This algorithm requires two WebGL extensions which are not supported across all devices. To test if a device supports the new transparency algorithm, open webglreport.com on the device's browser and check if OES_texture_float and WEBGL_color_buffer_float are available in the extensions list. On unsupported devices, the old algorithm is used.

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.