SQL Formatter

How to Use

1. 1Paste your SQL query
2. 2Choose the SQL dialect
3. 3Click "Format" or "Minify"
4. 4Copy, download, or share the result

Features

• Format and minify actions
• Seven SQL dialects
• Automatic reformatting as you edit
• Copy, download, and share actions
• Error message for malformed input

Before → After

select id,name,total from orders where status='paid' and created_at>'2026-01-01' order by total desc limit 10 becomes:

• SELECT id, name, total
• FROM orders
• WHERE status = 'paid' AND created_at > '2026-01-01'
• ORDER BY total DESC
• LIMIT 10;

Dialect notes

• BigQuery: backtick-quoted project.dataset.table identifiers survive formatting
• T-SQL: square-bracket [columns] and TOP clauses handled
• Snowflake: QUALIFY and other vendor extensions recognized as keywords

What the formatter does not promise

A neatly formatted query can still be wrong, slow, or unsafe. The formatter helps humans read the SQL; it does not validate permissions, execution plans, parameterization, or business logic. Use it to improve reviewability, not as a correctness oracle.

Real-World Use Cases

• Cleaning up one-line SQL copied from logs or application code
• Standardizing queries before code review or documentation
• Switching between formatted and minified SQL during debugging
• Checking how a query reads under a specific dialect parser
• Sharing a readable version of a complex query with another developer

Best Practices

• Pick the closest supported dialect before trusting the formatted output for vendor-specific SQL
• Format first for readability, then minify only if you need a compact single-line result
• Review literals, identifiers, and comment placement after formatting complex queries
• Use the downloaded output when you want to keep a clean reviewed version beside the source query
• Treat formatter output as a readability tool rather than as a SQL validator or optimizer

Common Mistakes to Avoid

• Choosing the wrong dialect and assuming the formatter will interpret vendor-specific syntax correctly
• Treating formatting as proof that the SQL is valid or semantically correct
• Minifying a query too early when you still need to review nested structure
• Ignoring formatter errors when the real issue is malformed input
• Assuming keyword counts or line counts reveal query quality on their own

Troubleshooting

• If formatting fails, check the query for truncated strings, mismatched parentheses, or malformed clauses
• If the result looks odd, switch to the dialect that matches the target database engine
• If minified output is hard to inspect, format the same query again before editing it further
• If a vendor extension still formats poorly, confirm it is covered by one of the supported dialects
• If the query is sensitive, remember the whole transformation still happens locally in your browser