SQL Formatter

The SQL Formatter takes compressed or inconsistently styled SQL and re-prints it with clean indentation, one clause per line, and uniform keyword casing. Whether you inherited a one-liner from a colleague or a log file dumped a query without line breaks, this tool makes it scannable in seconds.

Readable SQL is easier to review, debug, and maintain. When every clause starts on its own line and indentation shows nesting depth, you can spot missing JOIN conditions, misplaced WHERE filters, or incorrect GROUP BY columns at a glance instead of scrolling horizontally through a wall of text.

The formatter uses the sql-formatter library to parse your query and re-print it with consistent indentation, line breaks before clauses, and your chosen keyword casing. It tokenizes the input into keywords, identifiers, operators, and literals, then reconstructs the output following formatting rules for each clause type.

You can choose between 2-space and 4-space indentation, and between UPPER or lower keyword casing. The library handles standard SQL dialect by default, meaning most queries from PostgreSQL, MySQL, SQLite, and SQL Server will format correctly. Formatting does not validate SQL correctness — a syntactically invalid query will still be formatted based on best-effort tokenization.

The formatter runs entirely in your browser — your SQL queries are never sent to any server, so you can safely paste production queries containing table names, column names, or literal values without concern. No data is logged, stored, or transmitted anywhere.

This makes it suitable for formatting queries that reference internal schemas, customer data columns, or proprietary business logic. You get the convenience of an online tool with the privacy of a local desktop application.

The formatter uses a generic SQL dialect by default, which works well for ANSI-standard queries. If you use vendor-specific syntax like PostgreSQL's array operators, MySQL's backtick quoting, or T-SQL's square bracket identifiers, the output should still be reasonable but may not perfectly align non-standard constructs.

Formatting does not validate your SQL — if a query has a syntax error, the formatter will still attempt to produce output rather than rejecting it. This is useful for formatting partial queries or query fragments, but means you should not rely on successful formatting as proof that your SQL is correct. For very large queries (thousands of lines), performance depends on your browser but is typically instant for anything under 10,000 tokens.