SQL Formatter

SQL formatting reorganizes queries by adding consistent indentation, capitalizing keywords (SELECT, FROM, WHERE, JOIN), adding line breaks between clauses, and aligning columns. The result is functionally identical to the original but far more readable, making it easier to review, debug, and maintain complex queries.

Yes. SELECT queries are formatted by expanding each clause onto its own line (SELECT, FROM, WHERE, GROUP BY, ORDER BY) and indenting columns. INSERT queries list fields and values aligned. UPDATE statements separate each SET onto its own line. Subqueries receive an extra indentation level to indicate their hierarchy within the main query.

The convention of writing SQL keywords in uppercase (SELECT, FROM, WHERE) dates back to IBM in the 1970s with the SEQUEL language (SQL's predecessor). On terminals of that era, uppercase visually improved readability by distinguishing language commands from table and column names. Although modern SQL engines are case-insensitive for keywords, the convention persists in SQL style guides from Google, Airbnb, and most data teams.

Subqueries are indented one additional level relative to the containing query. A subquery in a WHERE clause receives 4 or 8 spaces of indentation depending on the chosen style. Correlated subqueries (referencing columns from the outer query) are visually marked with comments in some formatters. CTEs (Common Table Expressions) using WITH are listed one per line before the main query.

Yes. Some ORMs and query caching systems benefit from minified SQL (without unnecessary whitespace or line breaks) for comparing queries by hash or reducing traffic in database protocols. Minified SQL also makes it easier to include queries in code strings without escape characters. SQL minification removes comments, collapses multiple spaces into one, and eliminates line breaks while preserving exact semantics.