Sourcemap Explorer
Stack · npm package

@mui/material

Material UI is an open-source React component library that implements Google's Material Design. It's comprehensive and can be used in production out of the box.

latest 9.3.1· MIT· 261 versions publishedView on npm

About

Material UI is an open-source React component library that implements Google's Material Design. It's comprehensive and can be used in production out of the box.

reactreact-componentmuimaterial-uimaterial design

What detecting @mui/material tells you about a site

@mui/material (Material UI) tells you the site is built on Google's Material Design via the most popular React component library. Its presence implies a large, themed component system and usually Emotion-based styling under the hood — a fast route to a consistent, accessible UI at the cost of a heavier bundle.

Why the exact @mui/material version matters

MUI v5 moved to Emotion and the `sx` prop; v6/v7 advanced the styling engine and React 18/19 support. The exact bundled version tells you which styling API and theming model the app uses, and whether it's carrying the older JSS-based v4.

@mui/material in a real-world stack

When you find @mui/material in a bundle, it rarely travels alone. @emotion/react and @emotion/styled (the default style engine), plus @mui/icons-material.

Quick facts

Latest version9.3.1
LicenseMIT
AuthorMUI Team
Installnpm install @mui/material
Direct dependencies12
Peer dependenciesreact, react-dom, @types/react, @emotion/react, @emotion/styled, @mui/material-pigment-css

This package powers Material UI

The @mui/material package is the canonical implementation of Material UI. Sourcemap Explorer uses this exact npm package as the framework-level fingerprint when it flags Material UI on a page — both via the bundled node_modules/@mui/material/ source paths and via the embedded package.json inside the JavaScript sourcemap.

Common pairings

Packages this one expects to find in the same project. Each is also a Sourcemap Explorer detection target.

reactreact-dom@types/react@emotion/react@emotion/styled@mui/material-pigment-css

What @mui/material pulls in

@mui/material declares 12 direct dependencies — each one also rides into any bundle that ships @mui/material, so they are detection targets too. Reading them is a quick way to understand the package's real footprint .

clsxcsstypereact-is@mui/types@mui/utilsprop-types@mui/system@babel/runtime@popperjs/corereact-transition-group@mui/core-downloads-tracker@types/react-transition-group

How Sourcemap Explorer detects @mui/material

@mui/material ships as v9.3.1, published 2026-08-06 and carries 12 direct dependencies, 6 peer dependencies (react, react-dom, @types/react), 261 versions on the registry. Those exact numbers are the footprint Sourcemap Explorer matches when @mui/material rides inside a deployed bundle — here is how the detection works.

We catch @mui/material from two complementary signals: bundled source paths and the embedded package.json. Modern bundlers (webpack, Vite, esbuild, Rollup, Turbopack) preserve the original node_modules/@mui/material/ paths inside the JavaScript sourcemap's sources[] array — that's the canonical signal. When the matching package.json is also captured in sourcesContent[], we read the exact version field — patch number included. No regex guessing, no version inference.

  1. 1

    Confirm the site exposes sourcemaps

    In DevTools Network, check the response headers of any application script for `SourceMap` or `X-SourceMap`. Failing that, fetch the script's last 4 KB and look for a `//# sourceMappingURL=` comment — that map is where the `@mui/material` paths live.

  2. 2

    Find the package in the bundle

    Open DevTools → Network → reload. Click any application script and look at its sourcemap. Inside, search `sources[]` for entries matching `node_modules/@mui/material/` — every match confirms the package is bundled. The matching `sourcesContent[i]` for `node_modules/@mui/material/package.json` gives you the exact installed version.

  3. 3

    Read the version directly from package.json

    Run `jq -r '. as $m | $m.sources | to_entries[] | select(.value | endswith("node_modules/@mui/material/package.json")) | $m.sourcesContent[.key] | fromjson | .version' bundle.js.map`. Sourcemap Explorer automates the same query in the popup.

Major releases of @mui/material

When each major version first landed. Major bumps are where breaking changes live, so this timeline is the fastest way to date the @mui/material version a site actually ships against the ecosystem.

Major
First release
Date
v9
9.0.0
2026-04-07
v7
7.0.0
2025-03-26
v6
6.0.0
2024-08-27
v5
5.0.0
2021-09-16

Recent versions

Version
Released
9.3.1
2026-08-06
9.3.0
2026-08-05
9.2.0
2026-07-03
9.1.2
2026-06-23
9.1.1
2026-06-11
9.1.0
2026-06-08
9.0.1
2026-05-07
9.0.0
2026-04-07

