Home » Developer Tools » SCSS Beautifier
Paste messy SCSS source and get clean readable code with consistent indentation in seconds.
Last updated 13 November 2026
Your code never leaves your browser. Everything runs locally on your device.
This tool only formats code. It does not run, compile or execute it, so always review the formatted output before you use it in a project.
Messy SCSS is hard to read, especially with deep nesting. The SCSS Beautifier reformats SCSS source with consistent indentation for nesting, mixins, and media queries, while keeping variables and constructs intact.
It understands SCSS, not just plain CSS, so variables, interpolation, and nested rules are formatted correctly. Everything runs in your browser, so your code is never uploaded to a server.
Here is a real file run through this tool. A test file of 179 characters holds a variable, an interpolation selector, two attribute selectors, an at root rule and a font shorthand line. At 2 space indent the formatted output is 189 characters, and at 4 space indent it is 199 characters. Beautifying adds line breaks, so the file grows a little. That is normal for a beautifier: the gain is readability, not size.
What matters is that every construct survives intact. The output still has .icon-#{$size} with no space inside the selector, a[href^="https"] and a[href$=".pdf"] with their operators joined, @at-root .plain with its space, and font: 16px/1.5 sans-serif with the slash tight. Before the fix, all four came out corrupted, so the formatted code no longer meant the same thing.
The beautifier only changes indentation and spacing. Your variables, nesting, mixins, includes, media queries and values stay exactly the same, and the output is still SCSS source, which you compile with Sass as usual. It does not run, compile or execute your code, so always review the formatted output before you use it in a project.
Interpolation, attribute selectors, at rules and font shorthand are now handled as SCSS, not as plain CSS. A descendant selector such as .a .b keeps its space, a hex colour such as #fff keeps its space after the value before it, and a comparison such as $a == $b stays joined. Pick 2 spaces or 4 spaces from the indent size option to match your project style.
This beautifier does not compile SCSS to CSS. The output is still SCSS source, formatted for reading, and you compile it with Sass as usual. It does not minify either. When your SCSS is readable again and ready to ship smaller, use the SCSS minifier to shrink the source.
It also does not fix broken SCSS. It only formats code that already parses as SCSS, so fix syntax errors first, then beautify. And it does not check that your selectors match anything in your HTML: a neatly formatted selector that matches nothing is still a selector that matches nothing.
Yes, it is completely free with no sign up.
No. Beautifying only changes indentation and spacing. Your variables, nesting, mixins, and values stay exactly the same.
No. The output is still SCSS source, formatted for reading, and you compile it with Sass as usual.
Yes. Nested rules, mixins, includes, media queries, and interpolation are all formatted with correct indentation.
Yes. Pick 2 spaces or 4 spaces from the indent size option to match your project style.
No. All formatting happens in your browser on your own device, so your code never leaves your computer.
Yes. An interpolation such as .icon-#{$size} keeps its shape, with no space added inside the selector, and #{$w}px keeps the unit joined to the interpolation, so the compiled CSS still targets the right selector.
Yes. The operators ^=, $=, *=, ~= and |= stay joined to the equals sign, so a[href^="https"] stays a valid attribute selector instead of coming out split.
@at-root?The space after the directive is kept, so @at-root .plain stays a directive plus a selector. Before, the two were merged into @at-root.plain, which means something else.
No. The slash in font: 16px/1.5 sans-serif stays tight, because in Sass a spaced slash means division. A real division such as $w / 2 still keeps its spaces.
No. It only formats code that already parses as SCSS. Fix syntax errors first, then beautify, and always review the output before you use it in a project.
When your SCSS is readable again and ready to ship smaller, try the SCSS minifier to shrink the source.