Should I upgrade to MUI X 8 now?

Choose whether to move to MUI X 8 now that it supports Material UI 7 out of the box, or stay on an earlier MUI X line to avoid a broader frontend upgrade.

Hold on MUI X 7 unless you already need v8-only features or are ready to fund a Material UI 7 migration; move to MUI X 8 only with a coordinated frontend upgrade.

Blockers

Who this is for

Candidates

Upgrade to Material UI 7 and standardize on MUI X 8

MUI X v8 was released on 2025-04-17 and, as of 2026-04-08, the docs show the active v8 line with continuous support. MUI states that MUI X 8 supports Material UI 7 out of the box and moved its packages to the Node.js exports layout for better ESM integration. The official v7-to-v8 Data Grid migration guide also raises the minimum supported TypeScript version to v5 and provides codemods for many API changes. As of 2026-04-08, the pricing page lists Pro at $299 per developer per year, Premium at $599 per developer per year, and Enterprise at $1,399 per developer per year.

When to choose

Use this when you can absorb a coordinated frontend upgrade and want to stay on the actively developed MUI X major. The decisive factor is whether you already plan to adopt Material UI 7 or need v8-only features and the cleaner default ESM path.

Tradeoffs

You get the current major, continuous support, official codemods, and the simplest package compatibility story. The cost is a wider migration surface across Material UI, MUI X, TypeScript, and any code touching changed Data Grid APIs.

Cautions

The migration guide calls out breaking changes beyond version bumps: `LicenseInfo` must come from `@mui/x-license`, modern bundle aliases must be removed, and some Data Grid behaviors and types changed. Codemods do not cover every case, especially spread props and cross-file patterns, so manual review and testing are still required.

Sources

Hold on MUI X 7 and defer the Material UI 7 upgrade

MUI X 7 is still supported, but it is now in long-term support rather than the active major. The support page says v7 receives security and regression support until 2027-04-17, which means it remains a viable holding pattern as of 2026-04-08. This is the clearest way to avoid MUI X 8's default expectation of Material UI 7 while keeping an officially supported branch. By contrast, MUI X 6 support ended on 2026-03-23, so the practical 'stay back' option is v7, not v6.

When to choose

Use this when a stack-wide Material UI 7 migration is not funded or would create too much churn across apps in the next quarter or two. The decisive factor is whether MUI X 7 already covers the features you need through the 2027-04-17 LTS window.

Tradeoffs

This minimizes immediate migration cost and lets you separate framework upgrade work from product delivery. The downside is that you stay off the active major and delay access to v8 improvements and its cleaner out-of-the-box package compatibility story.

Cautions

Do not treat 'earlier MUI X versions' as a broad safe zone: as of 2026-04-08, v6 has already left support. You should also assume the eventual jump to v8 will still require planning for API changes and Material UI 7 alignment later.

Sources

Adopt MUI X 8 now but keep Material UI 5 or 6 temporarily with the compatibility guide

MUI provides an official 'Usage with Material UI v5/v6' guide for teams that want MUI X 8 without immediately moving the rest of the stack to Material UI 7. The guide says v5 and v6 can still be used, but extra steps are required in Node.js environments because MUI X 8 follows the Material UI 7 package layout and exports-field changes. The documented fixes include passing the `require` condition in Node.js and configuring Vite, webpack, or Next.js Pages Router accordingly. This is a bridge option, not the default path MUI recommends.

When to choose

Use this when you need MUI X 8 specifically, but a full Material UI 7 rollout has to be phased across apps or packages. The decisive factor is whether your team can tolerate temporary build and SSR complexity to decouple the MUI X upgrade from the wider design-system upgrade.

Tradeoffs

This can shorten the wait for v8 features without forcing an all-at-once frontend migration. The tradeoff is higher build-tool complexity and a less standard setup, especially in Node.js, SSR, or multi-app environments.

Cautions

MUI explicitly says v7 is the out-of-the-box path and only recommends the compatibility steps when you actually hit Node.js import issues such as `ERR_UNSUPPORTED_DIR_IMPORT`. For Next.js Pages Router, Vite SSR, and webpack, you must keep the documented condition settings aligned or you can get inconsistent dev/build behavior.

Sources

Facts updated: 2026-04-08
Published: 2026-04-08

Related questions

Try with your AI agent

$ npm install -g pocketlantern
$ pocketlantern init
# Restart Claude Code, Cursor, or your MCP client, then ask:
# "Should I upgrade to MUI X 8 now?"
Missing something? Request coverage