@mui/material README

Live mirror of the GitHub README, for reference. Updated whenever the repo's default branch changes.

Material UI logo

Material UI

license npm latest package npm next package npm downloads GitHub branch status Coverage Status Follow on X Renovate status Average time to resolve an issue Open Collective backers and sponsors OpenSSF Best Practices

Material UI is a comprehensive library of React components that features our independent implementation of Google's Material Design system. It's trusted by some of the world's greatest product teams because it's been rigorously battle-tested through more than a decade of development by thousands of open-source contributors.

Material UI's core functionality is extended by MUI X, a suite of complex components for advanced use cases.

Documentation

Get started in the Material UI documentation.

Older versions

Note: @next points to pre-releases. Use @latest for the latest stable release.

Sponsors

Diamond 💎

doit

Diamond sponsors are those who have pledged $1,500/month or more to MUI.

Gold 🏆

via Open Collective or via Patreon

tidelift.com   dialmycalls.com  

Goread.io   Buzzoid   Twicsy   Poprey   SocialWick   Follower24   Views4You  

Gold sponsors are those who have pledged $500/month or more to MUI.

More backers

See the full list of our backers.

Questions

For how-to questions that don't involve making changes to the code base, please use Stack Overflow instead of GitHub issues.

Examples

Our documentation features a collection of example projects.

Premium templates

You can find complete templates and themes in the MUI Store.

Contributing

Read the contributing guide to learn about our development process, how to propose bug fixes and improvements, and how to build and test your changes.

Contributing is about more than just issues and pull requests! There are many other ways to support Material UI beyond contributing to the code base.

Changelog

The changelog is regularly updated to reflect what's changed in each new release.

Roadmap

Future plans and high-priority features and enhancements can be found in the roadmap.

License

This project is licensed under the terms of the MIT license.

Security

For details on supported versions and contact information for reporting security issues, please refer to the security policy.

Sponsoring services

These great services sponsor MUI's core infrastructure:

GitHub logo

GitHub lets us host the Git repository and coordinate contributions.

Netlify logo

Netlify lets us distribute the documentation.

CodeCov logo

CodeCov lets us monitor test coverage.

FAQ

What is @mui/material used for?

Material UI is an open-source React component library that implements Google's Material Design. It's comprehensive and can be used in production out of the box.

How can I tell if a website is using @mui/material?

Open the page in Chrome with the Sourcemap Explorer extension installed and read the Stack tab. We catch `@mui/material` from two complementary signals: `node_modules/@mui/material/` paths inside the JavaScript sourcemap, and the embedded `package.json` we read for exact-version detection. Without the extension you can do the same lookup manually in DevTools — the steps are listed in the "How Sourcemap Explorer detects" section above.

How do I find out which version of @mui/material a website is running?

Read it straight from the site's JavaScript sourcemap. When a build ships source maps, the bundled `@mui/material/package.json` carries the exact `version` string — Sourcemap Explorer extracts it in one click on the Stack tab, and you can do it by hand in DevTools by opening the `.map` file and searching for `node_modules/@mui/material/package.json`. That is far more reliable than inferring the version from an asset-hash or a `?ver=` query string, which is all surface-level detectors have to go on. The current npm release is 9.3.1, but real deployments frequently run an older pinned version — which is exactly why reading the bundled number matters.

What is the latest version of @mui/material?

9.3.1, as published on the npm registry. The "Recent versions" table on this page lists the most recent 8 releases with their release dates. Sourcemap Explorer reports the version actually bundled into a site, which can lag the latest release by months on real-world deployments.

Is @mui/material actively maintained?

Very actively maintained — the last release shipped within the past three months. The last published release was 2026-08-06. Source code: https://github.com/mui/material-ui.

What is the relationship between @mui/material and Material UI?

@mui/material is the canonical npm package for Material UI. Sourcemap Explorer treats finding `@mui/material` in a bundle as the framework-level signal that Material UI is on the page, and the page you're reading is the canonical Sourcemap Explorer entry for the package itself.

Where can I read more?

Project homepage: https://mui.com/material-ui/. Source code: https://github.com/mui/material-ui. Published on npm: https://www.npmjs.com/package/@mui/material. Licensed as MIT.

Keep reading on Sourcemap Explorer

Detected by Sourcemap Explorer

When a bundle ships sourcemaps, we read the embedded package.json for @mui/material and report the precise version (the registry's latest is v9.3.1, published 2026-08-06; the bundled copy is often older). Without sourcemaps, an import / require in the page's scripts is enough to flag it.

Install free on Chrome