Shopify's admin has a new look. Your app probably doesn't

On September 15, 2026, Shopify started rolling out a new look for the admin: new colour, type, spacing and icons, inside a new frame. Search, notifications and the store picker moved into a collapsible side panel, and Sidekick became a floating chat. Nine days later the Polaris 2.0 release candidate landed to match it.

Nothing about this breaks your app. That is exactly why it is worth your attention. A broken app files bug reports; an app that merely looks dated inside someone else's product does not. It just quietly stops feeling like part of the admin, one merchant at a time, on a rollout schedule you do not control.

What restyles itself and what does not

Shopify drew this line along its own component boundary, which is the tell for where the platform wants you to be. Anything rendered through Shopify's extension surfaces is Shopify's problem. Anything you rendered yourself is yours.

The part that catches people: both designs are live at once

The rollout is progressive. For months, some of your installs are on the new admin and some are still on the old one, and you do not get to know which is which. That turns a redesign into a harder problem than a redesign: your app has to look correct in two different admins simultaneously.

This is the actual argument for Polaris 2.0, and it is worth stating plainly because the changelog buries it. Load polaris-2.0-rc.js and the components render the new styles on a store with the new admin, the previous styles on a store that still has the old one, and the new appearance outside the admin entirely. One script, three contexts, handled. You are not choosing a look, you are delegating the choice to something that can see which store it is in.

Polaris CDN channels, and why you cannot pin 2.0 yet

The Polaris CDN adopted semantic versioning on August 31, and Polaris CDN 1.1 went stable on September 22. That gives you four kinds of URL, and they behave differently enough that picking the wrong one is a real incident waiting to happen.

1<!-- Legacy. Tracks polaris-1.js. -->2<script src="https://cdn.shopify.com/shopifycloud/polaris.js"></script>3 4<!-- Major channel. Compatible improvements arrive automatically,5     breaking majors do not. This is the sensible default. -->6<script src="https://cdn.shopify.com/shopifycloud/polaris-1.js"></script>7 8<!-- Pinned. Published only once 1.1 became stable. Never moves. -->9<script src="https://cdn.shopify.com/shopifycloud/polaris-1.1.js"></script>10 11<!-- Release candidate. Accumulates changes and updates IN PLACE. -->12<script src="https://cdn.shopify.com/shopifycloud/polaris-2.0-rc.js"></script>

Now the detail that decides your timing, which you will not find in the changelog. polaris-2.0-rc.js serves a 200. polaris-2.js serves a 404. There is no stable major-2 channel yet, so shipping the new look to production today means shipping a dependency on a release-candidate URL that Shopify says will accumulate improvements and update in place. That is fine in a staging store and an uncomfortable thing to have under a paying merchant's workflow.

If you are still on Polaris React

Shopify's own advice is to start with Page, Section and Button, on the grounds that they carry the most visual weight per component converted. That is sound, and there is a better reason for it than visual impact: those three are the components that establish the frame. Convert them and the rest of your screen inherits correct spacing and surface colour even where the inner components are still yours. Convert leaf components first and you get a page that is half new, half old, in a way that looks worse than either.

What to actually do this week

1. Find out which bucket you are in. Grep your app for @shopify/polaris and for a Polaris CDN script tag. React imports and no script tag means the longest road.
2. Open your app on a store with the new admin and look at it. Not a screenshot review, the actual app. The drift shows up at the edges: card surfaces, icon weight, the gap between your header and Shopify's.
3. Grep for hardcoded colour and spacing literals. Every one is a decision you made about an admin that is being replaced.
4. Check your CDN channel. If you are on the legacy polaris.js, move to polaris-1.js now. It is the same code today and a much better contract tomorrow.
5. Put May 1, 2027 in the calendar only if you are Built for Shopify. Everyone else has no deadline, which is precisely why this slips.

The broader read: this redesign is a quiet audit of how much of your interface you built yourself. Every custom component you were proud of is now a component you maintain against someone else's moving design system, forever. That trade is sometimes worth making. It is worth making on purpose.