How to use Static Unused CSS Selector Report
- Paste CSS or choose one local UTF-8 CSS file; a selected file replaces the pasted stylesheet.
- Paste an HTML snapshot or choose up to 20 local HTML files. Selected snapshots replace the pasted HTML, and every page stays inert.
- Read updated static matches across the supplied set. Dynamic/unsupported selectors and unevaluated at-rules remain separate from unmatched candidates.
- Download the report if needed. Check other pages, responsive states, scripts and shadow DOM before considering any removal; no cleaned CSS is produced.
Example: Static Unused CSS Selector Report
Compare the sample CSS with one snapshot: two unmatched selector candidates and three unevaluated cases, including @import.
Options
- Snapshot evidence
- A selector matching nothing in this input can still be used by another page or runtime state.
- Unknown selectors
- Unsupported syntax, dynamic pseudo states and unevaluated at-rules remain unknown rather than receiving an unused verdict.
- Stylesheet
- Up to 100,000 CSS characters, 200 rules and 400 selectors. Simple style rules are inspected; @import is reported without evaluation and is never fetched.
- Static HTML snapshot
- A saved page or a fragment. The detached parser never runs scripts and never requests images or stylesheets.
- Local CSS file (optional)
- A selected UTF-8 CSS file replaces the pasted stylesheet for this check. Up to 100,000 bytes; it is never applied or imported.
- Local HTML snapshots (optional)
- Selected UTF-8 files replace the pasted snapshot. Up to 20 pages and 200,000 bytes total. Every page stays inert; no cleaned CSS is produced.
Supported inputs and limits
- CSS up to 100,000 pasted characters or one selected UTF-8 file up to 100,000 bytes;
- 200 rules and 400 selectors.
- Selected HTML intake allows 20 snapshots and 200,000 bytes total.
- Static supported selector matches only; stylesheet rules are never applied. @import, dynamic/unsupported states and conditional cases are unevaluated.
- Missing document wrappers in fragments can also remain unknown.
More details
No runtime coverage, shadow-state analysis, CSS deletion or safe-removal certificate.
Where your input is processed
This tool does not upload your inputs. See the limits for anything saved on your device.
An unmatched selector is not safe to delete
Scripts, responsive state, forms, shadow trees and pages outside the snapshot can use a rule. Recheck those contexts in a real application and retain the source stylesheet until review is complete. This report never automatically removes CSS.
Questions about Static Unused CSS Selector Report
Will it remove CSS automatically?
It exports findings without editing your stylesheet.
Are hover states called unused?
Dynamic or unsupported states remain unknown.
Does one snapshot cover every page?
No. Review other pages and runtime states separately.