⌘ K
prettier · postcss · scss · live

Format SCSS with Prettier

Prettier's SCSS parser indents nested selectors, normalises @mixin/@include, and keeps Sass variables tidy. Runs locally.

SCSS Formatter
Input
53 B
1 lines
Output
0 B
1 lines
Status
loading
parser…
Ratio
0.00×
out/in
input · scss
output · formatted scss
Loading parser…
Quick Start

How to format SCSS

Prettier's postcss-scss parser understands nesting, parent selectors, and at-rules — and lays them out consistently.

  1. 01

    Paste SCSS

    A partial, an entire stylesheet, or a single rule with nesting.

    Parsing runs through Prettier’s standalone bundle (or the language-specific equivalent) loaded lazily — no parser ships until the tool is opened.

    scssPrettierASTstandalonelazy
    input · sourceraw · AST
    .a{&:hover{color:red}}
    loaded · parsedAST · ready
  2. 02

    Adjust spacing

    Tab width controls indent depth; print width forces long calc() and gradients to wrap.

    Indent width, tab style, and print-width re-format through a memoised pass — switching 2 → 4 spaces never re-parses, only re-prints.

    optionsindentprint-widthmemoisedlive
    opts · optionstab/width · live
    tab=2
width=80
    options applied · livelive
  3. 03

    Watch nesting align

    Nested rules indent under their parent, @include and @mixin keep their own lines, $variables stay readable.

    The formatter is deterministic and idempotent: running it twice produces byte-identical output, which keeps diffs and git noise to a minimum.

    liveidempotentdeterministicdiff-cleanstable
    out · formattedpretty · ready
    .a {
  &:hover { color: red; }
}
    formatted · liveidempotent
  4. 04

    Copy or download

    Save as .scss for your repo or copy to clipboard. Source stays in the browser.

    Download writes a Blob with the language-appropriate extension; copy uses navigator.clipboard.writeText so the output preserves all whitespace exactly.

    exportclipboardbloblanguage MIMEclient-side
    ok · copiedready · done
    OK Copied
    shipped · ready to shipsuccess
Pro tips

Formatting tips that keep diffs sane

Pick one config and pin it

Inconsistent formatting causes diff churn. Commit .prettierrc / .editorconfig and enforce in CI.

Format on save

Editor integration is faster feedback than a pre-commit hook. Use both for belt-and-braces.

Idempotency matters

Running the formatter twice should produce identical output. Test this on a representative file.

Match the language community

Default to community conventions: 2 spaces for JS/CSS, 4 for Python, tabs for Go. Fights over indent are a productivity tax.

Print-width drives wrapping

80, 100, and 120 are the common targets. Wider lines parse fast but review slower side-by-side.

Don’t mix formatters and linters

Prettier handles whitespace; ESLint handles correctness. Disable overlapping rules to avoid fight-club configs.

Related toolsCSS FormatterLess FormatterSort CSS PropsCSS MinifierHTML FormatterSort Tailwind
Use Cases

When to format SCSS

Component styles, design systems, legacy refactors.

Component styles

Tidy nested SCSS for React/Vue components. Idempotent: running the formatter twice produces byte-identical output, which is the foundation of a clean CI gate. Pair with a pre-commit hook so PRs arrive already formatted, focusing review on logic.

idempotent

Design systems

Normalise tokens, mixins, and variables. Pairs with EditorConfig + .prettierrc for end-to-end consistency. Whitespace-only changes vanish so reviewers see real diffs, and git blame stays honest about who wrote what.

CI-ready

Code reviews

Strip whitespace churn so diffs are clean. Output respects your indent width, tab style, and print-width — settings carry over for repeat runs. Switching 2-space to 4-space costs nothing in CPU but standardises an entire codebase.

diff-clean

Legacy refactor

Format an old Sass file before splitting it up. Format-on-save is the fastest feedback loop; CI is the safety net. Together they make inconsistent indentation a thing of the past and free up review cycles for genuine concerns.

PR-friendly

Quick edits

Reformat after a fast inline change. Whitespace-only changes don't trigger downstream content-hash invalidations, so CDN cache keys and CI cache layers stay warm. Real changes get all the rebuild budget.

review-ready

Docs examples

Standardise SCSS examples for style guides. Pairs with linters (ESLint, Stylelint, pylint) that catch what formatting alone can't — bugs, unused imports, dead code. Each tool stays in its lane, and the codebase stays clean.

deterministic
FAQ

Frequently asked questions

No — this is a source formatter only. Use sass / dart-sass to compile.
No — only .scss curly-brace syntax. The indented .sass parser is not enabled.
No. Use the Sort CSS Properties tool if you want alphabetical order.
Yes — Prettier formats whitespace but never reorders or removes module rules.
No — Prettier runs locally in your browser tab.
Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

Sent straight to the maintainers · no account needed
47 in queue·8 shipped this month
Request queued. Thanks!