⌘ K
prisma · schema · indent · live

Format Prisma schema files

Basic indenter for schema.prisma — tracks { and } depth. For full field-type alignment use prisma format from the CLI. Runs locally.

Prisma Schema Formatter
Input
133 B
4 lines
Output
138 B
5 lines
Status
ready
live
Ratio
1.04×
out/in
input · prisma
output · formatted schema
datasource db{provider="postgresql"url=env("DATABASE_URL")}
model User{id Int @id @default(autoincrement())
  name String
  posts Post[]}
Quick Start

How to format Prisma schema

A brace-tracking indenter — counts { and } to lay out model, enum, datasource and generator blocks consistently.

  1. 01

    Paste schema

    Drop in a schema.prisma — datasource, generator, model, and enum blocks all welcome.

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

    prismaPrettierASTstandalonelazy
    input · sourceraw · AST
    model User{id Int}
    loaded · parsedAST · ready
  2. 02

    Set indent width

    2 spaces matches the Prisma CLI default. Tabs are not produced — spaces only.

    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=2
    options applied · livelive
  3. 03

    Watch blocks align

    Fields inside { ... } indent, attribute decorators like @id and @default stay on the same line.

    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
    model User {
  id Int @id
}
    formatted · liveidempotent
  4. 04

    Copy or download

    Save as schema.prisma 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
    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 toolsGraphQL FormatterSQL FormatterOpenAPI FormatterProtobuf FormatterYAML FormatterJSON Formatter
Use Cases

When to format Prisma schema

Schema reviews, migration cleanup, docs examples.

Schema reviews

Re-indent before requesting a code review. 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

Migration cleanup

Tidy a hand-edited schema before db push. 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

Snippet sharing

Format a model excerpt before pasting in Slack. 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

Generator config

Re-indent generator blocks after edits. 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 after a paste from a tutorial. 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 schema snippets in documentation. 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 — the CLI command also aligns field types and attributes. This tool only handles indent depth.
No. Run prisma validate for type and relation checks.
No. @id, @default(...), @relation(...) stay exactly as authored.
Triple-slash documentation comments are preserved on their own lines.
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!