Tailwind Class Sorter
Sort Tailwind classes and detect conflicting utilities with a winner explanation.
OpenSee exactly which design tokens changed between two releases before the change reaches production.
JSON design tokens or CSS custom properties both work.
Catch brand drift before a release.
List cascade layers declared in pasted CSS.
Compare selector tuples when debugging overrides.
The design team shipped a new token export and the release notes only say "color refresh". Before you bump the package, you want a list of every value that moved, every token that vanished and every new one you now have to support. Paste the old and new files side by side and the diff tells you.
Each side accepts either a JSON token file or plain CSS with custom properties. JSON is flattened into dot paths such as color.brand, reading the value key when a token is an object (the Style Dictionary layout). CSS input is scanned for --name: value; declarations and any @layer statements. Press Diff and the report lists added, removed and changed tokens, with the old and new value for each change, plus the layer names found on each side. An optional third box scores selectors, one per line, as (id, class, element) tuples.
A common trap with CSS input: if the same custom property is declared under :root and again under a dark theme selector, only the last declaration is kept, because tokens are keyed by name alone. Diff light and dark themes as separate pastes. For a quick single-selector check, the CSS specificity scorer is lighter, and JSON Compare helps when you need a raw structural diff of the token file itself.
The comparison runs locally in this tab, which is useful when the token file belongs to a brand refresh that has not been announced yet.
Keyboard shortcut
Answers for this tool. For site-wide help, open the FAQ hub.
Not as a special case. Tokens using $value still appear in the diff, but their paths end in .$value instead of collapsing to the token name. Style Dictionary files that use a plain value key flatten cleanly.
Yes, but the keys will rarely line up. JSON paths look like color.brand while CSS properties are named like color-brand, so most tokens will show as removed on one side and added on the other.
No. It lists layer names and specificity tuples so you can reason about the cascade, but it does not evaluate full stylesheets or source order.