Description
MUI X provides React components that extend MUI Core (or more specifically, Material UI). Some of the features are MIT licensed, and some are not.
The Pro plan, annual license, can be purchased on this page.
Please note:
– MUI X doesn’t include any design assets. You can find design kits for Figma, Sketch, and Adobe XD under the “Design” section.
– MUI X isn’t a template, you can find templates under the “Templates” section.
– If you’re an existing MUI customer looking to renew your v8 license, please contact us: sales@mui.com
– MUI X doesn’t include any design assets. You can find design kits for Figma, Sketch, and Adobe XD under the “Design” section.
– MUI X isn’t a template, you can find templates under the “Templates” section.
– If you’re an existing MUI customer looking to renew your v8 license, please contact us: sales@mui.com
Resources
A couple of resources that you might be looking for:
- MUI X End User License Agreement
- The product philosophy behind each plan
- How to get support for the software
- The documentation
- The MUI X pricing page
- The email address to use to contact sales: sales@mui.com
Philipp Huber (verified owner) –
—
dimension: bugs
—
MUI X Pro — great library, but a blocking upstream bug forced a rollback
We’ve used MUI X Pro (Data Grid Pro, Tree View) for a while and rate it highly — solid components, good docs, fair pricing for what you get. Support has been responsive too.
That said, we had to fully revert a recent upgrade (@mui/material 6→9, @mui/x-* 7→9) in production. Under React 19, Autocomplete’s handleClick calls inputRef.current.focus() without a null guard, and React 19’s ref-cleanup timing can null that ref before the handler runs. Result: an uncaught crash, plus silent failures — typed values not triggering recompute, onChange not firing on selection. No visible error to the user, which made it worse.
This is the same root cause already fixed at one call site by mui/material#48617 (“Guard against null inputRef during unmount”) — just not yet applied to handleClick. Once that guard lands there too, we’re ready to move back to v9 right away.
Still a great library overall — just flagging a real production blocker so others hit it with eyes open.
Greg Abaoag –
Thank you for the detailed feedback, and we really appreciate you taking the time to document what you encountered.
We’re glad to hear that MUI X Pro has otherwise been working well for your team, particularly the components, documentation, pricing, and support. We also understand how frustrating it is to have to roll back an upgrade because of a production-blocking issue.
We’ve reached out to learn more about what you experienced and to better understand the impact this had on your production environment. While we really appreciate the clear and constructive feedback you’ve shared here, any additional details you can provide about the issue and the specific scenarios where you encountered these failures would be extremely helpful to our team as we investigate further.
Thanks again for taking the time to flag this and for helping us make MUI X better.