---
title: Migrate Spinner from Polaris React
description: Learn how to migrate Polaris React Spinner to Polaris web components.
source_url:
  html: >-
    https://shopify.dev/docs/apps/build/app-home/migrate-from-polaris-react/spinner
  md: >-
    https://shopify.dev/docs/apps/build/app-home/migrate-from-polaris-react/spinner.md
api_name: app-home
---

# Migrate Spinner from Polaris React

Use `s-spinner` for indeterminate progress in a bounded region. Pair it with text when the operation or wait state isn't obvious.

***

## Choose the destination

| Polaris React | Polaris web components | Migration type |
| - | - | - |
| `Spinner` | [`s-spinner`](https://shopify.dev/docs/api/app-home/web-components/feedback-and-status-indicators/spinner) | Direct |

***

## Map spinner properties

| Polaris React | Polaris web components | Migration notes |
| - | - | - |
| `accessibilityLabel` | `accessibilityLabel` | Name the operation, such as "Loading products", not the spinner itself. |
| `size="small"` | `size="base"` | Use for inline or compact feedback. |
| `size="large"` | `size="large"` or `size="large-100"` | Use for a larger standalone loading state. |

***

## Migrate the call site

1. Inventory every `Spinner` call site and record the content, state, events, and accessibility behavior it uses.

2. Open the linked Polaris web component reference and map only documented properties, slots, and events.

3. Move unsupported responsibilities into adjacent content or app state instead of passing old props through.

4. After verification, remove the `Spinner` import and any Polaris-only state, wrappers, or helpers that no longer have a caller.

***

## Preserve these behaviors

* Accessible names, semantics, and keyboard behavior.
* Visible content plus disabled, loading, selected, or error state that affects the task.
* Click, change, submit, and navigation behavior used by app logic.

***

## Test and remove Polaris React

Test every migrated `Spinner` state used by the app. For interactive destinations, verify keyboard operation, focus, and accessible naming. For content destinations, verify document structure and alternative text where applicable. Compare behavior rather than pixel-for-pixel styling.

Don't remove `@shopify/polaris` while another component still imports it. Once all call sites are migrated, remove the package and its provider-level setup, then run the app's full test suite.

***

## Migration example

## Migrating Spinner

##### Polaris web components

```tsx
export function SpinnerMigrationExample() {
  return (
    <><s-spinner accessibilityLabel="Loading products" size="large"></s-spinner></>
  );
}
```

##### Polaris React

```tsx
import {Spinner} from '@shopify/polaris';


export function SpinnerMigrationExample() {

  return (
    <Spinner accessibilityLabel="Loading products" size="large" />
  );
}
```

***