Is this swift-format from Apple?

No. This is a lightweight brace-based formatter. Apple's swift-format implements a much larger rule set including line wrapping.

Does my Swift code get uploaded?

No. Everything runs in your browser. iOS app code stays on the device.

Will SwiftUI view modifiers be split across lines?

Existing line breaks are preserved. The formatter does not automatically break long chains of modifiers.

Are property wrappers like @State kept?

Yes. Attributes such as @State, @Binding, and @Environment are preserved on their original lines.

swift · indent · brace-based · live

Format Swift source files

Brace-tracking indenter for Swift — normalises whitespace inside struct, class, and func bodies. Use swift-format for production runs. Runs locally.

Swift Formatter

Input

107 B

3 lines

Output

120 B

4 lines

Status

ready

live

Ratio

1.12×

out/in

input · swift

output · indented swift

struct Greeter{let name:String
    func greet(){print("Hello, \(name)")
        if name.isEmpty{print("(anonymous)")}}}

Quick Start

How to format Swift

A brace-tracking indenter for Swift — it doesn't parse the syntax tree, so consider it a quick clean-up rather than a swift-format replacement.

01
Paste Swift source
Single file, snippet from a tutorial, or a chunk pulled out of an Xcode project.
Parsing runs through Prettier’s standalone bundle (or the language-specific equivalent) loaded lazily — no parser ships until the tool is opened.
swiftPrettierASTstandalonelazy
input · sourceraw · AST
```
struct A{let x=1}
```
loaded · parsedAST · ready
02
Set indent
Apple's style is 4 spaces; many SwiftLint configs prefer 2.
Indent width, tab style, and print-width re-format through a memoised pass — switching 2 → 4 spaces never re-parses, only re-prints.
optsindentprint-widthmemoisedlive
opts · optionsindent · live
```
indent=4
```
options applied · livelive
03
Braces aligned
Lines after { indent one step; lines starting with } dedent first.
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 · formatteddepth · ready
```
struct A {
    let x = 1
}
```
formatted · liveidempotent
04
Copy or save
Source is never uploaded — copy the .swift output or download the file.
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.

Use Cases

When to format Swift

Pasted snippets, code review, tutorials.

Tutorial snippets

Tidy code that arrived from a blog post or Stack Overflow. 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

Code reviews

Indent before pasting into a review comment for diff clarity. 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

Playground prep

Format a single-file Swift playground before sharing. 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

Docs examples

Standardise Swift snippets across an API guide. 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-line Swift expression for readability. 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

Cross-language repos

Match the indent style of neighbouring Kotlin / Java files. 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

Is this swift-format?

No — swift-format needs SwiftSyntax (Mac toolchain). This is a brace-tracking heuristic for quick clean-ups.

Does it touch string literals?

No — single-line and multi-line """ strings are detected and left as-is.

What about property wrappers?

@State, @Published etc. format like any other declaration — they stay on their own line.

Will it format SwiftUI views?

Yes for the brace structure; it won't dot-align trailing closures or chained modifiers.

Is anything sent to a server?

No — formatting runs locally in your browser tab.

Suggest a tool

Something missing?

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

47 in queue·8 shipped this month

Request queued. Thanks!