Does the query run against any database?

No. The tool only reformats text. Your query is not executed and is never sent to a server.

Which SQL dialects are supported?

PostgreSQL, MySQL, MariaDB, SQLite, BigQuery, Snowflake, Redshift, and ANSI SQL are recognised. Pick the dialect that matches your target database for the best output.

Will it fix invalid SQL?

No. The formatter only changes whitespace and casing. Syntax errors will be preserved as-is, though obviously broken input may produce odd indentation.

Can I force uppercase keywords?

Yes. There is an option to render keywords as UPPERCASE, lowercase, or leave them untouched. Identifiers and string literals are never re-cased.

sql-formatter · 11 dialects · keyword case · live

Format SQL with dialect awareness

Re-indent SELECT/JOIN/WHERE, normalise keyword case, and pick from 11 dialects. Powered by sql-formatter — runs locally.

SQL Formatter

Input

188 B

1 lines

Output

0 B

1 lines

Status

parser…

Ratio

0.00×

out/in

input · sql

output · formatted sql

Loading parser…

Quick Start

How to format SQL

sql-formatter understands per-dialect keywords and reserved words, so PostgreSQL window functions and BigQuery analytic clauses stay aligned.

01
Paste SQL query
Single statement or a multi-statement script — semicolons preserved.
Parsing runs through Prettier’s standalone bundle (or the language-specific equivalent) loaded lazily — no parser ships until the tool is opened.
sqlPrettierASTstandalonelazy
input · sourceraw · AST
```
select 1
```
loaded · parsedAST · ready
02
Pick dialect
Choose Postgres / MySQL / BigQuery / TSQL etc. — reserved words and quoting follow the choice.
Indent width, tab style, and print-width re-format through a memoised pass — switching 2 → 4 spaces never re-parses, only re-prints.
dialectindentprint-widthmemoisedlive
opts · optionslang · live
```
postgresql
```
options applied · livelive
03
Set case & indent
Force keywords UPPER, lower, or preserve casing; tweak indent width.
The formatter is deterministic and idempotent: running it twice produces byte-identical output, which keeps diffs and git noise to a minimum.
styleidempotentdeterministicdiff-cleanstable
opts · formattedstyle · ready
```
upper · 2
```
formatted · liveidempotent
04
Copy or download
Export to .sql file 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
```
✓ 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 SQL

Migrations, ORM logs, query reviews.

ORM log inspection

Pretty-print queries Prisma / Sequelize emits to console. 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 drafts

Format auto-generated migrations before committing. 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 review

Make a colleague's one-line monster query readable. 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

BI dashboards

Normalise SQL pasted into Metabase / Mode questions. 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

Slow query log

Indent slow queries from MySQL/Postgres logs for triage. 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 SQL examples for runbooks and docs. 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

Which dialects work?

Standard SQL, PostgreSQL, MySQL, MariaDB, SQLite, BigQuery, Snowflake, Redshift, Spark SQL, T-SQL, and PL/SQL.

Will it rewrite my query?

No — only whitespace and keyword case change. Semantics are preserved.

Comments?

Single-line (--) and block (/* */) comments are preserved.

Does it validate syntax?

Loosely — sql-formatter tolerates some non-standard SQL and won't refuse to format it.

Is anything sent to a server?

No — sql-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.

47 in queue·8 shipped this month

Request queued. Thanks!