Inspect a stylesheet: every selector with its specificity, properties with their values, custom properties with where they are defined, and every media query.
Waiting for a stylesheet
Selectors, declarations, custom properties and media queries, from one parse.
The report appears here
Selectors with specificity, properties with their values, custom properties, and every conditional rule.
CSS Inspector runs entirely on your device — nothing is uploaded.
You’re on the Free plan. Compare plans
Five views over one parse: selectors with their specificity, properties with the values they take, custom properties with where each is defined and how often it is read, media queries with what is inside them, and the counts across the whole sheet.
Specificity is computed the way the selectors specification defines it — a triple of id, class-like and element-like counts — including the awkward modern cases. :is(), :not() and :has() take the specificity of their most specific argument. :where() contributes nothing at all, which is the entire reason it exists and the thing people most often get wrong when reasoning about it by hand. An attribute selector counts as class-like; a pseudo-element counts as element-like.
The custom-property view answers a question that is otherwise tedious: which variables does this sheet define, which does it read, and which does it read without ever defining. That last group is worth looking at. The variable may come from another stylesheet or from an inline style, in which case all is well — or it may come from nowhere, in which case the declaration using it falls back to its initial value or is dropped, silently.
There are three things this tool will not tell you, and it is explicit about each. It cannot say whether a selector is unused, because that needs the HTML. It cannot say whether a declaration is overridden, because that needs the whole cascade including every other stylesheet on the page, the inline styles and the layer order. And it cannot score performance, because that needs a page to measure. A confident answer to any of those without the context would be a guess, and a guess presented in a tidy table is worse than no answer.
Duplicate selectors are reported as a fact rather than a fault. Writing the same selector twice is a normal way to override an earlier rule; it is only a problem when it was not deliberate, and only you can tell which it was.
As the specification defines it: a triple counting ids, then classes, attribute selectors and pseudo-classes, then elements and pseudo-elements. Comparison is left to right, so a single id beats any number of classes.
The first three take the specificity of their most specific argument, so :is(#a, .b) counts as an id. :where() contributes nothing at all, which is what makes it useful for writing defaults that are easy to override.
No, and it will not guess. Knowing whether a selector matches anything requires the HTML it is meant to match, which this tool never sees. Your browser's coverage panel can answer that against a real page.
No. That needs the full cascade — every other stylesheet on the page, the inline styles, the layer order and the document order. A verdict based only on this file would be wrong often enough to be dangerous.
That var(--name) appears in this stylesheet with no matching definition in it. The variable may be defined elsewhere, which is fine. If it is not defined anywhere, the declaration using it falls back to the property's initial value or is dropped — silently, which is what makes it worth catching.
Not necessarily. Writing a selector twice is a normal way to override an earlier declaration. It is reported so you can tell whether this one was deliberate.