{"id":1840282,"date":"2023-02-27T10:56:00","date_gmt":"2023-02-27T18:56:00","guid":{"rendered":"https:\/\/www.esri.com\/arcgis-blog\/?post_type=blog&p=1840282"},"modified":"2025-09-11T22:06:01","modified_gmt":"2025-09-12T05:06:01","slug":"arcgis-api-for-javascript-version-3-x-retirement","status":"publish","type":"blog","link":"https:\/\/www.esri.com\/arcgis-blog\/products\/js-api-arcgis\/developers\/arcgis-api-for-javascript-version-3-x-retirement","title":{"rendered":"ArcGIS API for JavaScript, Version 3.x Retirement"},"author":4271,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","format":"standard","meta":{"_acf_changed":false,"_searchwp_excluded":""},"categories":[738191],"tags":[],"industry":[],"product":[36831,36601],"class_list":["post-1840282","blog","type-blog","status-publish","format-standard","hentry","category-developers","product-js-api-arcgis","product-developers"],"acf":{"short_description":"ArcGIS API 3.x for JavaScript retires July 2024: Read about what this means and begin building apps with the ArcGIS Maps SDK for JavaScript.","flexible_content":[{"acf_fc_layout":"content","content":"

ArcGIS API 3.x for JavaScript<\/a> was retired on July 1, 2024.<\/p>\n

Fifteen years ago, Esri released the first version of the ArcGIS API for JavaScript, which developers have been using to build powerful web mapping applications throughout dozens of industries, across the globe. The API\u2019s original code base was not only used by the developer community, but also powered the web mapping experience in ArcGIS Online, ArcGIS Enterprise, and web mapping applications available with ArcGIS. In 2016, we introduced a more powerful, performant, and modern 2D\/3D API with a completely new code base \u2013 version 4.x (now called ArcGIS Maps SDK for JavaScript<\/a> or simply, JavaScript Maps SDK). Initially, the development team split their efforts between continuing to enhance 3.x, meanwhile progressing JavaScript Maps SDK with redesigned, modernized capabilities. Over time, we drastically reduced our focus on 3.x and eventually all new innovation was introduced in JavaScript Maps SDK, with only minor updates and critical bug fixes released with version 3.x. Over the last few years, we have been encouraging developers to build all new apps using the JavaScript Maps SDK and consider migrating 3.x-based apps.<\/p>\n

FAQ<\/h1>\n

What happens when ArcGIS API 3.x for JavaScript is retired? <\/strong><\/p>\n

Once version 3.x is retired, there will be no further bug fixes or enhancements to the API and hence no further 3.x API deployments to js.arcgis.com. In addition, technical support will no longer be available. Please refer to the Product Lifecycle Support Policy<\/a>.<\/p>\n

What are the risks of using ArcGIS API 3.x for JavaScript after retirement?<\/strong><\/p>\n

After retirement, the 3.x API will remain hosted on our CDN for a multi-year grace period so that apps that have already been deployed which have a dependency on the API will not break. However, browser updates may introduce new issues to apps running on the 3.x API, resulting in performance issues, feature malfunction, or even crashing applications. After retirement, there will be no further bug fixes, patches, and enhancement to the API, and technical support will also no longer be available, per the Product Lifecycle Support Policy<\/a>.<\/p>\n

Therefore, even though your apps may still work after the retirement, we strongly encourage developers to migrate to the version 4.x –\u00a0 ArcGIS Maps SDK for JavaScript – to mitigate risks and enjoy the outstanding performance and all the new features of a modern JavaScript mapping library.<\/p>\n

What action should I take to mitigate the impact of this product retirement?\u00a0<\/strong><\/p>\n

Custom web apps should be migrated and, in most cases, rewritten to use the JavaScript Maps SDK as soon as possible. This way, apps will benefit from superior performance, capabilities, and other aspects that are based on modern browser technology. Also, because it is our active code base, we will address issues found in the API and introduced by browser updates.<\/p>\n

Esri highly encourages that a<\/span>pps <\/span>created using Esri\u2019s configurable apps and builders<\/span> that are based on 3.x should be migrated to <\/span>options<\/span> that are based on the <\/span>ArcGIS Maps SDK for <\/span>JavaScript, <\/span>if possible. For example, when possible, apps built on ArcGIS Web AppBuilder and ArcGIS Configurable Apps can move to ArcGIS Experience Builder and\/or ArcGIS Instant Apps.
\n<\/span><\/p>\n

When will ArcGIS Web AppBuilder retire?<\/strong><\/p>\n

There are three editions of ArcGIS Web AppBuilder.<\/p>\n