Experience Editor Is Going Away in SitecoreAI

Experience Editor Is Going Away. Page Builder Is Finally Ready to Take Over.

If you've run on Sitecore for any length of time, Experience Editor is muscle memory. It's how a generation of authors learned the platform. So here's the news: effective January 1, 2027, Experience Editor will be officially deprecated, and Page Builder becomes the supported editing experience in SitecoreAI. SitecoreXP is fine, don't worry, nothing will break.

We are not worried about that date.

When Page Builder first shipped, plenty of teams still needed Experience Editor for specific workflows, maybe for legacy support for ported over sites or familiarity or solutions built around EE, whatever it was.

Over the past few years Sitecore has filled any gaps that existed between the old experience and new Page Builder, one by one, based on what teams actually asked for and authors needed. The Page Builder you'd move to today is not the one you tried and shelved two years ago because it felt "not ready". OH, it's ready. 

Here's where Page Builder stands, and what each piece replaces:

• Custom editing interfaces: Marketplace Custom Fields let developers build tailored UI components and rendering parameters right in Page Builder. That's the flexibility for business-specific fields people kept requesting.
• A modern developer foundation: the Content SDK replaces the legacy approaches with a stable, cloud-native base. Paired with Local Editing Host, teams are building enterprise-grade pages about 3× faster.
• Real inline editing: an enhanced floating panel handles inline text editing, configurable toolbars, direct item editing, and drag-and-drop component management, all without leaving the canvas.
• Layers: clear visibility into page hierarchy and structure, which authors have wanted for a long time.
• Personalization and A/B testing on-canvas: with analytics built into the authoring flow instead of bolted on after.
• Content mode: a full-screen, distraction-free space for creating, finding, and editing content items and datasources, with guided creation and search. No more bouncing out to Content Editor.
• Publishing controls that make sense: unpublish a page directly without deleting it, keep every version intact for reuse, and read live status at a glance with draft, approved, live, and scheduled badges.

That list covers the workflows that used to be the reason to stay on Experience Editor. The reason is gone.

One caveat I want to flag loudly. If you're still running JSS in Chromes mode, you'll effectively lose your only WYSIWYG editor, because Page Builder supports Metadata mode only. If that's you, this is the line item that jumps to the top of your migration plan. Don't let it surprise you in December.

On timing, my advice is simple. Don't read "2027" as "later." Read it as "now." Teams that treat a deprecation date as a deadline scramble in Q4. Teams that treat it as a runway move at a comfortable pace and find their edge cases before the clock starts. The Page Builder readiness recipe and its documentation are there to make the move smooth, and so are we.

This is a non-event if you plan for it and a fire drill if you don't. If you want a second set of eyes on your path, especially if you're on JSS Chromes mode, reach out. Better to map it together now than to rush it next December.