Colors
Mantine includes 14 color palettes with 10 shades each, plus the scheme-aware neutral color. The palettes use OKLCH with shared lightness values, so colored controls have consistent brightness across hues.
Colors are exposed on the theme object as an array of strings. You can access a color shade by color name and index (0-9); colors with a larger index are darker:
Colors are also exposed as CSS variables:
OKLCH CSS variables
In v10,
--mantine-color-*variables emitoklch(L C H)strings instead of hex/RGB. Code that reads these values and parses them as hex or RGB must be updated. See the 9.x → 10.x migration guide for details and the one-line v9 opt-out.
Adding extra colors
You can add any number of extra colors to the theme.colors object.
This will allow you to use them in all components that support the color prop, for example
Button, Badge, and Switch.
10 shades per color
A colors override must include at least 10 shades per color. Otherwise, you will get a TypeScript error and some variants will not have proper colors. If you only have one color value, you can either pick the remaining colors manually or use the colors generator tool.
You can add more than 10 shades per color: these values will not be used by Mantine components with the default colors resolver, but you can still reference them by index, for example,
color="blue.11".
Neutral color
Use color="neutral" for black in light mode and white in dark mode.
Hover styles and light backgrounds adjust automatically, while the white variant keeps black text on its white background:
Unlike regular palettes, neutral shades share one scheme-aware value.
Set neutral as the primary color to use it throughout your app:
Use --mantine-color-neutral-filled for this color in CSS.
Numbered --mantine-color-neutral-0..9 variables belong to the neutral scale instead.
Virtual colors
A virtual color is a special color whose values should be different for light and dark color schemes.
To define a virtual color, use the virtualColor function which accepts an object with the following
properties as a single argument:
name– color name, must be the same as the key intheme.colorsobjectlight– a key oftheme.colorsobject for light color schemedark– a key oftheme.colorsobject for dark color scheme
To see the demo in action, switch between light and dark color schemes (Ctrl + J):
colorsTuple
Use the colorsTuple function to:
- Use a single color as the same color for all shades
- Transform dynamic string arrays to Mantine color tuple (the array should still have 10 values)
Supported color formats
You can use the following color formats in theme.colors:
- HEX:
#fff,#ffffff - RGB:
rgb(255, 255, 255),rgba(255, 255, 255, 0.5) - HSL:
hsl(0, 0%, 100%),hsla(0, 0%, 100%, 0.5) - OKLCH:
oklch(96.27% 0.0217 238.66),oklch(96.27% 0.0217 238.66 / 0.5)
Example of adding an oklch color to theme:
primaryColor
theme.primaryColor is a key of theme.colors, it is used:
- As a default value for most of the components that support
colorprop - To set default focus ring outline color
CSS color values at
theme.primaryColorThe value of
theme.primaryColormust be a key of thetheme.colorsobject. For example,blue,orange, orgreen. You cannot assign CSS color values; for example, the following code will throw an error during theme merging:
primaryShade
theme.primaryShade is a number from 0 to 9. It determines which shade will be used for components that have a color prop.
You can also customize primary shade for dark and light color schemes separately:
Semantic color variables
In addition to the raw shade variables (--mantine-color-gray-3, etc.), Mantine v10 exposes
semantic role tokens that components use internally. You can override these to theme borders,
surfaces, and text uniformly:
Key role variables and their defaults:
Role variables are defined as var() references to the underlying shade variables, so overriding
--mantine-color-gray-3 still cascades into --mantine-color-border. --mantine-color-body is
aliased to --mantine-color-surface-page, so overriding the latter also updates the page background.
--mantine-color-focus-ring is the color of every focus ring: the .mantine-focus-auto /
.mantine-focus-always outline and the focused Input border. It follows theme.primaryColor, but
unlike --mantine-primary-color-filled it uses shade 5 in dark mode instead of primaryShade.dark,
so the ring stays legible against dark backgrounds. Override it to restyle focus rings everywhere
without touching filled buttons.
Neutral color ladder
A --mantine-color-neutral-0..9 scale backs the role and surface tokens above. The ladder is
scheme-agnostic by role – index N means the same thing in both color schemes – while the
underlying shade differs so contrast holds in both. Use var(--mantine-color-neutral-N) in custom
CSS when you need a neutral shade that adapts to the color scheme without hardcoding separate
gray-N/dark-N pairs:
Mantine components consume this ladder directly for neutral surfaces that have no dedicated role
token – striped table rows, filled fieldsets and accordions, chart empty cells, checkerboard
overlays, drag handles and similar – so overriding --mantine-color-neutral-N re-themes them
together with the role tokens. A few component styles intentionally keep scheme-specific values
and are not affected by ladder overrides: code blocks rendered with a forced codeColorScheme
(CodeHighlight), the inverted Tooltip and Slider label bubbles, and the accent-tinted
drag-and-drop targets in @mantine/schedule.
Dark neutral flavors
Four pre-built neutral color tuples are exported for use as theme.colors.dark:
tintColors
Use tintColors to mix a color into every shade of a MantineColorsTuple.
For example, create a custom dark palette:
strength (default 0.1) controls how much of the tint is mixed in. Middle shades of the tuple
receive proportionally more tint than the shades near either end of the ramp.
The result contains CSS color-mix() expressions, which the browser resolves when applying styles.
Neutral shades tint
Override theme.colors.gray and theme.colors.dark to reproduce the tint in this website's theme settings.
Gray uses 40% of the mixing strength: 10% for dark shades corresponds to 4% for gray shades.
Install @mantine/colors-generator to use mixNeutralColors:
Pass a palette, tint color and percentage to mixNeutralColors.
For Mantine's default OKLCH palettes, it keeps lightness close to the original:
Warm and cold neutrals
Use grayWarmColors and darkWarmColors for warm neutrals in both color schemes.
For cold neutrals, use grayColdColors and darkColdColors instead:
Pass warm or cold palettes to mixNeutralColors to combine both effects:
Surface component
Surface is the depth-aware background primitive introduced in v10. It replaces
Paper (deprecated in v10, removed in v11) and supports automatic elevation stepping in dark mode –
each nested Surface renders one level above its parent by default:
Depth can also be set explicitly with the level prop, either as an absolute 0–2 value or as a
relative string like level="+1"/level="-1" that steps from the parent surface's level. Either
form overrides autoDepth and clamps to the 0–2 range. See the
Surface documentation for all details.
Surface backgrounds can be overridden per color scheme with the surfaces theme key, without
touching CSS variables directly:
Each scheme (light/dark) accepts page, panel, panel2, sunken, muted and input keys,
matching the six surface tokens documented above.
--mantine-color-surface-input is the background of inputs, checkboxes, radios, Dropzone and
RichTextEditor. It is white in light mode and dark-7 in dark mode, one shade above the page, so
fields stand out from the page background.
--mantine-color-surface-muted is the background of code and inset content – Code, Kbd,
CodeHighlight, JsonViewer, Typography pre/code/kbd, striped table rows and filled
Fieldset and Accordion. It is one step off the page in both color schemes (gray-0 / dark-7).
--mantine-color-surface-sunken stays on the well value (gray-1 / dark-9) used by the
SegmentedControl root, the Tabs contained list, and ScrollArea scrollbars, where a raised
indicator sits inside the well. Kbd also uses it in dark mode, so keys stay visible inside inputs.
Color prop
Components that support changing their color have color prop. This prop supports the following values:
- Key of
theme.colors, for example,blueorgreen - Key of
theme.colorswith color index, for example,blue.5orgreen.9 - CSS color value, for example,
#ffforrgba(0, 0, 0, 0.5)
Filled variant
Light variant
Outline variant
Colors index reference
You can reference colors by index in the color prop and style props, for example the c prop:
Text with blue.6 color
Difference between color and c props
The color prop is used to control multiple CSS properties of the component. These properties can vary across different components,
but usually the color prop controls background, color, and border-color CSS properties. For example,
when you set color="#C3FF36" on the Button component (with variant="filled"), it will set the following CSS properties:
background-colorto#C3FF36background-colorwhen the button is hovered to#B0E631(#C3FF36darkened by 10%)colortovar(--mantine-color-white)border-colortotransparent
c is a style prop – it is responsible for setting a single CSS property color (color of the text).
You can combine both props to achieve better contrast between text and background. In the following example:
- The
colorprop setsbackground: #C3FF36andcolor: var(--mantine-color-white) - The
cprop overrides color styles tocolor: var(--mantine-color-black)
Colors variant resolver
theme.variantColorResolver is a function that is used to determine which colors will be used
in different variants in the following components: Alert, Avatar, Button, Badge, and ActionIcon.
It accepts an object argument with the following properties:
theme.variantColorResolver must return an object with the following properties:
You can use theme.variantColorResolver to customize colors handling by default variants
or to add support for new variants:
Colors generation
Use the colors generator to generate 10 shades from a single color.
To generate colors at runtime, install the @mantine/colors-generator package:
generateColors accepts any CSS color and returns a MantineColorsTuple of 10 OKLCH shades.
The input color is kept as is at the shade that matches its lightness, the other shades are built around it:
The second argument adjusts the generated shades. All options are optional:
generateColorFormats returns the palette in oklch, hex, rgb and hsl formats together with the index of the base shade:
Default colors
Add custom colors types
TypeScript will only autocomplete Mantine's default colors when accessing the theme. To add your custom colors to the MantineColor type, you can use TypeScript module declaration.