Tailwind Class Sorter
Sort Tailwind classes and detect conflicting utilities with a winner explanation.
OpenA ready starting block of breakpoints and fluid clamp() values to paste into a new stylesheet.
The breakpoint and clamp() template loads immediately.
Change the widths to match your design system.
Set minimum, preferred and maximum sizes for type and spacing.
Copy the block or download responsive.css.
You are starting a small marketing page and need the usual breakpoints and a heading size that scales between phone and desktop. Instead of opening an old project to copy them, take this starter block and edit the numbers.
This helper outputs a fixed starter template rather than taking inputs. It contains three media queries (max-width 640px for mobile, min-width 768px for tablet and min-width 1024px for desktop) with empty bodies, a fluid font-size using clamp(1rem, 0.9rem + 0.5vw, 1.25rem), and fluid horizontal padding using clamp(1rem, 4vw, 3rem). Copy it, or download it as responsive.css, and fill in the rules.
Two edits are worth making before you build on it. First, pick one direction: the template mixes a max-width query with min-width queries, which leaves screens between 641 and 767 px covered by neither the mobile nor the tablet block. Mobile-first projects usually drop the max-width query and put mobile styles outside any query. Second, adjust clamp() to your type scale: the first value is the minimum, the last is the maximum, and the middle expression controls how quickly it grows with the viewport. To turn pixel sizes from a design file into rem values for clamp(), use the px to rem calculator. For column changes at each breakpoint, build the base layout in the CSS grid builder.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
This helper is a fixed starter template. Edit the breakpoint widths and clamp() values after you copy them; the defaults suit many small sites but are not tailored to yours.
Mostly, because the minimum and maximum are in rem. Keep a rem part in the middle expression, as the template does, so text still grows when users raise their default font size.
Both work in current browsers. em-based queries follow the user's font size setting, which some teams prefer for accessibility. Convert by dividing the px value by 16.