Developer Changelog / Admin ยท Polaris

The Shopify admin gets a new look
Apps either "update automatically" or "opt into Polaris 2.0 themselves"

Starting September 15, 2026, the admin's new look rolls out gradually. Admin UI extensions and App Home UI extensions get the new style automatically. Apps that render their own UI in App Home keep their current style until they migrate to Polaris 2.0.

On this page
  1. What's changing (in 30 seconds)
  2. 3 changes merchants will see
  3. Impact by app type (diagram)
  4. Impact comparison table
  5. Rollout and Polaris versions
  6. Decision flow: what to do
  7. 5 key points for developers
  8. 3 business use cases
  9. One-line summary for proposals

1What's changing

The Shopify admin's own look (colors, typography, spacing, icons, and frame) is being refreshed .
How this affects apps depends on how they're built.UI extensions update automatically; custom UI in App Home stays as is(it switches to the new style only when you adopt Polaris 2.0).

New style automatically

Admin UI extensions / App Home UI extensions. Functionality stays the same, and no extension code changes are needed.

Unchanged until you opt in

Embedded apps that render their own interface in App Home. They keep their current style until they adopt Polaris 2.0.

23 changes merchants will see

Aa

A new look on every page

New colors, typography, spacing, and icons, shown inside a new frame.

Consolidated in the side nav

Search, notifications, and store switching move to the side nav. The side nav can be collapsed to give pages more room.

Sidekick goes floating

Sidekick moves from a side panel to a chat that floats at the bottom of the page.

3Impact by app type (diagram)

The new admin Phased rollout from Sep 15, 2026 Admin UI ext / App Home UI ext Provides UI as extensions Embedded App Home + Polaris WC 1.0 Already on Polaris Web Components Embedded App Home (not using Polaris WC) Renders its own UI New style applied automatically No action needed; functionality unchanged Stays as is (opt-in) Choose whether and when to move to Polaris 2.0 Stays as is (new design not applied) Migrating to Polaris WC comes first
The key question is "whether your app is built on Polaris Web Components". The article states that migrating to Polaris WC is what puts you in a position to adopt Polaris 2.0 (the new design).

4Impact comparison

How the app is builtNew style appliedAction required
Admin UI extensions / App Home UI extensions Automatic Applied once the refreshed admin reaches the shop None No code updates, no functional changes
Embedded App Home (using Polaris Web Components 1.0) Opt-in Stays as is until you move to Polaris 2.0 You decide whether and when to adopt it
Embedded App Home (not using Polaris Web Components) Not applied Keeps the current style To get the new design, start by migrating to Polaris WC

5Rollout and Polaris versions

Currently RC Polaris WC 1.1 RC 2026/9/15 New admin rollout begins Gradually to merchants Coming soon (no date given) Polaris 2.0 RC available Styles that align App Home with the new admin Completion date: not specified

Old and new coexist during the transition

During the rollout, the same app may appear in either the old or the new admin, depending on the merchant's shop.

Adopting the major version is explicit

With semantic versioning on the Polaris CDN, adopting a new major version is an explicit choice.Merchants never see a partially updated app.

6Decision flow: what to do

1

Apps with only UI extensions

No action needed. The new styles are applied automatically.

2

Path A: Prepare for Polaris 2.0

If you migrate to Polaris Web Components now, you can try the new styles with minimal changes once the 2.0 RC is released.

3

Path B: Keep the current styles

Do nothing. Your app won't move to Polaris 2.0 on its own.

No app needs to take action until the Polaris 2.0 RC is available. There's no need to rush any changes.

75 key points for developers

1. UI extensions update with no code changes

Admin UI extensions and App Home UI extensions are styled by the platform, so they get the new look without touching your extension code. Functionality stays the same.

2.0

2. Polaris 2.0 is opt-in

With semantic versioning on the Polaris CDN, adopting a major version is explicit. Your app won't switch to 2.0 on its own, and merchants won't see a partially updated state.

Old New

3. The old and new admin coexist

Because of the phased rollout, the same app may appear in either the old or the new admin. Account for both when checking your UI and handling support.

4. Polaris Web Components is the prerequisite

Embedded apps that don't use Polaris WC won't receive the new design. Migrating to Polaris WC is the foundation for adopting 2.0. The current RC is 1.1.

5. No deadlines or schedule details given

The article doesn't state when the Polaris 2.0 RC will be available, when the stable release will ship, when the rollout will finish, or when Polaris 1.x support will end.No action is needed until the 2.0 RC is availableis all it explicitly says.

83 practical use cases

USE CASE 1

Complete an impact inventory of your apps using 3 categories

Challenge
You manage multiple apps or stores and can't clearly explain to stakeholders which ones will change in the new admin and which won't.
Approach
Classify each app as "UI extensions only," "App Home on Polaris WC 1.0," or "App Home without Polaris WC," then apply the article's guidance directly.
Impact
You can share, with clear reasoning, that no app needs immediate action, avoiding unnecessary emergency fixes.
Technical note
The article explicitly says no action is needed until the 2.0 RC is available. A classification table will help you decide what to do once the RC ships.
Custom UI Polaris WC
USE CASE 2

Plan a migration of custom-UI embedded apps to Polaris WC

Challenge
Your App Home UI is built without Polaris WC, so your app may look out of place inside the new admin.
Action
Migrate to Polaris Web Components first, so you can try the new styles with minimal changes once the 2.0 RC is available ("Path A" in the article).
Impact
Once the 2.0 RC is available, you can quickly match the look of the new admin.
Technical notes
The article doesn't cover the migration effort or specific steps. It points to the App Home documentation and Polaris 1.1 RC as references.
Old New ?
USE CASE 3

Update support docs and manuals so they work for both the old and new admin

Challenge
During the rollout, merchants see different versions of the admin, which may lead to questions like "Where are search and notifications?" or "Sidekick disappeared."
Action
Add notes to user manuals and support answers explaining that in the new admin, search, notifications, and store switching are in the side navigation, and Sidekick is a floating chat at the bottom of the page.
Impact
Support runs more smoothly while the old and new admin coexist.
Technical notes
App functionality doesn't change (UI extensions). Only the admin frame and visual design change, so explanations can focus on where things moved on screen.

9One-line summary for proposals

"With the admin's new design,UI extensions adapt automatically, with no changes needed..
Custom UI in App Home stays as-is until you choose to adopt Polaris 2.0..
If you want to match the new design, the fastest path is to move to Polaris Web Components now."