// the take
material-tailwind is a component library that reskins Tailwind CSS with Material Design, shipped as two separate packages — @material-tailwind/react and @material-tailwind/html — covering roughly 40 components (accordion through timeline) in each. It's aimed at teams who want the Material look without pulling in MUI's bundle and styling system, and who are fine building on Tailwind utility classes directly.
Wide component coverage (accordion, dialog, menu, table, stepper, etc.) shipped in both a React flavor and a framework-agnostic HTML/vanilla-JS flavor, so you're not locked into React. Styling is pure Tailwind utility classes rather than a separate CSS-in-JS runtime, so there's no extra client-side styling engine shipped with it. Theming is centralized through one ThemeProvider/config object instead of scattered per-component overrides, which makes consistent rebranding less painful. 4.3k stars and a healthy npm download count suggest real production usage rather than a demo repo.
The withMT() tailwind.config wrapper assumes Tailwind v3's JS config file; Tailwind v4 moved to a CSS-first config with no tailwind.config.js by default, so anyone on v4 will hit friction until this is addressed. The README's setup snippet wraps the whole app in ThemeProvider using the plain CRA ReactDOM.createRoot pattern, with no guidance for Next.js App Router, where wrapping server-rendered trees in a client context provider is a common source of hydration mismatches. There's no mention anywhere in the docs of accessibility — keyboard navigation, ARIA roles — for any component, so looking like Material Design doesn't tell you anything about screen-reader support. Last push was 2026-04-28, which is six months stale for a library with this much surface area (40+ components across two separately versioned packages) to keep in sync with Tailwind and React releases.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →