Guide
Why a CSS to SCSS converter should respect cascade order
What this converter does differently — and what it deliberately leaves out.
Many CSS to SCSS converters optimize for neat-looking output and freely move rules or media queries. That can change the cascade: a declaration that used to win can become overridden after conversion. This tool treats preserving reviewable cascade order as the default.
Safe mode keeps the source order and converts straightforward BEM selectors such as .c-button__label and .c-button--primary into &__label and &--primary nesting. It does not silently merge separate rules just because their selectors look related.
Breakpoint organize mode is optional. It orders simple min-width queries from small to large and max-width queries from large to small. Mixed, ranged, or multi-condition queries stay in source order and are called out in the conversion report instead of being guessed at.
The tradeoff is intentional. The first version does not attempt to fully interpret CSS Modules, @layer, complex @supports rules, already-nested CSS, or SCSS-only syntax. It also does not reorder properties. The goal is a useful conversion you can trust and review, not aggressive formatting that hides a behavior change.