Responsive styles
Media queries
Configure breakpoints
theme.breakpoints
are used in all responsive Mantine components. Breakpoints are expected to be set in em
units.
You can configure these values with MantineProvider:
Default theme.breakpoints
values:
Breakpoint | Viewport width | Value in px |
---|---|---|
xs | 36em | 576px |
sm | 48em | 768px |
md | 62em | 992px |
lg | 75em | 1200px |
xl | 88em | 1408px |
Breakpoints variables in CSS modules
It is not possible to use CSS variables inside media queries – these values cannot be dynamically
generated by MantineProvider. To use Mantine theme breakpoints
in your .css
files, you will need postcss-simple-vars
package:
Add it to your PostCSS config in postcss.config.js
:
Then you will be able to access these variables in your .css
files:
Will be transformed to:
Dynamic breakpoints are not supported
Values that are defined in
postcss-simple-vars
config are static and are not connected to the theme – if values change, you will need to update them manually in both theme override and postcss config.
hiddenFrom and visibleFrom props
All Mantine components that have a root element support hiddenFrom
and visibleFrom
props.
These props accept breakpoint (xs
, sm
, md
, lg
, xl
) and hide the component when
viewport width is less than or greater than the specified breakpoint:
Component size based on media query
Some components support size
prop, which changes various aspects of component appearance.
size
prop is not responsive – it is not possible to define different component sizes for different
screen sizes. Instead, you can render multiple components with different sizes and show/hide them
based on media query:
use-media-query hook
You can use use-media-query hook to change some of component props based on media query. Note that this approach is not recommended for most of the cases if you have ssr in your application (you use Next.js, Remix, Gatsby or any other framework that includes ssr) as it may cause hydration mismatch. If you do not have ssr in your application (for example, if you use Vite), then you can safely use this hook to change props of components or conditionally render components based on hook return value.
use-media-query hook can be safely used to change props of components that are not rendered
on server side (modals, tooltips, etc.). In the following example, it is safe to use useMediaQuery
hook to
change Tooltip props as it is not rendered on server side: