Design System Diff Lab
Diff design tokens and inspect CSS @layer order and selector specificity locally.
OpenPaste a crowded className and get it back grouped, deduplicated and without utilities that cancel each other out.
Drop className attributes or raw utility lists.
Layout, spacing, typography, and effects group cleanly.
See which utility wins when two set the same property.
Paste the conflict-free string back into your component.
A button component has passed through four pull requests and now carries p-2 and p-4, text-sm and text-lg, plus a hover color nobody remembers adding. Reviewers skim past it because the attribute is forty classes long. Paste it here to see which utilities collide and which ones never take effect.
The sorter accepts a bare list of classes or a whole class="..." or className="..." attribute and pulls the classes out for you. It arranges them into eight groups (layout, flex and grid, spacing, sizing, typography, background, border and ring, effects), puts base utilities before variants, and orders variants from sm through 2xl, then dark, then interaction states. Two classes that set the same property under the same variant are reported as a conflict. With Drop overridden classes ticked, the losers disappear from the output, and Wrap as className gives you a ready attribute to paste back.
One thing to keep in mind: in real Tailwind builds the winner of a conflict depends on the order of rules in the generated stylesheet, not on the order in your markup. The tool marks the last class in source order as the likely winner, but the dependable fix is to delete the other one. If the fight is between a utility and your own selector, compare selector weights with the specificity calculator instead.
Sorting happens in the page script, so internal component names never leave your machine. For token-level drift between themes, the design token diff lab is the better fit, and the full set of CSS generators covers the layout side.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
Conflicts are only checked inside the same variant scope. A hover background and a plain background apply in different states, so both are kept. The same goes for md:text-base next to text-sm.
Every class or className attribute found in the paste is merged into one list, which can produce false conflicts between unrelated elements. Paste one element at a time for an accurate report.
Usually yes, because classes are matched by prefix. bg-brand is treated as a background color and text-brand as a text utility. Classes with no known prefix go into an Unrecognised group at the end of their variant block and are never removed.