Web AppBuilder Retirement 2026–2027: Dates, Options and Checklist

Web AppBuilder apps in ArcGIS Online can no longer be updated from Q4 2026 and stop working in Q2 2027. Dates, replacement options and a migration checklist.

By Ahsan Mukhtar, CEO and Managing Director

Key takeaways

  • In ArcGIS Online, Web AppBuilder apps can no longer be updated from Q4 2026 and stop working in Q2 2027.
  • ArcGIS Enterprise 11.5 is the last release that includes Web AppBuilder, so upgrading beyond it means migrating first.
  • Web maps carry over unchanged, but custom widgets and themes cannot be converted and must be rewritten for Experience Builder.

Esri is retiring ArcGIS Web AppBuilder. In ArcGIS Online, existing Web AppBuilder apps can no longer be updated from Q4 2026, and they stop working in Q2 2027. In ArcGIS Enterprise, version 11.5 is the last release that includes it. If your organisation still runs Web AppBuilder apps, the practical answer is to inventory them now, decide which to retire, and rebuild the rest, most often in ArcGIS Experience Builder.

The retirement dates

PlatformWhat changesWhen
ArcGIS OnlineYou can no longer create new Web AppBuilder appsQ1 2026
ArcGIS OnlineYou can no longer update existing appsQ4 2026
ArcGIS OnlineExisting apps are retired and no longer functionQ2 2027
ArcGIS Enterprise11.5 is the last release with Web AppBuilderApplies when you upgrade beyond 11.5

These dates come from Esri's retirement notice. Esri has deprecated Web AppBuilder in ArcGIS Enterprise since March 2023.

Why it matters now

Once updates are switched off, an app is frozen. You cannot fix a broken layer reference, change a filter or add a new data source, even if the app still loads. That leaves a short window to plan and rebuild before Q2 2027, when the apps stop working altogether.

Public-facing apps carry the most risk. A council property viewer, a utility outage map or a planning portal that fails takes a public service down with it, and links to it may be printed in documents, embedded in websites or saved by users.

Your three replacement options

OptionBest forWatch out for
ArcGIS Experience BuilderMost Web AppBuilder apps, especially those with several widgets, pages or custom behaviourCustom widgets and themes must be rewritten
ArcGIS Instant AppsSimple viewers with a map, a legend, search and a few toolsLimited customisation; a complex app may not fit
A custom app on the ArcGIS Maps SDK for JavaScriptProducts with workflows that go well beyond a configurable appMore development and maintenance than a configured app

Some apps fit an ArcGIS Dashboard better than a map app, and some are simply no longer used. Retiring those is the cheapest migration there is.

What carries over, and what does not

  • Web maps, layers and pop-ups carry over. They are separate items, and Experience Builder uses them as they are.
  • Standard widgets mostly have equivalents. Esri publishes a widget functionality matrix. Check each widget your apps use, because some have no direct match.
  • Custom widgets and themes do not convert. Esri states that direct conversion is not possible. Web AppBuilder runs on the ArcGIS API for JavaScript 3.x, and Experience Builder uses the ArcGIS Maps SDK for JavaScript 4.x, so custom code is rewritten.
  • App URLs change. Every link, embed, QR code and bookmark that points at an old app needs updating.

A checklist to audit your apps

  1. List every Web AppBuilder app in your ArcGIS organisation, with its owner.
  2. Record how much each app is used, and whether it is public or internal.
  3. Note the widgets each app uses, and mark any custom widgets or themes.
  4. Find where each app is linked or embedded: websites, documents, intranet pages, other apps.
  5. Decide per app: retire, replace with an Instant App or Dashboard, or rebuild in Experience Builder.
  6. Put the public-facing and custom-widget apps first, because they take longest and carry most risk.
  7. Set a cut-over date for each app, well before Q2 2027.

Common traps

  • Leaving custom widgets to last. They are the slowest part of most migrations, and the person who wrote them may have left.
  • Rebuilding everything. An inventory often shows apps nobody opens. Retire them instead.
  • Forgetting embeds. An app embedded in a website breaks silently when the old app is retired.
  • Upgrading Enterprise first. Upgrading beyond 11.5 before migrating removes Web AppBuilder while your apps still depend on it.

Where to get help

The migration itself follows Esri's documented steps: assess the app, create an Experience Builder app, add the data, reconfigure the widgets, test and share. Most of the effort sits in the inventory and the custom widgets.

If you want a team to take this on, our Web AppBuilder migration service covers the inventory, rebuild and cut-over, and our Experience Builder widget development rewrites custom widgets on the current SDK.

Frequently asked questions

When does Web AppBuilder stop working?

In ArcGIS Online, existing Web AppBuilder apps are retired and stop working in Q2 2027. From Q4 2026 they can still be opened but no longer updated.

Is Web AppBuilder deprecated or retired?

Both, on different platforms. Esri has deprecated Web AppBuilder in ArcGIS Enterprise since March 2023, and 11.5 is the last Enterprise release that includes it. In ArcGIS Online it is being retired on the schedule above.

Can Web AppBuilder apps be converted to Experience Builder automatically?

Not fully. Web maps, layers and pop-ups carry over, and many standard widgets have equivalents, but custom widgets and themes have to be rewritten for the ArcGIS Maps SDK for JavaScript 4.x.

What is the replacement for Web AppBuilder?

ArcGIS Experience Builder is Esri's main replacement. ArcGIS Instant Apps and ArcGIS Dashboards suit simpler apps, and a custom app on the ArcGIS Maps SDK for JavaScript suits products that go beyond a configurable app.

Summary

Web AppBuilder apps in ArcGIS Online can no longer be updated from Q4 2026 and stop working in Q2 2027. ArcGIS Enterprise 11.5 is the last release that includes Web AppBuilder. Start with an inventory, retire what nobody uses, and rebuild the rest in Experience Builder, beginning with public-facing apps and any app with custom widgets.

References and further reading

Working on something similar? Jugrafiya builds GIS products, spatial data pipelines and the web and mobile software around them.

Talk to an engineer