Lerpa UI vs Material UI (MUI): ownership and bundle size compared
· 6 min read · comparison · material-ui · mui · react
Material UI is a powerful runtime component library. Lerpa UI takes the opposite approach — copy-paste source, zero runtime, Tailwind tokens. Here's how they compare for React apps.
Material UI (MUI) is one of the most established React component libraries. It is powerful and batteries-included, but it is also a runtime library with a strong Material Design opinion. Lerpa UI takes the opposite approach: copy-paste source you own, zero runtime style engine, and a neutral aesthetic you theme with CSS variables.
| Feature | Lerpa UI | Material UI |
|---|---|---|
| Delivery | Copy-paste source you own | npm package dependency |
| Styling | Tailwind v4 + CSS variables (zero runtime) | Emotion / runtime CSS-in-JS |
| Design opinion | Neutral, fully retheme-able | Material Design |
| Bundle | Only what you add | Larger baseline runtime |
| Customization | Edit the file directly | Theme overrides / sx props |
| License | MIT | MIT |
Where Lerpa UI goes further
Because Lerpa components are plain files written into your repo, there is no runtime style engine tax and no theme-override indirection — to change something, you edit the component. Tokens are CSS variables, so a single theme swap recolors every component live. You ship only the components you add.
When Material UI is the better pick
If you want Material Design specifically, or a single versioned dependency to upgrade centrally with a vast ecosystem of community add-ons, MUI is a strong, mature choice. Lerpa UI wins when you want ownership, a custom look, and a smaller runtime.
Try it
See the gallery or install the CLI — Lerpa UI is free and MIT licensed.