Developer / Polaris Web Components

Polaris 2.0 Release Candidate
Match your app's look to the new admin design

The Polaris 2.0 RC is now available for embedded App Home. It brings the new Shopify admin's colors, typography, spacing, and icons. It automatically renders in the old or new design to match each store, so a single app can support both.

On this page
  1. What was released (in 30 seconds)
  2. How it works: which look gets rendered
  3. Adoption is explicit: it doesn't switch automatically
  4. Timeline and the Built for Shopify deadline
  5. How to test (3 steps)
  6. What to do for each migration pattern
  7. 5 key points for developers
  8. 3 business use cases
  9. One-line summary for proposals

1What was released

Starting September 15, 2026,the new Shopify admin designhas been gradually rolling out to merchants.
The Polaris 2.0 release candidate (RC)lets you align your embedded App Home UI with that new design.

Scope: embedded App Home

Applies to the app home page (App Home) embedded in the admin.

Aa

Contents: new visuals

The new admin's colors, typography, spacing, and icons come to Polaris Web Components.

Key feature: one app supports both

Stores on the old design render the old style; stores on the new design render the new style.

2How it works: which look gets rendered

Your app Loads polaris-2.0-rc.js Inside the admin of a store on the new design store has the new Shopify admin design Inside the admin of a store on the old design store has the previous admin design Outside the Shopify admin rendered outside the Shopify admin New style New colors, typography, spacing, and icons Classic style Same look as polaris-1.js New style (default) Can be checked without a store on the new design
The look is switched byThe current admin design of each storeis followed. Your app doesn't need to detect the design or branch on it.
When rendered outside the admin, components use the new style, soyou can try the new look even if you don't yet have access to a store with the new design.

3Adoption is explicit: it won't switch automatically

Loaded scriptUses Polaris 2.0?Appearance
polaris.js(legacy URL) No Doesn't automatically migrate to Polaris 2.0
polaris-1.js No Doesn't automatically migrate to Polaris 2.0
polaris-2.0-rc.js Yes Shows the new or old style to match the store's design
If you do nothing, the appearance stays the same.To match the new design, you need to update the CDN URL yourself.

4Timeline and Built for Shopify deadline

2026/09/15 New admin design phased rollout begins 2026/09/24 Polaris 2.0 RC released (this article) Preparation period: old and new designs coexist 2027/05/01 Built for Shopify deadline
Built for Shopify apps

Must comply by May 1, 2027

The embedded App Home UI must be updated to match the Shopify admin's visual style.

Benefits of using the RC

Prepare ahead during the rollout

Components adapt to the design available in each store, so a single app can support merchants on either design.

The release date of the stable (non-RC) Polaris 2.0 and when the rollout will be complete arenot stated in the article.

5Testing steps (3 steps)

Load the release candidate from the Shopify CDN:

<script src="https://cdn.shopify.com/shopifycloud/polaris-2.0-rc.js"></script>

Then check behavior and appearance in the following three environments.

1
NEW

A store with the new design

If you don't have one, create a new store with the "Shopify admin's new design" feature preview enabled.

2
OLD

A store with the old design

Check that it looks the same as with polaris-1.js.

3

Outside the Shopify admin

Confirm that components render in the new style (the default).

Fixed / sticky UI Sidekick bar safe-area

Apps with UI fixed to the bottom of the screen need attention

To keep the floating Sidekick barfrom covering your UI, use the Environment API CSS variable --shopify-safe-area-inset-bottom .

Applies to: apps that place fixed or sticky content near the bottom of the viewport.

6What to do for each migration path

Pattern A

Already using Polaris Web Components

Just swap the CDN URL for the release candidate and test your existing UI.

Pattern B

Using Polaris React

Migrate to Polaris Web Components by following the migration guide. Start with Page / Section / Button first. It's the component whose appearance changes the most under the new design.

Pattern C

Not using Polaris Web Components

To adopt Polaris 2.0, you first need to migrate to Polaris Web Components.

Extensions adapt automatically.Admin UI extensions and App Home UI extensions automatically match the admin design available to each merchant. Functionality stays the same, and you don't need to update extension code to get the new style.

75 key points for developers

opt-in

1. Switching is opt-in

polaris-1.js and legacy polaris.js won't switch to 2.0 automatically.polaris-2.0-rc.js must be loaded explicitly. Only apps that do so are affected.

2. Polaris handles the old/new switch

Components change their appearance based on the store's admin design. Your app doesn't need any design detection or conditional logic.

3. The new style is the default outside the admin

Anything rendered outside the admin, such as in a local environment or Storybook, uses the new style. You can check the look even without a store on the new design.

4. Keep bottom-fixed UI clear with safe-area variables

--shopify-safe-area-inset-bottom(Environment API) to avoid overlapping with the floating Sidekick bar.

RC

5. Currently at the "release candidate" stage

The URL name is polaris-2.0-rc.js. The article doesn't give the stable release URL or release date. For versioning, see the related doc "Polaris CDN semantic versioning".Extensions (Admin UI / App Home UI extensions) adapt automatically with no code changes, so the only UI you need to work on is App Home itself.

83 practical use cases for your business

2027/05/01
USE CASE 1

Getting ahead of the change to protect your Built for Shopify badge

Challenge
Built for Shopify apps must align their embedded App Home with the admin's visual style by May 1, 2027.
Approach
Swap the CDN URL to polaris-2.0-rc.js , then test in three environments: the new design, the old design, and outside the admin.
Impact
Get ready early while the rollout is underway, and support merchants on either design with a single app.
Tech notes
If you don't have a store on the new design, create a new store with the "Shopify admin's new design" feature preview enabled.
React Web Comp.
USE CASE 2

Phased migration plan for Polaris React apps

Challenge
App Home is built with Polaris React, so it can't adopt Polaris 2.0 as is.
Approach
Follow the migration guide to move to Polaris Web Components, starting with Page, Section, and Button.
Impact
Starting with the components that most affect the look lets you close the gap with the new design quickly.
Tech notes
Migrate to Web Components first, then swap the CDN URL to the RC. No changes are needed to extension code.
USE CASE 3

Preventing bottom-fixed save bars and CTAs from being hidden by Sidekick

Challenge
App Home has a fixed save button or action bar at the bottom of the screen, which the floating Sidekick bar may cover.
Approach
For bottom spacing on fixed/sticky elements, use the Environment API's --shopify-safe-area-inset-bottom .
Impact
Avoids UI bugs where action buttons are hidden and can't be clicked.
Tech notes
The article doesn't specify the exact CSS variable syntax or values. Check the Environment API documentation.

9One-line summary for proposals

"Just swap the CDN URL to polaris-2.0-rc.js and App Home automatically follows each store's new or old admin design.
Switching is opt-in, extensions follow automatically, and the Built for Shopify deadline is May 1, 2027.
Now, during the rollout, is the time to start testing and migrating off Polaris React."