⌘ K
c# · brace indent · live · client-side

Format C# source files

A brace-tracking indenter for C# code. Re-indents namespaces, classes, methods, and properties. Runs locally.

C# Formatter
Input
82 B
1 lines
Output
83 B
2 lines
Status
ready
live
Ratio
1.01×
out/in
input · c#
output · formatted c#
using System;class Program{static void Main(){Console.WriteLine("Hello, World");}}
Quick Start

How to format C#

Counts brace depth so namespace, class, method, and property blocks all line up consistently.

  1. 01

    Paste C# source

    Top-level statements, classes, records, and LINQ chains all work.

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

    c#PrettierASTstandalonelazy
    input · sourceraw · AST
    class A{}
    loaded · parsedAST · ready
  2. 02

    Pick indent width

    4 spaces is the .NET default; 2 is common in tighter style guides.

    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 · optionsindent · live
    indent=4
    options applied · livelive
  3. 03

    Watch blocks align

    Namespaces, classes, methods, and property bodies indent one level per brace.

    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 · formattedindented · ready
    class A {
    void M() {}
}
    formatted · liveidempotent
  4. 04

    Copy or download

    Export as .cs or copy to clipboard. Source stays in your 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
    ✓ 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 toolsJava FormatterKotlin FormatterC FormatterC++ FormatterSwift FormatterDart Formatter
Use Cases

When to format C#

Scaffolded code, gist cleanup, code review.

Scaffolded code

Tidy code emitted by Roslyn analysers or T4 templates. 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

Gist cleanup

Re-indent samples pasted from blog posts and Stack Overflow. 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

Tutorial code

Make compressed examples readable for learning. 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

Code review

Strip whitespace churn so diffs only show real changes. 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 fix

Reformat a one-liner without opening Visual Studio. 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 C# examples for documentation pages. 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 — it's a brace-tracking indenter. Run dotnet format for real semantic formatting.
Record bodies indent based on brace depth just like classes.
Supported — they indent at the outer scope until a brace opens a new block.
Attributes keep their position; only line indentation changes.
No — the formatter 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!