SQL Formatter / Minifier

Pretty-print or minify an SQL statement in your browser. Each top-level clause on its own line, columns indented, JOIN clauses aligned. Keyword case, indent, and semicolons are configurable. Nothing is uploaded.

—

 
 
 

Loosely PostgreSQL-flavoured but tolerant of MySQL, SQLite,
    SQL Server, and Oracle-style syntax. Pure client-side, no
    upload. Not a parser — it doesn't validate that your SQL is
    syntactically correct.

   
  
About this tool
SQL Formatter pretty-prints SQL queries in your browser. It supports the major dialects (PostgreSQL, MySQL, SQLite, BigQuery, Standard SQL, and a generic mode) and lets you choose the indent (2 or 4 spaces), the keyword case (upper, lower, preserve), and whether to expand a comma-separated list onto separate lines. The formatter is dialect-aware: it knows about PostgreSQL's `::cast`, MySQL's backticks, SQLite's `INSERT OR REPLACE`, and BigQuery's backticked project references, and formats them correctly.
When to use it
  • Cleaning up a one-line query you pasted from a log or a chat window
  • Standardising the formatting of a migration file before commit
  • Preparing a query to paste into a code review where the reviewer prefers uppercase keywords
  • Tidying a query before sharing it on Stack Overflow or a forum
When not to use it
  • You need a query that round-trips losslessly — the formatter normalises whitespace and keyword case, so the formatted output will not equal the original byte-for-byte
  • You need to parse SQL — this formats, it does not validate syntax. A syntactically invalid query will format (or fail) without telling you what is wrong
  • You need to format a stored procedure or a script with control flow — the formatter handles single statements and CTEs, not procedural blocks
Frequently asked questions
Does it validate the SQL?
No. The formatter is syntax-tolerant — it tries to format whatever you give it, including invalid SQL. Use a real SQL parser (sqlfluff, sqlparse) if you need validation.
Why does my BigQuery query look different in this tool?
The BigQuery dialect uses backticks for identifiers and supports project.dataset.table references. Pick 'BigQuery' as the dialect so the formatter applies the right rules.
← Back to the homepage · More guides · More from the blog