PACKAGE · UI COMPONENTS

@mantine/core

React components library focused on usability, accessibility and developer experience

WEEKLY DOWNLOADS 983.0K
STARS 31.2K
FORKS 2.3K
OPEN ISSUES 39
GZIP SIZE 170.7 kB
UNPACKED SIZE 8.3 MB
LAST UPDATED 3mo ago
DOWNLOAD TRENDS

@mantine/core downloads — last 12 months

Download trends for @mantine/core1 download series from Jun 2025 to May 2026. Use left and right arrow keys to inspect monthly values.02.0M4.0M6.0M8.0MJun 2025SepDecMarMay 2026
@mantine/core
ABOUT @MANTINE/CORE

@mantine/core is a comprehensive React component library designed to accelerate UI development. It provides a rich set of pre-built, customizable components addressing common user interface needs, from basic layout elements to complex forms and data displays. This library aims to reduce the boilerplate code developers typically write for standard UI patterns, allowing them to focus on application logic rather than re-implementing common components.

The library is built with a strong emphasis on usability, accessibility, and developer experience. This means components are designed to be intuitive for end-users, conform to WCAG accessibility standards, and offer a streamlined development workflow. Its primary audience includes React developers seeking a unified and consistent design system for their applications, particularly those valuing maintainability and a high degree of customization.

Mantine's API is structured around a theming system and hook-based utilities. The `MantineProvider` wraps your application, allowing global theme configuration and component customization. Hooks like `useMantineTheme` provide access to theme variables, while component props offer granular control over styling and behavior. This approach facilitates easy theming and dynamic UI adjustments across the application.

Integration with the React ecosystem is seamless. It's framework-agnostic within React, working with popular choices like Next.js and Vite. Mantine's components are built with TypeScript, offering strong typing benefits. Its utility-focused design also pairs well with state management libraries and data fetching solutions, fitting into standard React development workflows.

With an unpacked size of 8.3 MB and a gzipped bundle size of 170.7 kB, @mantine/core offers a substantial feature set without imposing an overly heavy footprint. While not the lightest option for minimal UIs, its scope justifies the size for applications requiring a full component suite. The library has a mature and active development cycle, indicated by its 31.2K GitHub stars and consistent updates.

WHEN TO USE
  • When building a scalable React application that requires a consistent and customizable design system across multiple components.
  • When you need to quickly implement accessible UI elements, benefiting from built-in ARIA attributes and keyboard navigation.
  • When leveraging Mantine's extensive theming capabilities to create unique brand aesthetics or dark-mode support.
  • When you want to utilize hooks like `useDisclosure` or `useMediaQuery` to manage component state and responsiveness easily.
  • When integrating complex form structures with validation, taking advantage of the form-related utilities and components.
  • When developing for applications where accessibility compliance is a key requirement from the outset.
  • When you need a comprehensive set of UI primitives and advanced components like DatePickers, RichTextEditors, or Modals.
WHEN NOT TO USE
  • If your project's UI requirements are extremely minimal and only a handful of primitive HTML elements are needed, consider native HTML or a lighter utility-first CSS framework.
  • When you have a strict, pre-existing design system and an in-house component library that conflicts with Mantine's structure.
  • If the 170.7 kB gzipped bundle size is a critical concern for a highly performance-sensitive, low-resource application where every kilobyte counts.
  • When you prefer a CSS-in-JS solution with a different rendering strategy or API, as Mantine's styling is built on CSS variables and its own styling engine.
  • If you are working in an environment that strictly prohibits the use of external component libraries for ideological or policy reasons.

CORRECTIONS

Spot wrong data here?

A short note helps us fix it.

Anonymous · No account · No email back

COMPARISONS 7
@mantine/core vs @floating-ui/react ★ 32.6K · 8.5M/wk @mantine/core vs @mui/material ★ 98.4K · 4.4M/wk @mantine/core vs @radix-ui/themes ★ 8.4K · 305.9K/wk @mantine/core vs @chakra-ui/react ★ 40.4K · 761.4K/wk @mantine/core vs @headlessui/react ★ 28.6K · 3.1M/wk @mantine/core vs antd ★ 98.3K · 1.5M/wk @mantine/core vs @ark-ui/react ★ 5.2K · 419.0K/wk