Introducing Material UI and MUI X v9 (original) (raw)

We are thrilled to announce the simultaneous release of Material UI v9 and of each of the MUI X v9 components.

We are realigning the major versions of the core design system and all the advanced components to provide a more cohesive, predictable development experience. This is more than a version bump; it's one step toward a more unified ecosystem for MUI products.

In v9, we focused on three concrete areas:

Table of contents

What we released

All product announcements:

One MUI ecosystem, a synced major version

When we shipped MUI X v6 in 2023, we decoupled MUI X's major version from Material UI, at a time when Material UI was still on v5. The goal was to give advanced components a faster, predictable release rhythm without tying every breaking change to Material UI's release schedule. We also assumed that, over time, breaking-change pressure might push the two major lines further apart.

In practice, that divergence never really increased the way we expected, while keeping independent major numbers still made upgrades, peer dependencies, and communication across the stack heavier than we liked.

So for v9, we're realigning: Material UI moves from v7 straight to v9 (there is no Material UI v8, like there is no v2), in step with MUI X v9, restoring a single shared major for the suite for the first time since that split.

With v9, we're synchronizing the major version across the stack:

A single major version number makes it easier to:

Material UI and MUI X v9 ecosystem overview.

Components highlights

We've focused on stability, accessibility, and new building blocks across the v9 major; these bullets summarize the direction:

Note: Event Timeline and advanced Charts preview features are available under the Premium plan.

New MUI Console application

Last year, we began offering AI assistance for the Data Grid: users describe what they want in natural language, and the grid applies structured changes while keeping state visible and editable.

Until now, production rollout was harder: teams needed support round-trips for API keys and had less visibility into usage alongside licenses.

The MUI Console is the application we're rolling out to remove this friction. It gathers license keys, service API keys (including for assistant and add-on experiences), billing, and usage in one place: an operational hub for MUI's commercial offerings rather than scattered tickets and dashboards.

With the console, teams can:

We will expand Console over time, but v9 already covers the core operational loop: provision keys, manage licenses, and monitor usage.

"MUI Chat" renamed to "MUI Recipes"

MUI Chat is a generative UI tool: you describe the UI you want, and it generates a production-ready React interface using the idiomatic API of Material UI, MUI X, or Base UI, depending on the prompt.

Compared with starting from a blank file, it generates a first draft UI quickly and uses MUI component APIs directly. That reduces the amount of adaptation needed before you can use the output in a real codebase.

In practice, we use it mostly to deliver custom recipes and customization grounded in what you already see in the docs: variations on our examples, tuned layouts, and branded panels that stay aligned with the same APIs and patterns we document.

v9 introduces something different: MUI X Chat, a real chat component (@mui/x-chat) meant to ship inside your product. Keeping the builder under the name "Chat" would collide with that surface and confuse two very different offerings.

So MUI Chat is being renamed to MUI Recipes, a name that matches what the tool is optimized for today: recipe-style outputs and tailored UIs built from our component set, not an embeddable chat runtime.

MUI X pricing and licensing updates

Starting April 8, 2026, MUI X pricing and licensing are updated:

For full details, transition examples, and plan-by-plan terms, read the full announcement:Upcoming Changes to MUI X Pricing and Licensing in 2026.

Telemetry on commercial components

We launched telemetry for commercial components last year. In v9, telemetry is now enabled by default in development mode for commercial components, and it remains off in production builds.

Telemetry helps us understand how developers use components in real projects, so we can prioritize fixes, improve defaults, and focus roadmap work on the patterns teams actually use. If your workspace requires it, you can opt out by following the documented steps:Opting out of telemetry.

What's next

Over the coming months, we plan to focus our work on the following areas.

Component portfolio expansion

Advanced components continue to grow across three workflow types: data analysis (Data Grid and Charts), resource management (Calendar and Timeline), and conversational interfaces (Chat).

The goal is production workflows, not isolated demos: components should keep state inspectable, integrate cleanly, and remain controllable by application logic.

AI-native workflows

The Data Grid AI Assistant is the first large piece of that story in production. Together with the MUI Console, where you can handle licenses and service keys in one flow, it forms a clearer path from trying assistive features to rolling them out, without stitching together separate tools for assistants and account management.

Integrated AI workflows can reduce repetitive multi-step UI actions while keeping the resulting state visible and editable.

Across v9 minors, we plan to expand assistant coverage, improve reliability and documentation, and integrate assistant flows more deeply with advanced components.

Remove Emotion and add modern theme layering

We're listening to you, and for the next major, we're going to explore refactoring the styling layer and theme layering model to better support modern design-system workflows:

Further reading

We want your feedback

Your input drives our direction. Join our GitHub communities today to share your insights, report issues, and help shape the future: