Convert SASS to SCSS syntax. Part of the DevTools Surf developer suite. Browse more tools in the CSS collection.
Use Cases
Teams modernizing legacy indented Sass to the more popular SCSS syntax
Developers converting Sass files to SCSS for better IDE support
Open source maintainers aligning with SCSS as the community standard
New team members converting unfamiliar Sass to SCSS for readability
Tips
Verify that curly braces and semicolons are properly added
Check that + mixin includes expand to @include directives
Ensure multi-line property values are correctly brace-wrapped
Fun Facts
The Sass-to-SCSS conversion was so common that the Sass team built the sass-convert CLI tool specifically for this purpose.
SCSS became the default Sass syntax around 2010, and most modern Sass documentation uses SCSS examples exclusively.
Converting from indented Sass to SCSS is fully lossless; no features or behaviors change during the transformation.
FAQ
Do I lose anything going Sass → SCSS?
Only concision — the SCSS output has braces and semicolons that the Sass source didn't need. Behavior is identical.
Why bother converting?
Team onboarding: SCSS is what most engineers recognize. A codebase in SASS indented syntax can feel unfamiliar; switching to SCSS reduces the learning curve.
Can I convert back and forth freely?
Yes — both syntaxes represent the same AST. SASS↔SCSS round-trips losslessly.
Is one faster to compile?
No difference. Dart Sass parses both equally fast.
