System Requirements
In order to use version 4.x, your browser must meet certain system requirements.
Supported browsers
For the best performance, use the latest version of Chrome, Edge, Firefox or Safari.
- 2D: Modern browsers and IE11 is supported
- Chrome
- Edge
- Firefox
- Safari 9 and later
- iOS Safari
- IE11
- 3D: supported in desktop web browsers that support WebGL - a web technology standard for rendering 3D graphics
- Chrome
- Edge
- Firefox
- Safari 9 and later
- IE11*
- See the Scene Viewer topic for additional information.
The WebGL implementation of Internet Explorer is not optimized for memory-intensive applications and it might not work reliably when opening certain scenes.
Hardware requirements for 3D
Your computer hardware needs to have a minimum of 2 GB system memory and a video graphics card that supports WebGL. It is recommended that you have at least 4 GB of system memory.
Your hardware should have a nonmobile 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 scenes. Nonmobile versions of graphics cards typically have better performance than mobile graphics cards (denoted with m or mobile). To get more detailed information about WebGL requirements, visit WebGL troubleshooting.
Note that there is no current 3D support for mobile devices or iPad.
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://. Web server software is available free of charge for all operating systems. For Windows, IIS is recommended. On Mac OS and Linux, Apache is a popular option but any web server will do.
As a side note, a web server is not necessary when the ArcGIS API for JavaScript is used in embedded scenarios, e.g. Microsoft PowerBI, Windows Store app, or Adobe Creative Cloud.
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 and Track widget doesn't work on insecure origins.